Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa15803; 7 May 96 9:58 EDT Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa08323; 7 May 96 9:58 EDT Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa15773; 7 May 96 9:58 EDT Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa14222; 7 May 96 9:15 EDT Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; cc: ipng@sunroof.eng.sun.com Sender:ietf-announce-request@IETF.CNRI.Reston.VA.US From: Internet-Drafts@CNRI.Reston.VA.US Reply-to: Internet-Drafts@CNRI.Reston.VA.US Subject: I-D ACTION:draft-ietf-ipngwg-iid-02.txt Date: Tue, 07 May 96 09:15:12 -0400 X-Orig-Sender: cclark@CNRI.Reston.VA.US Message-ID: <9605070915.aa14222@IETF.CNRI.Reston.VA.US> --NextPart A Revised 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 : Identifying IPv6 Interfaces in Link-Local Addresses Author(s) : R. Elz Filename : draft-ietf-ipngwg-iid-02.txt Pages : 16 Date : 05/06/1996 This draft proposes a change to the way that IPv6 link local addresses are constructed, so that a node can guarantee that all of its link local addresses are unique within the node. The current definition of a link local address, a well known prefix, some number of zero bits, and a link specific unique token, ensures that it will be unique on the link, which is what is required for communications using those addresses over the link, but does not require uniqueness of the addresses within a node. In some cases all of a nodes interfaces may share the same link local address. Even the possibility of this means that link local addresses, which may in some situations be the only addresses that exist, cannot be used for internal definition of interfaces, or other purposes within the node. This draft suggests a method by which nodes may overcome this problem, by redefining the bits between the prefix and the token to be available to be used by the node to cause the addresses to be unique. 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-iid-02.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-ipngwg-iid-02.txt Internet-Drafts directories are located at: o Africa Address: ftp.is.co.za (196.4.160.8) o Europe Address: nic.nordu.net (192.36.148.17) Address: ftp.nis.garr.it (193.205.245.10) o Pacific Rim Address: munnari.oz.au (128.250.1.21) o US East Coast Address: ds.internic.net (198.49.45.10) o US West Coast Address: ftp.isi.edu (128.9.0.32) Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-ipngwg-iid-02.txt". NOTE: The mail server at ds.internic.net 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. For questions, please mail to Internet-Drafts@cnri.reston.va.us. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19960506111630.I-D@CNRI.Reston.VA.US> ENCODING mime FILE /internet-drafts/draft-ietf-ipngwg-iid-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipngwg-iid-02.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19960506111630.I-D@CNRI.Reston.VA.US> --OtherAccess-- --NextPart--   Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa15213; 10 May 96 10:39 EDT Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa08752; 10 May 96 10:39 EDT Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa15149; 10 May 96 10:39 EDT Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa12953; 10 May 96 9:02 EDT Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; cc: ipng@sunroof.eng.sun.com Sender:ietf-announce-request@IETF.CNRI.Reston.VA.US From: Internet-Drafts@CNRI.Reston.VA.US Reply-to: Internet-Drafts@CNRI.Reston.VA.US Subject: I-D ACTION:draft-ietf-ipngwg-pppext-ipv6cp-03.txt Date: Fri, 10 May 96 09:02:08 -0400 X-Orig-Sender: cclark@CNRI.Reston.VA.US Message-ID: <9605100902.aa12953@IETF.CNRI.Reston.VA.US> --NextPart A Revised 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 over PPP Author(s) : D. Haskin, E. Allen Filename : draft-ietf-ipngwg-pppext-ipv6cp-03.txt Pages : 11 Date : 05/09/1996 The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, and proposes a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This document defines the method for transmission of IP Version 6 [2] packets over PPP links as well as the Network Control Protocol (NCP) for establishing and configuring the IPv6 over PPP. It also specifies the method of forming IPv6 link-local addresses on PPP links. 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-pppext-ipv6cp-03.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-ipngwg-pppext-ipv6cp-03.txt Internet-Drafts directories are located at: o Africa Address: ftp.is.co.za (196.4.160.8) o Europe Address: nic.nordu.net (192.36.148.17) Address: ftp.nis.garr.it (193.205.245.10) o Pacific Rim Address: munnari.oz.au (128.250.1.21) o US East Coast Address: ds.internic.net (198.49.45.10) o US West Coast Address: ftp.isi.edu (128.9.0.32) Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-ipngwg-pppext-ipv6cp-03.txt". NOTE: The mail server at ds.internic.net 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. For questions, please mail to Internet-Drafts@cnri.reston.va.us. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19960509145039.I-D@CNRI.Reston.VA.US> ENCODING mime FILE /internet-drafts/draft-ietf-ipngwg-pppext-ipv6cp-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipngwg-pppext-ipv6cp-03.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19960509145039.I-D@CNRI.Reston.VA.US> --OtherAccess-- --NextPart--   Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18032; 10 May 96 12:25 EDT Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa10384; 10 May 96 12:25 EDT Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa17952; 10 May 96 12:25 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa17793; 10 May 96 12:18 EDT Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa10274; 10 May 96 12:18 EDT Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa17786; 10 May 96 12:18 EDT To: IETF-Announce: ; Cc: RFC Editor Cc: Internet Architecture Board Cc: ipng@sunroof.eng.sun.com Sender:ietf-announce-request@IETF.CNRI.Reston.VA.US From: The IESG Subject: Protocol Action: A Method for the Transmission of IPv6 Packets over Ethernet Networks to Proposed Standard Date: Fri, 10 May 96 12:18:17 -0400 X-Orig-Sender: scoya@CNRI.Reston.VA.US Message-ID: <9605101218.aa17786@IETF.CNRI.Reston.VA.US> The IESG has approved the Internet-Draft "A Method for the Transmission of IPv6 Packets over Ethernet Networks" as a Proposed Standard. This document is the product of the IPNG Working Group. The IESG contact persons are Scott Bradner and Allison Mankin. Technical Summary This memo specifies the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses on Ethernet networks. It also specifies the content of the Source/Target Link-layer Address option used in the Router Solicitation, Router Advertisement, Neighbor Solicitation, and Neighbor Advertisement messages described in IPv6 Neighbor Discovery when those messages are transmitted on an Ethernet. Working Group Summary The Working Group Last-Call did not indicate any problems with this proposal. Protocol Quality This document has been reviewed for the IESG by Scott Bradner and Allison Mankin.   Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa19247; 13 May 96 15:08 EDT Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa12058; 13 May 96 15:08 EDT Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa19230; 13 May 96 15:08 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa19121; 13 May 96 15:02 EDT Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa11978; 13 May 96 15:02 EDT Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa19109; 13 May 96 15:02 EDT To: IETF-Announce: ; Cc: RFC Editor Cc: Internet Architecture Board Cc: ipng@sunroof.eng.sun.com Sender:ietf-announce-request@IETF.CNRI.Reston.VA.US From: The IESG Subject: Protocol Action: An IPv6 Provider-Based Unicast Address Format to Proposed Standard Date: Mon, 13 May 96 15:02:23 -0400 X-Orig-Sender: scoya@CNRI.Reston.VA.US Message-ID: <9605131502.aa19109@IETF.CNRI.Reston.VA.US> The IESG has approved the Internet-Draft "An IPv6 Provider-Based Unicast Address Format" as a Proposed Standard. This document is the product of the IPNG Working Group. The IESG contact persons are Scott Bradner and Allison Mankin. Technical Summary This document defines an IPv6 provider-based unicast address format for use in the Internet. The address format defined in this document is consistent with previous documents from the IPng working group and is intended to facilitate scalable Internet routing. The unicast address format defined in this document doesn't preclude the use of other unicast address formats. Working Group Summary This document reflects comments recieved during IESG review. Protocol Quality The document was review for the IESG by Allison Mankin and Scott Bradner.   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa16959; 23 May 96 9:32 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa16948; 23 May 96 9:32 EDT Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa07660; 23 May 96 9:32 EDT Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa16914; 23 May 96 9:32 EDT Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa16659; 23 May 96 9:25 EDT Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; cc: ipng@sunroof.eng.sun.com X-Orig-Sender:ietf-announce-request@IETF.CNRI.Reston.VA.US Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Internet-Drafts@CNRI.Reston.VA.US Reply-to: Internet-Drafts@CNRI.Reston.VA.US Subject: I-D ACTION:draft-ietf-ipngwg-fddi-ntwrks-04.txt Date: Thu, 23 May 96 09:25:18 -0400 X-Orig-Sender: cclark@CNRI.Reston.VA.US Message-ID: <9605230925.aa16659@IETF.CNRI.Reston.VA.US> --NextPart A Revised 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 : A Method for the Transmission of IPv6 Packets over FDDI Networks Author(s) : M. Crawford Filename : draft-ietf-ipngwg-fddi-ntwrks-04.txt Pages : 6 Date : 05/22/1996 This memo specifies the MTU and frame format for transmission of IPv6 [IPV6] packets on FDDI networks, including a method for MTU determination in the presence of 802.1d bridges to other media. It also specifies the method of forming IPv6 link-local addresses on FDDI networks and the content of the Source/Target Link-layer Address option used the the Router Solicitation, Router Advertisement, Neighbor Solicitation, and Neighbor Advertisement messages described in [DISC], when those messages are transmitted on an FDDI network. 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-fddi-ntwrks-04.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-ipngwg-fddi-ntwrks-04.txt Internet-Drafts directories are located at: o Africa Address: ftp.is.co.za (196.4.160.8) o Europe Address: nic.nordu.net (192.36.148.17) Address: ftp.nis.garr.it (193.205.245.10) o Pacific Rim Address: munnari.oz.au (128.250.1.21) o US East Coast Address: ds.internic.net (198.49.45.10) o US West Coast Address: ftp.isi.edu (128.9.0.32) Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-ipngwg-fddi-ntwrks-04.txt". NOTE: The mail server at ds.internic.net 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. For questions, please mail to Internet-Drafts@cnri.reston.va.us. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19960522100514.I-D@CNRI.Reston.VA.US> ENCODING mime FILE /internet-drafts/draft-ietf-ipngwg-fddi-ntwrks-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipngwg-fddi-ntwrks-04.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19960522100514.I-D@CNRI.Reston.VA.US> --OtherAccess-- --NextPart--   Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa19354; 24 May 96 9:28 EDT Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa07050; 24 May 96 9:28 EDT Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa19226; 24 May 96 9:28 EDT Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa18668; 24 May 96 9:13 EDT Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; cc: ipng@sunroof.eng.sun.com Sender:ietf-announce-request@IETF.CNRI.Reston.VA.US From: Internet-Drafts@CNRI.Reston.VA.US Reply-to: Internet-Drafts@CNRI.Reston.VA.US Subject: I-D ACTION:draft-ietf-ipngwg-pmtuv6-03.txt Date: Fri, 24 May 96 09:13:32 -0400 X-Orig-Sender: cclark@CNRI.Reston.VA.US Message-ID: <9605240913.aa18668@IETF.CNRI.Reston.VA.US> --NextPart A Revised 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. Note: This revision reflects comments received during the last call period. Title : Path MTU Discovery for IP version 6 Author(s) : J. McCann, S. Deering, J. Mogul Filename : draft-ietf-ipngwg-pmtuv6-03.txt Pages : 16 Date : 05/23/1996 This document describes Path MTU Discovery for IP version 6. It is largely derived from RFC-1191, which describes Path MTU Discovery for IP version 4. 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-pmtuv6-03.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-ipngwg-pmtuv6-03.txt Internet-Drafts directories are located at: o Africa Address: ftp.is.co.za (196.4.160.8) o Europe Address: nic.nordu.net (192.36.148.17) Address: ftp.nis.garr.it (193.205.245.10) o Pacific Rim Address: munnari.oz.au (128.250.1.21) o US East Coast Address: ds.internic.net (198.49.45.10) o US West Coast Address: ftp.isi.edu (128.9.0.32) Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-ipngwg-pmtuv6-03.txt". NOTE: The mail server at ds.internic.net 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. For questions, please mail to Internet-Drafts@cnri.reston.va.us. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19960523144137.I-D@CNRI.Reston.VA.US> ENCODING mime FILE /internet-drafts/draft-ietf-ipngwg-pmtuv6-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipngwg-pmtuv6-03.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19960523144137.I-D@CNRI.Reston.VA.US> --OtherAccess-- --NextPart--   Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa19370; 24 May 96 9:28 EDT Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa07053; 24 May 96 9:28 EDT Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa19225; 24 May 96 9:28 EDT Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa18647; 24 May 96 9:13 EDT Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; cc: ipng@sunroof.eng.sun.com Sender:ietf-announce-request@IETF.CNRI.Reston.VA.US From: Internet-Drafts@CNRI.Reston.VA.US Reply-to: Internet-Drafts@CNRI.Reston.VA.US Subject: I-D ACTION:draft-ietf-ipngwg-nsap-ipv6-01.txt Date: Fri, 24 May 96 09:13:21 -0400 X-Orig-Sender: cclark@CNRI.Reston.VA.US Message-ID: <9605240913.aa18647@IETF.CNRI.Reston.VA.US> --NextPart A Revised 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. Note: This revision reflects comments received during the last call period. Title : OSI NSAPs and IPv6 Author(s) : J. Bound, B. Carpenter, D. Harrington, J. Houldsworth, A. Lloyd Filename : draft-ietf-ipngwg-nsap-ipv6-01.txt Pages : 19 Date : 05/23/1996 This document recommends that network implementors who have planned or deployed an OSI NSAP addressing plan, and who wish to deploy or transition to IPv6, should redesign a native IPv6 addressing plan to meet their needs. However, it also defines a set of mechanisms for the support of OSI NSAP addressing in an IPv6 network. These mechanisms are the ones that MUST be used if such support is required. This document also defines a mapping of IPv6 addresses within the OSI address format, should this be required. 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-nsap-ipv6-01.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-ipngwg-nsap-ipv6-01.txt Internet-Drafts directories are located at: o Africa Address: ftp.is.co.za (196.4.160.8) o Europe Address: nic.nordu.net (192.36.148.17) Address: ftp.nis.garr.it (193.205.245.10) o Pacific Rim Address: munnari.oz.au (128.250.1.21) o US East Coast Address: ds.internic.net (198.49.45.10) o US West Coast Address: ftp.isi.edu (128.9.0.32) Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-ipngwg-nsap-ipv6-01.txt". NOTE: The mail server at ds.internic.net 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. For questions, please mail to Internet-Drafts@cnri.reston.va.us. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19960523112140.I-D@CNRI.Reston.VA.US> ENCODING mime FILE /internet-drafts/draft-ietf-ipngwg-nsap-ipv6-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipngwg-nsap-ipv6-01.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19960523112140.I-D@CNRI.Reston.VA.US> --OtherAccess-- --NextPart--   Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa22100; 29 May 96 12:59 EDT Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa10927; 29 May 96 12:58 EDT Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa22073; 29 May 96 12:58 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa21920; 29 May 96 12:55 EDT Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa10875; 29 May 96 12:55 EDT Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa21915; 29 May 96 12:55 EDT To: IETF-Announce: ; Cc: RFC Editor Cc: Internet Architecture Board Cc: ipng@sunroof.eng.sun.com Sender:ietf-announce-request@IETF.CNRI.Reston.VA.US From: The IESG Subject: Protocol Action: Path MTU Discovery for IP version 6 to Proposed Standard Date: Wed, 29 May 96 12:55:26 -0400 X-Orig-Sender: scoya@CNRI.Reston.VA.US Message-ID: <9605291255.aa21915@IETF.CNRI.Reston.VA.US> The IESG has approved the Internet-Draft "Path MTU Discovery for IP version 6" as a Proposed Standard. This document is the product of the IPNG Working Group. The IESG contact persons are Scott Bradner and Allison Mankin. Technical Summary This document describes Path MTU Discovery for IP version 6. It defines a method to determine the largest packet size that can successfully traverse the path from the source node to the destination node. The procedure is largely derived from RFC-1191, which describes Path MTU Discovery for IP version 4. Since IPv6 routers do not fragment packets the use of Path MTU Discovery should be implemented in all IPv6 nodes which would like to send packets greater than the IPv6 minimum packet size (576 bytes) long. Working Group Summary The Working Group Last-Call produced no issues about the proposal. Protocol Quality This document was reviewed for the IESG by Scott Bradner and Allison Mankin.   Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18998; 30 May 96 11:02 EDT Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa08918; 30 May 96 11:02 EDT Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18944; 30 May 96 11:02 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18749; 30 May 96 10:53 EDT Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa08696; 30 May 96 10:53 EDT Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa18742; 30 May 96 10:53 EDT To: IETF-Announce: ; cc: ipng@sunroof.eng.sun.com Sender:ietf-announce-request@IETF.CNRI.Reston.VA.US From: IESG Secretary Subject: Last Call: IP Version 6 over PPP to Proposed Standard Date: Thu, 30 May 96 10:53:44 -0400 X-Orig-Sender: scoya@CNRI.Reston.VA.US Message-ID: <9605301053.aa18742@IETF.CNRI.Reston.VA.US> The IESG has received a request from the IPNG Working Group to consider "IP Version 6 over PPP" for the status of Proposed Standard. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by June 13, 1996.