- ipv6-wg - mailman.ripe.net

(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

(IPng 6135) I-D ACTION:draft-ietf-ipngwg-icmp-v2-01.txt (fwd)
by Thomas Trede 07 Aug '98

07 Aug '98

FYI. Regards, Thomas ---------- Forwarded message ---------- Date: Fri, 07 Aug 1998 08:58:34 -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 6135) I-D ACTION:draft-ietf-ipngwg-icmp-v2-01.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 : Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification Author(s) : A. Conta, S. Deering Filename : draft-ietf-ipngwg-icmp-v2-01.txt Pages : 20 Date : 06-Aug-98 This document specifies a set of Internet Control Message Protocol (ICMP) messages for use with version 6 of the Internet Protocol (IPv6). 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-icmp-v2-01.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipngwg-icmp-v2-01.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-icmp-v2-01.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 6137) I-D ACTION:draft-ietf-ipngwg-ipv6-spec-v2-02.txt (fwd)
by Thomas Trede 07 Aug '98

07 Aug '98

FYI. Regards, Thomas ---------- Forwarded message ---------- Date: Fri, 07 Aug 1998 09:29:25 -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 6137) I-D ACTION:draft-ietf-ipngwg-ipv6-spec-v2-02.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 : Internet Protocol, Version 6 (IPv6) Specification Author(s) : B. Hinden, S. Deering Filename : draft-ietf-ipngwg-ipv6-spec-v2-02.txt Pages : 39 Date : 06-Aug-98 This document specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng. 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-ipv6-spec-v2-02.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipngwg-ipv6-spec-v2-02.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-ipv6-spec-v2-02.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

(ngtrans) I-D ACTION:draft-ietf-ngtrans-natpt-02.txt (fwd)
by Thomas Trede 07 Aug '98

07 Aug '98

FYI. Regards, Thomas ---------- Forwarded message ---------- Date: Fri, 07 Aug 1998 09:16:17 -0400 From: Internet-Drafts(a)ietf.org Reply-To: ngtrans(a)sunroof.Eng.Sun.COM To: IETF-Announce:;;;;@ns.cnri.reston.va.us;@Eng.Sun.COM;;; Cc: ngtrans(a)sunroof.Eng.Sun.COM Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-natpt-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Next Generation Transition Working Group of the IETF. Title : Network Address Translation - Protocol Translation (NAT-PT] Author(s) : P. Srisuresh, G. Tsirtsis Filename : draft-ietf-ngtrans-natpt-02.txt Pages : 17 Date : 06-Aug-98 This document specifies a transition mechanism in addition to those already specified in [TRANS]. The new mechanism provides an end-to-end solution to allow IPv6-only hosts to communicate with IPv4-only hosts and vice versa using Network Address Translation and Protocol Translation. The scheme described does not require du- al-stack hosts; nor does it mandate any routing related changes on the hosts. The scheme is based on a combination of address transla- tion theme as described in [NAT] and V6/V4 protocol translation theme as described in [SIIT]. 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-ngtrans-natpt-02.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ngtrans-natpt-02.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-ngtrans-natpt-02.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 6139) Request that "Proposed TLA and NLA Assignment Rules" be published as Informational (fwd)
by Thomas Trede 07 Aug '98

07 Aug '98

FYI. Regards, Thomas ---------- Forwarded message ---------- Date: Fri, 07 Aug 1998 10:42:09 -0700 From: Bob Hinden <hinden(a)iprg.nokia.com> To: Thomas Narten <narten(a)raleigh.ibm.com>, Jeffrey Burgan <burgan(a)corp.home.net> Cc: ipng(a)sunroof.Eng.Sun.COM, scoya(a)ietf.org Subject: (IPng 6139) Request that "Proposed TLA and NLA Assignment Rules" be published as Informational Thomas, Jeff, This is a second request that the following document be published as an Informational RFC: Title : Proposed TLA and NLA Assignment Rules Author(s) : R. Hinden Filename : draft-ietf-ipngwg-tla-assignment-05.txt Pages : 10 Date : 06-Aug-98 This document 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. Bob Hinden / Steve Deering IPng Chairs -------------------------------------------------------------------- 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 6138) revised IPv6 specs (fwd)
by Thomas Trede 07 Aug '98

07 Aug '98

FYI. Regards, Thomas ---------- Forwarded message ---------- Date: Fri, 7 Aug 1998 09:43:49 -0700 From: Steve Deering <deering(a)cisco.com> To: ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6138) revised IPv6 specs New versions of the IPv6 spec and the ICMPv6 spec have been published, as part of the process of advancing these documents from Proposed Standard to Draft Standard. In the IPv6 spec, the IESG identified two parts of the protocol -- Flow Labels and the Jumbo Payload option -- as having insufficient interoperability experience to advance to Draft Standard. Therefore, in order not to hold up the rest of the protocol, the following changes were made: - Most of the Flow Label section was moved to an appendix of the IPv6 spec, with a pointer to the appendix remaining in the main body of the spec. - The Jumbo Payload option was removed from the spec and placed in a separate draft, which was submitted for publication yesterday afternoon. The other changes to the IPv6 spec were (a) revision of the language in the Security Considerations section (to break a standards dependency loop) and (b) in the Flow Label description, changing the constant FFFFF hex to FFFFF (to take account of the previous change of field width from 24 to 20 bits). Steve -------------------------------------------------------------------- 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 6060) Document Action: IPv6 Multicast Address Assignments to Informational (fwd)
by Thomas Trede 15 Jul '98

15 Jul '98

FYI. Regards, Thomas ---------- Forwarded message ---------- Date: Wed, 15 Jul 1998 07:48:54 -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 6060) Document Action: IPv6 Multicast Address Assignments to Informational The IESG has approved the Internet-Draft 'IPv6 Multicast Address Assignments' <draft-ietf-ipngwg-multicast-assgn-04.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 6020) I-D ACTION:draft-ietf-ipngwg-ipv6-tcp-mib-02.txt (fwd)
by Thomas Trede 10 Jul '98

10 Jul '98

FYI. Regards, Thomas ---------- Forwarded message ---------- Date: Fri, 10 Jul 1998 09:01:13 -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 6020) I-D ACTION:draft-ietf-ipngwg-ipv6-tcp-mib-02.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 : IP Version 6 Management Information Base for the Transmission Control Protocol Author(s) : M. Daniele Filename : draft-ietf-ipngwg-ipv6-tcp-mib-02.txt Pages : 9 Date : 09-Jul-98 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. This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in IPv6-based internets. 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-ipv6-tcp-mib-02.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipngwg-ipv6-tcp-mib-02.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-ipv6-tcp-mib-02.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 6021) I-D ACTION:draft-ietf-ipngwg-ipv6-udp-mib-02.txt (fwd)
by Thomas Trede 10 Jul '98

10 Jul '98

FYI. Regards, Thomas ---------- Forwarded message ---------- Date: Fri, 10 Jul 1998 09:01:20 -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 6021) I-D ACTION:draft-ietf-ipngwg-ipv6-udp-mib-02.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 : IP Version 6 Management Information Base for the User Datagram Protocol Author(s) : M. Daniele Filename : draft-ietf-ipngwg-ipv6-udp-mib-02.txt Pages : 8 Date : 09-Jul-98 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. This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in IPv6-based internets. 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-ipv6-udp-mib-02.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipngwg-ipv6-udp-mib-02.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-ipv6-udp-mib-02.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 6014) Protocol Action: IP Version 6 Addressing Architecture to Proposed Standard (fwd)
by Thomas Trede 08 Jul '98

08 Jul '98

FYI. Regards, Thomas ---------- Forwarded message ---------- Date: Wed, 08 Jul 1998 17:30:48 -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 6014) Protocol Action: IP Version 6 Addressing Architecture to Proposed Standard The IESG has approved the following o IP Version 6 Addressing Architecture <draft-ietf-ipngwg-addr-arch-v2-07.txt> for publication as a Proposed Standard. Note: This document is a replacement for RFC1884, which will be reclassified as Historic. o An IPv6 Aggregatable Global Unicast Address Format <draft-ietf-ipngwg-unicast-aggr-05.txt> for publication as a Proposed Standard. Note: This document is a replacement for RFC2073, which will be reclassified as Historic. These documents are the product of the IPNG Working Group. The IESG contact persons are Jeffrey Burgan and Thomas Narten. Technical Summary The document "IP Version 6 Addressing Architecture" specification defines the addressing architecture of the IP Version 6 protocol. This document includes the IPv6 addressing model, text representations of IPv6 addresses (which are 128 bits in length) , definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses. This document is intended to replace RFC 1884 which will become historic. The document "An IPv6 Aggregatable Global Unicast Address Format" defines an IPv6 aggregatable global unicast address format for use in the Internet. The address format defined in this document is consistent with the IPv6 Protocol and the IPv6 Addressing Architecture (mentioned above) and is designed to facilitate scalable Internet routing. This documented is intended to replaces RFC 2073, "An IPv6 Provider-Based Unicast Address Format" which will become historic. This document is viewed as an improvement over RFC 2073; major changes include removal of the registry bits because they are not needed for route aggregation, support of EUI-64 based interface identifiers, support of provider and exchange based aggregation, separation of public and site topology, and new aggregation based terminology. Working Group Summary These two documents have been the topic of much discussion and consideration, both within the working group and among the IANA and registries. Specifically, the Aggregatable Global Unicast Address Format document has been the subject of detailed discussions for well over a year in an attempt to come up with an address format which has the support of many in the Internet community, including the ISPs. In addition, the policies for how TLAs (the top-level prefixes) are assigned to ISPs have been moved to a separate document in order to clearly separate the technical issues from the operational aspects of how the IANA and the registries manage address space. 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