- ipv6-wg - mailman.ripe.net

(IPng 6108) I-D ACTION:draft-ietf-ipngwg-discovery-v2-03.txt (fwd)
by Thomas Trede 10 Aug '98

10 Aug '98

FYI. Regards, Thomas ---------- Forwarded message ---------- Date: Tue, 04 Aug 1998 09:50:09 -0400 From: Internet-Drafts(a)ietf.org To: IETF-Announce:;;;;@ns.cnri.reston.va.us;@Eng.Sun.COM;;; Cc: ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6108) I-D ACTION:draft-ietf-ipngwg-discovery-v2-03.txt Note: This revision reflects comments received during the last call period. A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IPNG Working Group of the IETF. Title : Neighbor Discovery for IP Version 6 (IPv6) Author(s) : W. Simpson, T. Narten, E. Nordmark Filename : draft-ietf-ipngwg-discovery-v2-03.txt Pages : 92 Date : 03-Aug-98 This document specifies the Neighbor Discovery protocol for IP Version 6. IPv6 nodes on the same link use Neighbor Discovery to discover each other's presence, to determine each other's link-layer addresses, to find routers and to maintain reachability information about the paths to active neighbors. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipngwg-discovery-v2-03.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipngwg-discovery-v2-03.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv(a)ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipngwg-discovery-v2-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.

1 0

(IPng 6154) I-D ACTION:draft-ietf-iab-case-for-ipv6-02.txt (fwd)
by Thomas Trede 10 Aug '98

10 Aug '98

FYI. Regards, Thomas ---------- Forwarded message ---------- Date: Mon, 10 Aug 1998 08:52:01 -0700 From: Steve Deering <deering(a)cisco.com> To: ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6154) I-D ACTION:draft-ietf-iab-case-for-ipv6-02.txt If any of you aren't on the general ietf or ietf-announce list, you probably missed the following ID announcement. This is a draft IAB document, and the IAB would very much appreciate technical review by folks here in the IPNGWG before publishing it as an RFC. Steve > A New Internet-Draft is available from the on-line Internet-Drafts > directories. This draft is a work item of the Internet Architecture > Board (IAB). > > Title : The Case for IPv6 > Author(s) : B. Fink, D. Haskin, C. Perkins, R. Fax, > W. Ling, T. Meehan, S. King > Filename : draft-ietf-iab-case-for-ipv6-02.txt > Pages : 50 > Date : 07-Aug-98 > > This document outlines the business and technical case for IPv6. It > is intended to acquaint both the existing IPv4 community with IPv6, > to encourage its support for change, and to attract potential future > users of Internet technology. > > Internet-Drafts are available by anonymous FTP. Login with the username > "anonymous" and a password of your e-mail address. After logging in, > type "cd internet-drafts" and then > "get draft-ietf-iab-case-for-ipv6-02.txt". > A URL for the Internet-Draft is: > ftp://ftp.ietf.org/internet-drafts/draft-ietf-iab-case-for-ipv6-02.txt -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to majordomo(a)sunroof.eng.sun.com --------------------------------------------------------------------

1 0

(IPng 6153) I-D ACTION:draft-ietf-ipngwg-jumbo-00.txt (fwd)
by Thomas Trede 10 Aug '98

10 Aug '98

FYI. Regards, Thomas ---------- Forwarded message ---------- Date: Mon, 10 Aug 1998 11:21:36 -0400 From: Internet-Drafts(a)ietf.org To: IETF-Announce:;;;;@ns.cnri.reston.va.us;@Eng.Sun.COM;;; Cc: ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6153) I-D ACTION:draft-ietf-ipngwg-jumbo-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IPNG Working Group of the IETF. Title : The IPv6 Jumbo Payload Option Author(s) : B. Hinden, S. Deering Filename : draft-ietf-ipngwg-jumbo-00.txt Pages : 5 Date : 07-Aug-98 This document describes the Jumbo Payload option for IPv6, which is used to send IPv6 packets with payloads longer than 65,535 octets. This option is relevant only for IPv6 nodes that may be attached to links with a link MTU greater than 65,575 octets, and need not be implemented or understood by IPv6 nodes that do not support attachment to links with such large MTUs. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipngwg-jumbo-00.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipngwg-jumbo-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv(a)ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipngwg-jumbo-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.

1 0

(IPng 6151) Document Action: Proposed TLA and NLA Assignment Rules to Informational (fwd)
by Thomas Trede 10 Aug '98

10 Aug '98

FYI. Regards, Thomas ---------- Forwarded message ---------- Date: Mon, 10 Aug 1998 09:03:19 -0400 From: The IESG <iesg-secretary(a)ietf.org> To: IETF-Announce:;;;;@ns.cnri.reston.va.us;@Eng.Sun.COM;;; Cc: RFC Editor <rfc-editor(a)isi.edu>, Internet Architecture Board <iab(a)isi.edu>, ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6151) Document Action: Proposed TLA and NLA Assignment Rules to Informational Deja vu! This protocol action announcement is being resent with the correct subject line. Sorry for any confusion, but it IS Monday morning! The IESG has approved the Internet-Draft Proposed TLA and NLA Assignment Rules <draft-ietf-ipngwg-tla-assignment-05.txt> as an Informational RFC. This document is the product of the IPNG Working Group. The IESG contact persons are Jeffrey Burgan and Thomas Narten. -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to majordomo(a)sunroof.eng.sun.com --------------------------------------------------------------------

1 0

(IPng 6149) Protocol Action: IP Version 6 Management Information Base for the Transmission Control Protocol to Proposed Standard (fwd)
by Thomas Trede 10 Aug '98

10 Aug '98

FYI. Regards, Thomas ---------- Forwarded message ---------- Date: Mon, 10 Aug 1998 08:15:40 -0400 From: The IESG <iesg-secretary(a)ietf.org> To: IETF-Announce:;;;;@ns.cnri.reston.va.us;@Eng.Sun.COM;;; Cc: RFC Editor <rfc-editor(a)isi.edu>, Internet Architecture Board <iab(a)isi.edu>, ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6149) Protocol Action: IP Version 6 Management Information Base for the Transmission Control Protocol to Proposed Standard The IESG has approved the Internet-Draft 'IP Version 6 Management Information Base for the Transmission Control Protocol' <draft-ietf-ipngwg-ipv6-tcp-mib-02.txt> as a Proposed Standard. This document is the product of the IPNG Working Group. The IESG contact persons are Jeffrey Burgan and Thomas Narten. Technical Summary This document is one in the series of documents that define various MIB objects for IPv6. Specifically, this document is the MIB module which defines managed objects for implementations of the Transmission Control Protocol (TCP) over IP Version 6 (IPv6). This document also recommends a specific policy with respect to the applicability of RFC 2012 for implementations of IPv6. Namely, that most of managed objects defined in RFC 2012 are independent of which IP versions underlie TCP, and only the TCP connection information is IP version-specific. Working Group Summary The Working Group last call produced no issues with this document. Protocol Quality This document has been reviewed for the IESG by Juergen Schoenwaelder. It has also been reviewed by Jeffrey Burgan and Thomas Narten of the IESG. -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to majordomo(a)sunroof.eng.sun.com --------------------------------------------------------------------

1 0

(IPng 6152) Document Action: IPv6 Testing Address Allocation to Experimental (fwd)
by Thomas Trede 10 Aug '98

10 Aug '98

FYI. Regards, Thomas ---------- Forwarded message ---------- Date: Mon, 10 Aug 1998 09:33:21 -0400 From: IESG Secretary <iesg-secretary(a)ns.cnri.reston.va.us> To: IETF-Announce:;;;;@ns.cnri.reston.va.us;@Eng.Sun.COM;;; Cc: RFC Editor <rfc-editor(a)isi.edu>, Internet Architecture Board <iab(a)isi.edu>, ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6152) Document Action: IPv6 Testing Address Allocation to Experimental I HATE Mondays... I am sorry, but the Document Action: Proposed TLA and NLA Assignment Rules to Informational was sent in ERROR. This document is currently being evaluated by the IESG, but no decision has been reached at this time. What follows is (I HOPE) THE announcement that is being retransmitted with the corrected Subject line. ===================================================== The IESG has approved the Internet-Draft IPv6 Testing Address Allocation <draft-ietf-ipngwg-testv2-addralloc-01.txt> for publication as an Experimental RFC. This document is the product of the IPNG Working Group. The IESG contact persons are Thomas Narten and Jeffrey Burgan. Note to RFC Editor: The references: [DHCP6] Bound, J., "Host Configuration Protocol for IPv6", Internet Draft, <draft-ietf-dhc-dhcpv6-02.txt>, July 1995. [TLAASN] Hinden, R., "TLA and NLA Assignment Rules", Internet Draft, <draft-ietf-ipngwg-tla-assignment-00.txt>, July 1997. should be changed to "work in progress". I.e., they shouldn't be considered normative). -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to majordomo(a)sunroof.eng.sun.com --------------------------------------------------------------------

1 0

(IPng 6147) Protocol Action: Internet Protocol, Version 6 (IPv6) Specifications to Draft Standard (fwd)
by Thomas Trede 10 Aug '98

10 Aug '98

FYI. Regards, Thomas ---------- Forwarded message ---------- Date: Mon, 10 Aug 1998 06:49:21 -0400 From: The IESG <iesg-secretary(a)ietf.org> To: IETF-Announce:;;;;@ns.cnri.reston.va.us;@Eng.Sun.COM;;; Cc: RFC Editor <rfc-editor(a)isi.edu>, Internet Architecture Board <iab(a)isi.edu>, ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6147) Protocol Action: Internet Protocol, Version 6 (IPv6) Specifications to Draft Standard The IESG has approved publication of the following Internet-Draft as Draft Standards: o Internet Protocol, Version 6 (IPv6) Specification <draft-ietf-ipngwg-ipv6-spec-v2-02.txt> replacing RFC 1883, currently a Proposed Standard. o Neighbor Discovery for IP Version 6 (IPv6) <draft-ietf-ipngwg-discovery-v2-03.txt>, replacing RFC1970, currently a Proposed Standard o IPv6 Stateless Address Autoconfiguration <draft-ietf-ipngwg-addrconf-v2-02.txt>, replacing RFC1971, currently a Proposed Standard o Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification <draft-ietf-ipngwg-icmp-v2-01.txt> replacing RFC 1885, currently a Proposed Standard The IESG also approved Path MTU Discovery for IP version 6 <rfc1981> as a Draft Standard. These documents are the product of the IPNG Working Group. The IESG contact persons are Jeffrey Burgan and Thomas Narten. Technical Summary These documents represent the base protocols for IPv6. The IPv6 Specification defines the base IPv6 packet format and processing rules. The Neighbor Discovery specification defines how to do address resolution for neighboring nodes, as well as to how to locate neighboring routers. The Stateless Address Autoconfiguration document defines how a booting node can generate its own IP addresses without the need to maintain configuration information across machine restarts. The ICMPv6 specification defines the packet formats and processing rules for ICMP for IPv6. The Path MTU Discovery document defines how to perform Path MTU in IPv6. All nodes are required to implement Path MTU in IPv6; routers do not fragment packets they forward. Working Group Summary There is Working Group consensus for the protocols defined in these documents. There were two objections raised during Last Call, but the objections did not have support of the Working Group. However, a small clarification was made to the ICMPv6 spec to make it easier to deploy a new ICMP "Packet Too Big" message, should such a message become defined. Protocol Quality There are numerous implementations of these protocols, and extensive interoperability tests have been done via the UNH consortium and on the 6bone. The documents have been reviewed for the IESG by Jeffrey Burgan and Thomas Narten. -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to majordomo(a)sunroof.eng.sun.com --------------------------------------------------------------------

1 0

(IPng 6148) Protocol Action: Generic Packet Tunneling in IPv6 Specification to Proposed Standard (fwd)
by Thomas Trede 10 Aug '98

10 Aug '98

FYI. Regards, Thomas ---------- Forwarded message ---------- Date: Mon, 10 Aug 1998 07:24:11 -0400 From: The IESG <iesg-secretary(a)ietf.org> To: IETF-Announce:;;;;@ns.cnri.reston.va.us;@Eng.Sun.COM;;; Cc: RFC Editor <rfc-editor(a)isi.edu>, Internet Architecture Board <iab(a)isi.edu>, ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6148) Protocol Action: Generic Packet Tunneling in IPv6 Specification to Proposed Standard The IESG has approved the Internet-Draft 'Generic Packet Tunneling in IPv6 Specification' <draft-ietf-ipngwg-ipv6-tunnel-08.txt> as a Proposed Standard. This document is the product of the IPNG Working Group. The IESG contact persons are Jeffrey Burgan and Thomas Narten. Technical Summary This document specifies a method and generic mechanisms by which a packet is encapsulated and carried as payload within an IPv6 packet. The resulting packet is called an IPv6 tunnel packet. The forwarding path between the source and destination of the tunnel packet is called an IPv6 tunnel. The technique is called IPv6 tunneling. The document also discusses specific mechanisms for tunneling IPv6 and IPv4 packets. Working Group Summary The Working Group last call produced no issues with this document. Protocol Quality This document has been reviewed by Jeffrey Burgan and Thomas Narten of the IESG. -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to majordomo(a)sunroof.eng.sun.com --------------------------------------------------------------------

1 0

(IPng 6150) Protocol Action: IP Version 6 Management Information Base for the User Datagram Protocol to Proposed Standard (fwd)
by Thomas Trede 10 Aug '98

10 Aug '98

FYI. Regards, Thomas ---------- Forwarded message ---------- Date: Mon, 10 Aug 1998 08:29:16 -0400 From: The IESG <iesg-secretary(a)ietf.org> To: IETF-Announce:;;;;@ns.cnri.reston.va.us;@Eng.Sun.COM;;; Cc: RFC Editor <rfc-editor(a)isi.edu>, Internet Architecture Board <iab(a)isi.edu>, ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6150) Protocol Action: IP Version 6 Management Information Base for the User Datagram Protocol to Proposed Standard The IESG has approved the Internet-Draft 'IP Version 6 Management Information Base for the User Datagram Protocol' <draft-ietf-ipngwg-ipv6-udp-mib-02.txt> as a Proposed Standard. This document is the product of the IPNG Working Group. The IESG contact persons are Jeffrey Burgan and Thomas Narten. Technical Summary This document is one in the series of documents that define various MIB objects for IPv6. Specifically, this document is the MIB module which defines managed objects for implementations of the User Datagram Protocol (UDP) over IP Version 6 (IPv6). This document also recommends a specific policy with respect to the applicability of RFC 2013 for implementations of IPv6. Namely, that most of managed objects defined in RFC 2013 are independent of which IP versions underlie UDP, and only the UDP listener information is IP version-specific. Working Group Summary The Working Group last call produced no issues with this document. Protocol Quality This document has been reviewed for the IESG by Juergen Schoenwaelder. It has also been reviewed by Jeffrey Burgan and Thomas Narten of the IESG. -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to majordomo(a)sunroof.eng.sun.com --------------------------------------------------------------------

1 0

(IPng 6136) I-D ACTION:draft-ietf-ipngwg-tla-assignment-05.txt (fwd)
by Thomas Trede 07 Aug '98

07 Aug '98

FYI. Regards, Thomas ---------- Forwarded message ---------- Date: Fri, 07 Aug 1998 08:58:39 -0400 From: Internet-Drafts(a)ietf.org To: IETF-Announce:;;;;@ns.cnri.reston.va.us;@Eng.Sun.COM;;; Cc: ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6136) I-D ACTION:draft-ietf-ipngwg-tla-assignment-05.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IPNG Working Group of the IETF. Title : Proposed TLA and NLA Assignment Rules Author(s) : B. Hinden Filename : draft-ietf-ipngwg-tla-assignment-05.txt Pages : 10 Date : 06-Aug-98 This document proposes rules for Top-Level Aggregation Identifiers (TLA ID) and Next-Level Aggregation Identifiers (NLA ID) as defined in [AGGR]. These proposed rules apply to registries allocating TLA ID's and to organizations receiving TLA ID's. This proposal is intended as input from the IPng working group to the IANA and Registries. It is not intended for any official IETF status. Its content represents the result of extensive discussion between the IPng working group, IANA, and Registries. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipngwg-tla-assignment-05.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipngwg-tla-assignment-05.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv(a)ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipngwg-tla-assignment-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.

1 0