SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Summary of Major Changes to IPv6 Node Requirements Document Draft

bluma avatar
bluma
12 diapositives · 242 Views · Sep 23, 2014

This document outlines significant updates to the IPv6 Node Requirements draft, highlighting changes in formatting, requirement language, and the removal of non-essential documents. Key updates include the clarification of MUST, SHOULD, and MAY requirements, especially regarding Path MTU Discovery and Multicast Listener Discovery. Considerations for Privacy Extensions in Stateless Address Autoconfiguration are discussed, along with IPv4 support scenarios. The document aims to establish clear standards for node functionalities, signaling a need for consistency across implementations.

Summary of Major Changes to IPv6 Node Requirements Document Draft - slide 1
01 / 12Summary of Major Changes to IPv6 Node Requirements Document Draft
1 / 17

Télécharger la présentation

Summary of Major Changes to IPv6 Node Requirements Document Draft
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. IETF 55 IPv6 Working Group IPv6 Node Requirements draft-ietf-ipv6-node-requirements-02.txt John Loughney

  2. Major Changes • Some formatting stuff. • Requirements language. • Removal of many ‘IP over x’ documents. • Many of the MIPv6 requirements.

  3. Requirement Language • MUST ... • (always mandatory) • MUST ... when X • (mandatory under condition X) • SHOULD ... • (always highly recommended) • SHOULD ... when X • (highly recommended when X, possible otherwise) • MAY ... • (possible if you want to do it) • However, we should discuss if this is a Standards Track or Informational document.

  4. RFC 1981 - Path MTU Discovery … • Path MTU is MAY. Some folks have commented that it needs to be SHOULD. • Comment: • ’We really shouldn't be encouraging the idea that it's an option except in very restricted circumstances.’

  5. RFC 3041 - Privacy Extensions …. • Do we want to discuss in what circumstances Privacy Extensions for Stateless Address Autoconfiguration in IPv6 are needed? • hosts • servers • mobile nodes • other

  6. MLD • Change: • Multicast Listener Discovery [RFC-2710] MUST be supported by nodes supporting multicast applications. A primary IPv6 multicast application is Neighbor Discovery (all those solicited-node mcast addresses must be joined). • To: • Multicast Listener Discovery [RFC-2710] MUST be supported by nodes supporting multicast applications or Neighbor Discovery. • Change: • When MLDv2 [MLDv2] has been completed, it SHOULD take precedence over MLD. • To • Nodes supporting source-specific multicast applications MUST support MLDv2.

  7. Default Address Selection for IPv6 • Change: • The rules specified in the document are the only MUST to implement portion of the architecture. A node MUST belong to one site. There is no requirement that a node be able to belong to more than one. • To: • The rules specified in the document are the only MUST to implement portion of the architecture. There is no requirement that a node be able to belong to more than one site.

  8. IPv4 Support • IPv6 nodes MAY support IPv4. However, this document should consider the following cases: • Native IPv6 only • Native IPv6 with IPv4 supported only via tunneling over IPv6 • Native IPv6 and native IPv4 both fully supported. • Need to sort out if this places any requirements on this.

  9. Mobile IP • Mobile Node functionality MAY be supported. • Route Optimization functionality SHOULD be supported for hosts. • Route Optimization is not required for routers. • Remove Home Agent functionality text.

  10. MIBs • What do we want to do here? • Only IP level MIBs SHOULD or MUST be supported. • Forwarding table MIB • IP MIB • Interfaces MIB • Others may be supported as needed. • If you implement another protocol, then you SHOULD or MUST implement the MIB. You MUST implement if you have an SNMP agent. • RFC 1112 says nothing about MIBs.

  11. Other • Remove section on RFC2874 - DNS Extensions to Support IPv6 Address Aggregation and Renumbering

  12. Discussions to Capture (at some point) • Flow Label • DNS discovery • SeND WG issues • ANYCAST