IETF 79 Proceedings

Introduction  |  Area, Working Goup & BoF Reports  |  Plenaries  |  Training  |  Internet Research Task Force

IPv6 Maintenance (6man) (WG)

Minutes  | Audio Archives  |  Jabber Logs  |  Mailing List Archives

Additional information is available at tools.ietf.org/wg/6man

Chair(s): Robert Hinden Brian Haberman Internet Area Director(s): Ralph Droms Jari Arkko Internet Area Advisor: Jari Arkko

Meeting Slides

• Introduction and Agenda
• An uniform format for IPv6 extension headers
• The IPv6 UDP Zero Checksum
• UDP Checksum for Tunneled Packets
• Update to RFC 3484 Default Address Selection for IPv6
• Using 127-bit IPv6 Prefixes on Inter-Router Links
• Duplicate Address Detection Proxy
• Requirements for Addresses Registration
• Update to the IPv6 flow label specification
• Security Assessment of the IPv6 Flow Label
• Moving the Endpoint Identifier (EID) Option to Obsolete Status
• Mitigating Teredo Rooting Loop Attacks

Internet-Drafts:

• IPv6 Node Requirements RFC 4294-bis (65098 bytes)
• Considerations for IPv6 Address Selection Policy Changes (43327 bytes)
• IPv6 UDP Checksum Considerations (83097 bytes)
• An uniform format for IPv6 extension headers (10661 bytes)
• An IPv6 Routing Header for Source Routes with RPL (29492 bytes)
• RPL Option for Carrying RPL Information in Data-Plane Datagrams (17129 bytes)
• Update to RFC 3484 Default Address Selection for IPv6 (22986 bytes)
• Using the IPv6 flow label for equal cost multipath routing and link aggregation in tunnels (21515 bytes)
• Rationale for update to the IPv6 flow label specification (28986 bytes)
• Distributing Address Selection Policy using DHCPv6 (15750 bytes)
• The Line Identification Destination Option (27644 bytes)
• Duplicate Address Detection Proxy (25783 bytes)
• IPv6 Flow Label Specification (29982 bytes)
• UDP Checksums for Tunneled Packets (24819 bytes)

Request for Comments:

• Negotiation for IPv6 datagram compression using IPv6 Control Protocol (RFC 5172) (14646 bytes) obsoletes RFC 2472
• Reserved IPv6 Interface Identifiers (RFC 5453) (11754 bytes)
• Handling of Overlapping IPv6 Fragments (RFC 5722) (11838 bytes) Updates RFC 2460
• IANA Allocation Guidelines for the IPv6 Routing Header (RFC 5871) (4000 bytes) Updates RFC 2460
• IPv6 Subnet Model: The Relationship between Links and Subnet Prefixes (RFC 5942) (27035 bytes) Updates RFC 4861
• A Recommendation for IPv6 Address Text Representation (RFC 5952) (26570 bytes) Updates RFC 4291
• IPv6 Router Advertisement Options for DNS Configuration (RFC 6106) (45181 bytes) obsoletes RFC 5006
• Using 127-bit IPv6 Prefixes on Inter-Router Links (RFC 6164) (16057 bytes)

Charter (as of 2008-12-16)

The 6man working group is responsible for the maintenance, upkeep,
and advancement of the IPv6 protocol specifications and addressing
architecture. It is not chartered to develop major changes or
additions to the IPv6 specifications. The working group will
address protocol limitations/issues discovered during deployment
and operation. It will also serve as a venue for discussing
the proper location for working on IPv6-related issues within
the IETF.

The working group's work items are as follows:

o Complete work on RA Flags Option
o Complete work on RH0 Deprecation
o Complete work on IPv6 over PPP Compression Negotiation
o Complete work on Centrally Allocated Unique Local
Addresses (ULA-C)

All new work items not listed above require the approval
of the working group and the sponsoring Area Director before
they will be taken on by the working group.

Goals and Milestones:

Done		Submit RH0 Deprecation specification to IESG as a Proposed Standard
Jan 2008		Submit PPP Compression Negotiation specification to IESG as a Proposed Standard
Mar 2008		Determine way forward for ULA-C specification