[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Revised charter: IPv6
Thomas,
This charter looks good. Moving DNS out seems logical, having a dedicated WG or
as part of a WG looking at the general topic of service discovery in IPv6 makes
more sense to me.
Regarding the rest, point to point links were suggested as something for PPP as
an alternative. It might be wise to firm this up before releasing the charter.
Putting this in PPP might make sense, as the expertise is presumably there.
The proposed schedule looks a little aggressive, but since most of these items
are currently underway, perhaps not so. I'm particularly concerned about the
scoped addressing discussion in this regard, but perhaps there will be some
concensus emerging out of discussions in SFO that promises earlier than expected
completion.
jak
----- Original Message -----
From: "Thomas Narten" <narten@us.ibm.com>
To: <iesg@ietf.org>; <iab@iab.org>
Sent: Tuesday, March 04, 2003 6:50 AM
Subject: Revised charter: IPv6
> Here is a revised charter for the IPv6 WG. A new charter has been
> needed for quite some time, and it would be very good to
> get one approved prior to SF.
>
> One contentious issue is that it does not mention DNS discovery
> anymore; it was removed at my request. There will likely be at least
> some unhappiness over this in the WG, and my next task is to draft a
> note to the WG explaining why I wanted the item out.
>
> Internet Protocol Version 6 (IPv6) Working Group Charter -- DRAFT
>
> <ipv6-wg-charter-10.txt>
>
> Chairs:
>
> Bob Hinden <hinden@iprg.nokia.com>
> Margaret Wasserman <mrw@windriver.com>
>
> Description of the Working Group:
>
> The IPv6 working group is responsible for the specification and
> standardization of the Internet Protocol version 6 (IPv6). IPv6 provides
> a much larger global addresses space than its predecessor IPv4. This
> enables global end-to-end communication and restores valuable properties
> of the IP architecture that have been lost in the IPv4 Internet. The
> core IPv6 standards are widely implemented and are in the early stages of
> global deployment.
>
> The IPv6 working group was originally chartered by the IESG as the IP
> Next Generation (IPng) working group to implement the recommendations of
> the IPng Area Directors as outlined at the July 1994 IETF meeting and in
> "The Recommendation for the IP Next Generation Protocol," RFC1752,
> January 1995.
>
> The primary focus of the IPv6 w.g. is to complete the standardization of
> the IPv6 protocols.
>
> The working group's responsibilities are:
>
> - Completing work on the IPv6 working group documents as described
> below, and
> - Reviewing and updating IPv6 specifications based on implementation
> and deployment experience, and advancing them on the standardization
> track as appropriate.
>
> The IPv6 working group's standardization responsibilities are divided
> into two areas: Urgent for Deployment, and Completing Current Work.
> Priority will be given to the first area. The work items in each
> priority area are as follows:
>
> Urgent For Deployment
> - Complete Prefix Delegation requirements and publish. Related work is:
> o Work with DHCPv6 working group to write DHCPv6 option for IPv6
> prefix delegation.
> o Develop Proxy Router Advertisement solution for prefix delegation
> and publish. This enable a simple site border router to
> re-advertise downstream a prefix it hears on it's upstream link.
> Use Multi-Link subnet work as basis for this. Note: general
> multi-link subnet work will be done elsewhere in the IETF.
> - Complete revision of IPv6 MIBs (combined IPv4/IPv6 versions) and
> publish.
>
> Current Work
> - Complete work on "A Flexible method to manage the assignment of bits
> of an IPv6 address block".
> - Revise "Aggregatable Unicast Addresses" (RFC2374) to remove TLA/NLA/SLA
> terminology.
> - Revise "Basic Sockets Extensions" (RFC2553) and publish.
> - Revise "Advanced Sockets API" (RFC2292) and publish.
> - Complete "Default Router Preferences, More-Specific Routes, and Load
> Sharing" and publish.
> - Update to ICMPv6 (RFC2463) and publish.
> - Complete "Node Information Queries" and publish.
> - Update Auto Configuration (RFC2462) and Neighbor Discovery (RFC2461)
> and publish.
> - Update "Privacy Extensions for Stateless Autoconfiguration"
> document (RFC3041) and publish.
> - Complete work on IPv6 Node Requirements and publish.
> - Complete work on Flow Label and publish.
> - Explore and document the issues with site-local addressing. Determine
> appropriate limitations on the use of site-local addresses, and
> document those limitations.
> - Complete work on Scoped Addressing Architecture and publish.
> - Update IPv6 over PPP (RFC2472) and publish (may be done in PPP
> Extension w.g.).
> - Review Point-to-point link support in IPv6 and decide if any IPv6
> specifications need to be updated.
> - Complete work on "Link Scoped IPv6 Multicast Addresses" and publish.
>
> All new work items not listed above require the approval of the working
> group and IESG before they will be taken on by the working group.
>
> Goals & Milestones
>
> Feb 03 Submit "A Flexible method to manage the assignment of bits
> of an IPv6 address block" to the IESG for Informational.
> Feb 03 Submit Flow Label specification to IESG for Proposed Standard.
> Feb 03 Submit Routing Table MIB to IESG for Proposed Standard.
> Mar 03 Submit Prefix Delegation requirements and submit to IESG for
> Informational.
> Mar 03 Draft on Proxy RA solution for prefix delegation.
> Mar 03 Revise Aggregatable Unicast Addresses (RFC2374) to remove
> TLA/NLA/SLA terminology.
> Apr 03 Submit update to ICMPv6 (RFC2463) to be republished at Draft
> Standard.
> Apr 03 Submit TCP MIB to IESG for Proposed Standard.
> Apr 03 Submit IPv6 Node Requirements to IESG for Informational.
> May 03 Resubmit Node Information Queries to IESG for Proposed Standard.
> May 03 Submit UDP MIB to IESG for Proposed Standard.
> Jun 03 Submit IP MIB to IESG for Proposed Standard.
> Jun 03 Submit Router Preferences, More-Specific Routes, and Load
> Sharing to IESG for Proposed Standard
> Jun 03 Submit updates to Auto Configuration (RFC2462) and Neighbor
> Discovery (RFC2461) to be republished at Draft Standard.
> Jun 03 Submit Update to Privacy Extensions for Stateless
> Autoconfiguration document (RFC3041) to the IESG for Draft
> Standard.
> Jul 03 Submit Proxy RA to IESG for Proposed Standard.
> Jul 03 Submit Link Scoped IPv6 Multicast Addresses to IESG for Proposed
> Standard.
> Aug 03 Submit IPv6 Scoped Addressing Architecture to IESG for Proposed
> Standard
> Aug 03 Submit update to IPv6 over PPP (RFC2472) to IESG for Draft
> Standard.
> Nov 03 Re-charter or close working group.
>
>
>
> Thomas
>