December 1998 - ipv6-wg - mailman.ripe.net

Fw: (ngtrans) interim meeting planning
by Thomas Trede 16 Dec '98

16 Dec '98

FYI. Regards, Thomas Trede -----Original Message----- From: Steve Deering <deering(a)cisco.com> To: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM>; ngtrans(a)sunroof.Eng.Sun.COM <ngtrans(a)sunroof.Eng.Sun.COM>; 6bone(a)ISI.EDU <6bone(a)ISI.EDU> Cc: hinden(a)iprg.nokia.com <hinden(a)iprg.nokia.com>; rlfink(a)lbl.gov <rlfink(a)lbl.gov>; tonyhain(a)microsoft.com <tonyhain(a)microsoft.com>; deering(a)cisco.com <deering(a)cisco.com> Date: Mittwoch, 16. Dezember 1998 09:30 Subject: (ngtrans) interim meeting planning >As mentioned in the ipngwg and ngtrans meetings in Orlando last week, >the chairs of the two working groups propose to hold a two-day joint >interim meeting in the first week of February to discuss the next steps >in IPv6 standardization, implementation, transition, and deployment. >We propose also to allocate a third day for non-working-group business, >such as coordination of the 6bone, 6ren, and other IPv6-related >initiatives. A more concrete agenda is in preparation, but of >immediate concern is deciding where to meet. We have narrowed it >down to two choices: > > (1) the San Francisco Bay Area > > (2) Grenoble, France > >The meeting dates will be February 2-4. > >We would like to hear as soon as possible (like, within the next 24 hours) >from those of you who would like to attend the meeting but will be able >to attend in only one of those two places. Specifically: > > - If you can attend in either place, do not reply. > > - If you cannot attend in either place, do not reply, > > - If you can attend in only one of those two places, > please reply as soon as possible to Bob, Bob, Tony, and me > (our addresses are in the Cc: line, above; please do NOT reply > to the three mailing lists in the To: line!), and tell us > in which place you can attend. > >Thanks, >Steve > > >

1 0

Fw: (IPng 6884) Last Call: Mobility Support in IPv6 to Proposed Standard
by Thomas Trede 16 Dec '98

16 Dec '98

FYI. Regards, Thomas Trede -----Original Message----- From: The IESG (by way of Bob Hinden <hinden(a)iprg.nokia.com>) <iesg-secretary(a)ietf.org> To: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Date: Dienstag, 15. Dezember 1998 19:12 Subject: (IPng 6884) Last Call: Mobility Support in IPv6 to Proposed Standard > >The IESG has received a request from the IP Routing for Wireless/Mobile >Hosts Working Group to consider Mobility Support in IPv6 ><draft-ietf-mobileip-ipv6-07.txt> as a 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(a)ietf.org or ietf(a)ietf.org mailing lists by January 7, 1999. > >Files can be obtained via >http://www.ietf.org/internet-drafts/draft-ietf-mobileip-ipv6-07.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

Fw: (IPng 6859) Implementation Reports for Addressing Specifications
by Thomas Trede 11 Dec '98

11 Dec '98

FYI. Regards, Thomas Trede -----Original Message----- From: Bob Hinden <hinden(a)iprg.nokia.com> To: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Cc: hinden(a)iprg.nokia.com <hinden(a)iprg.nokia.com>; deering(a)cisco.com <deering(a)cisco.com> Date: Montag, 7. Dezember 1998 16:07 Subject: (IPng 6859) Implementation Reports for Addressing Specifications >The first set of implementation reports for "RFC2373 IP Version 6 >Addressing Architecture" and "RFC2374 An Aggregatable Global Unicast >Address Format" are available at: > >ftp://playground.sun.com/pub/ipng/implementation-reports/add-arch-aggregat. txt > >Collecting implementation reports for these specifications is an important >part of moving them to Draft Standard. If you have not sent one in yet, >please do. > >Thanks, >Bob > > > > > > > > >-------------------------------------------------------------------- >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

Fw: (IPng 6865) RFC 2473 on Generic Packet Tunneling in IPv6
by Thomas Trede 09 Dec '98

09 Dec '98

FYI. Regards, Thomas Trede -----Original Message----- From: RFC Editor (by way of Bob Hinden <hinden(a)iprg.nokia.com>) <rfc-ed(a)ISI.EDU> To: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Date: Dienstag, 8. Dezember 1998 15:51 Subject: (IPng 6865) RFC 2473 on Generic Packet Tunneling in IPv6 > >A new Request for Comments is now available in online RFC libraries. > > > RFC 2473: > > Title: Generic Packet Tunneling in IPv6 Specification > Author(s): A. Conta, S. Deering > Status: Proposed Standard > Date: December 1998 > Mailbox: aconta(a)lucent.com, deering(a)cisco.com > Pages: 36 > Characters: 77956 > Updates/Obsoletes/See Also: None > I-D Tag: draft-ietf-ipngwg-ipv6-tunnel-08.txt > > > URL: ftp://ftp.isi.edu/in-notes/rfc2473.txt > > >This document defines the model and generic mechanisms for IPv6 >encapsulation of Internet packets, such as IPv6 and IPv4. The model >and mechanisms can be applied to other protocol packets as well, such >as AppleTalk, IPX, CLNP, or others. > >This document is a product of the IPNG Working Group of the IETF. > >This is now a Proposed Standard protocol. > >This document specifies an Internet standards track protocol for >the Internet community, and requests discussion and suggestions >for improvements. Please refer to the current edition of the >"Internet Official Protocol Standards" (STD 1) for the >standardization state and status of this protocol. Distribution >of this memo is unlimited. > >This announcement is sent to the IETF list and the RFC-DIST list. >Requests to be added to or deleted from the IETF distribution list >should be sent to IETF-REQUEST(a)IETF.ORG. Requests to be >added to or deleted from the RFC-DIST distribution list should >be sent to RFC-DIST-REQUEST(a)RFC-EDITOR.ORG. > >Details on obtaining RFCs via FTP or EMAIL may be obtained by sending >an EMAIL message to rfc-info(a)RFC-EDITOR.ORG with the message body >help: ways_to_get_rfcs. For example: > > To: rfc-info(a)RFC-EDITOR.ORG > Subject: getting rfcs > > help: ways_to_get_rfcs > >Requests for special distribution should be addressed to either the >author of the RFC in question, or to RFC-Manager(a)RFC-EDITOR.ORG. Unless >specifically noted otherwise on the RFC itself, all RFCs are for >unlimited distribution.echo >Submissions for Requests for Comments should be sent to >RFC-EDITOR(a)RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC >Authors, for further information. > > >Joyce K. Reynolds and Alegre Ramos >USC/Information Sciences Institute > >... > >Below is the data which will enable a MIME compliant Mail Reader >implementation to automatically retrieve the ASCII version >of the RFCs. >Content-Type: text/plain >Content-ID: <981207160836.RFC(a)RFC-EDITOR.ORG> > >RETRIEVE: rfc >DOC-ID: rfc2473 > ><ftp://ftp.isi.edu/in-notes/rfc2473.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

Fw: (IPng 6849) RFC 2472 on IP Version 6 over PPP
by Thomas Trede 08 Dec '98

08 Dec '98

FYI. Regards, Thomas Trede -----Original Message----- From: RFC Editor (by way of Bob Hinden <hinden(a)iprg.nokia.com>) <rfc-ed(a)ISI.EDU> To: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Date: Freitag, 4. Dezember 1998 22:12 Subject: (IPng 6849) RFC 2472 on IP Version 6 over PPP > >A new Request for Comments is now available in online RFC libraries. > > > RFC 2472: > > Title: IP Version 6 over PPP > Author(s): D. Haskin, E. Allen > Status: Proposed Standard > Date: December 1998 > Mailbox: dhaskin(a)baynetworks.com, eallen(a)baynetworks.com > Pages: 14 > Characters: 29696 > Obsoletes: 2023 > I-D Tag: draft-ietf-ipngwg-ipv6-over-ppp-06.txt > > URL: ftp://ftp.isi.edu/in-notes/rfc2472.txt > > >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. > >This document is a product of the IPNG Working Group of the IETF. > >This is now a Proposed Standard Protocol. > >This document specifies an Internet standards track protocol for >the Internet community, and requests discussion and suggestions >for improvements. Please refer to the current edition of the >"Internet Official Protocol Standards" (STD 1) for the >standardization state and status of this protocol. Distribution >of this memo is unlimited. > >This announcement is sent to the IETF list and the RFC-DIST list. >Requests to be added to or deleted from the IETF distribution list >should be sent to IETF-REQUEST(a)IETF.ORG. Requests to be >added to or deleted from the RFC-DIST distribution list should >be sent to RFC-DIST-REQUEST(a)RFC-EDITOR.ORG. > >Details on obtaining RFCs via FTP or EMAIL may be obtained by sending >an EMAIL message to rfc-info(a)RFC-EDITOR.ORG with the message body >help: ways_to_get_rfcs. For example: > > To: rfc-info(a)RFC-EDITOR.ORG > Subject: getting rfcs > > help: ways_to_get_rfcs > >Requests for special distribution should be addressed to either the >author of the RFC in question, or to RFC-Manager(a)RFC-EDITOR.ORG. Unless >specifically noted otherwise on the RFC itself, all RFCs are for >unlimited distribution.echo >Submissions for Requests for Comments should be sent to >RFC-EDITOR(a)RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC >Authors, for further information. > > >Joyce K. Reynolds and Alegre Ramos >USC/Information Sciences Institute > >... > >Below is the data which will enable a MIME compliant Mail Reader >implementation to automatically retrieve the ASCII version >of the RFCs. >Content-Type: text/plain >Content-ID: <981204115249.RFC(a)RFC-EDITOR.ORG> > >RETRIEVE: rfc >DOC-ID: rfc2472 > ><ftp://ftp.isi.edu/in-notes/rfc2472.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

Fw: (IPng 6838) RFC 2470 on IPv6 over Token Ring
by Thomas Trede 08 Dec '98

08 Dec '98

FYI. Regards, Thomas Trede -----Original Message----- From: RFC Editor (by way of Bob Hinden <hinden(a)iprg.nokia.com>) <rfc-ed(a)ISI.EDU> To: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Date: Freitag, 4. Dezember 1998 03:23 Subject: (IPng 6838) RFC 2470 on IPv6 over Token Ring > >A new Request for Comments is now available in online RFC libraries. > > > RFC 2470: > > Title: Transmission of IPv6 Packets over Token Ring > Networks > Author(s): M. Crawford, T. Narten, S. Thomas > Status: Proposed Standard > Date: December 1998 > Mailbox: crawdad(a)fnal.gov, narten(a)raleigh.ibm.com, > stephen.thomas(a)transnexus.com > Pages: 11 > Characters: 21677 > Updates/Obsoletes/See Also: None > I-D Tag: draft-ietf-ipngwg-trans-tokenring-05.txt > > URL: ftp://ftp.isi.edu/in-notes/rfc2470.txt > > >This memo specifies the MTU and frame format for transmission of IPv6 >packets on Token Ring networks. It also specifies the method of >forming IPv6 link-local addresses on Token Ring networks and the >content of the Source/Target Link-layer Address option used the Router >Solicitation, Router Advertisement, Redirect, Neighbor Solicitation >and Neighbor Advertisement messages when those messages are >transmitted on a Token Ring network. > >This document is a product of the IPNG Working Group of the IETF. > >This is now a Proposed Standard Protocol. > >This document specifies an Internet standards track protocol for >the Internet community, and requests discussion and suggestions >for improvements. Please refer to the current edition of the >"Internet Official Protocol Standards" (STD 1) for the >standardization state and status of this protocol. Distribution >of this memo is unlimited. > >This announcement is sent to the IETF list and the RFC-DIST list. >Requests to be added to or deleted from the IETF distribution list >should be sent to IETF-REQUEST(a)IETF.ORG. Requests to be >added to or deleted from the RFC-DIST distribution list should >be sent to RFC-DIST-REQUEST(a)RFC-EDITOR.ORG. > >Details on obtaining RFCs via FTP or EMAIL may be obtained by sending >an EMAIL message to rfc-info(a)RFC-EDITOR.ORG with the message body >help: ways_to_get_rfcs. For example: > > To: rfc-info(a)RFC-EDITOR.ORG > Subject: getting rfcs > > help: ways_to_get_rfcs > >Requests for special distribution should be addressed to either the >author of the RFC in question, or to RFC-Manager(a)RFC-EDITOR.ORG. Unless >specifically noted otherwise on the RFC itself, all RFCs are for >unlimited distribution.echo >Submissions for Requests for Comments should be sent to >RFC-EDITOR(a)RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC >Authors, for further information. > > >Joyce K. Reynolds and Alegre Ramos >USC/Information Sciences Institute > >... > >Below is the data which will enable a MIME compliant Mail Reader >implementation to automatically retrieve the ASCII version >of the RFCs. >Content-Type: text/plain >Content-ID: <981203163602.RFC(a)RFC-EDITOR.ORG> > >RETRIEVE: rfc >DOC-ID: rfc2470 > ><ftp://ftp.isi.edu/in-notes/rfc2470.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

Fw: (IPng 6839) RFC 2471 on IPv6 Testing Address Allocation
by Thomas Trede 08 Dec '98

08 Dec '98

FYI. Regards, Thomas Trede -----Original Message----- From: RFC Editor (by way of Bob Hinden <hinden(a)iprg.nokia.com>) <rfc-ed(a)ISI.EDU> To: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Date: Freitag, 4. Dezember 1998 03:23 Subject: (IPng 6839) RFC 2471 on IPv6 Testing Address Allocation > >A new Request for Comments is now available in online RFC libraries. > > > RFC 2471: > > Title: IPv6 Testing Address Allocation > Author(s): R. Hinden, R. Fink, J. Postel (deceased) > Status: Experimental > Date: December 1998 > Mailbox: hinden(a)ipsilon.com, rlfink(a)lbl.gov > Pages: 5 > Characters: 8031 > Obsoletes: 1897 > I-D Tag: draft-ietf-ipngwg-testv2-addralloc-01.txt > > > URL: ftp://ftp.isi.edu/in-notes/rfc2471.txt > > >This document describes an allocation plan for IPv6 addresses to be >used in testing IPv6 prototype software. These addresses are >temporary and will be reclaimed in the future. Any IPv6 system using >these addresses will have to renumber at some time in the future. >These addresses will not to be routable in the Internet other than >for IPv6 testing. > >This document is a product of the IPNG Working Group of the IETF. > >This memo defines an Experimental Protocol for the Internet community. >It does not specify an Internet standard of any kind. Discussion and >suggestions for improvement are requested. Distribution of this memo >is unlimited. > >This announcement is sent to the IETF list and the RFC-DIST list. >Requests to be added to or deleted from the IETF distribution list >should be sent to IETF-REQUEST(a)IETF.ORG. Requests to be >added to or deleted from the RFC-DIST distribution list should >be sent to RFC-DIST-REQUEST(a)RFC-EDITOR.ORG. > >Details on obtaining RFCs via FTP or EMAIL may be obtained by sending >an EMAIL message to rfc-info(a)RFC-EDITOR.ORG with the message body >help: ways_to_get_rfcs. For example: > > To: rfc-info(a)RFC-EDITOR.ORG > Subject: getting rfcs > > help: ways_to_get_rfcs > >Requests for special distribution should be addressed to either the >author of the RFC in question, or to RFC-Manager(a)RFC-EDITOR.ORG. Unless >specifically noted otherwise on the RFC itself, all RFCs are for >unlimited distribution.echo >Submissions for Requests for Comments should be sent to >RFC-EDITOR(a)RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC >Authors, for further information. > > >Joyce K. Reynolds and Alegre Ramos >USC/Information Sciences Institute > >... > >Below is the data which will enable a MIME compliant Mail Reader >implementation to automatically retrieve the ASCII version >of the RFCs. >Content-Type: text/plain >Content-ID: <981203163906.RFC(a)RFC-EDITOR.ORG> > >RETRIEVE: rfc >DOC-ID: rfc2471 > ><ftp://ftp.isi.edu/in-notes/rfc2471.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

Fw: (IPng 6837) RFC 2450 on Proposed TLA and NLA Assignment Rules
by Thomas Trede 08 Dec '98

08 Dec '98

FYI. Regards, Thomas Trede -----Original Message----- From: RFC Editor (by way of Bob Hinden <hinden(a)iprg.nokia.com>) <rfc-ed(a)ISI.EDU> To: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Date: Freitag, 4. Dezember 1998 02:53 Subject: (IPng 6837) RFC 2450 on Proposed TLA and NLA Assignment Rules > >A new Request for Comments is now available in online RFC libraries. > > > Title: Proposed TLA and NLA Assignment Rules > Author(s): R. Hinden > Status: Informational > Date: December 1998 > Mailbox: hinden(a)iprg.nokia.com > Pages: 11 > Characters: 24484 > Updates/Obsoletes/See Also: None > I-D Tag: draft-ietf-ipngwg-tla-assignment-05.txt > > URL: ftp://ftp.isi.edu/in-notes/rfc2450.txt > > >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 document is a product of the IPNG Working Group of the IETF. > >This memo provides information for the Internet community. It does >not specify an Internet standard of any kind. Distribution of this >memo is unlimited. > >This announcement is sent to the IETF list and the RFC-DIST list. >Requests to be added to or deleted from the IETF distribution list >should be sent to IETF-REQUEST(a)IETF.ORG. Requests to be >added to or deleted from the RFC-DIST distribution list should >be sent to RFC-DIST-REQUEST(a)RFC-EDITOR.ORG. > >Details on obtaining RFCs via FTP or EMAIL may be obtained by sending >an EMAIL message to rfc-info(a)RFC-EDITOR.ORG with the message body >help: ways_to_get_rfcs. For example: > > To: rfc-info(a)RFC-EDITOR.ORG > Subject: getting rfcs > > help: ways_to_get_rfcs > >Requests for special distribution should be addressed to either the >author of the RFC in question, or to RFC-Manager(a)RFC-EDITOR.ORG. Unless >specifically noted otherwise on the RFC itself, all RFCs are for >unlimited distribution.echo >Submissions for Requests for Comments should be sent to >RFC-EDITOR(a)RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC >Authors, for further information. > > >Joyce K. Reynolds and Alegre Ramos >USC/Information Sciences Institute > >... > >Below is the data which will enable a MIME compliant Mail Reader >implementation to automatically retrieve the ASCII version >of the RFCs. >Content-Type: text/plain >Content-ID: <981203162857.RFC(a)RFC-EDITOR.ORG> > >RETRIEVE: rfc >DOC-ID: rfc2450 > ><ftp://ftp.isi.edu/in-notes/rfc2450.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

Fw: (IPng 6836) RFC 2467 on IPv6 over FDDI
by Thomas Trede 08 Dec '98

08 Dec '98

FYI. Regards, Thomas Trede -----Original Message----- From: RFC Editor (by way of Bob Hinden <hinden(a)iprg.nokia.com>) <rfc-ed(a)ISI.EDU> To: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Date: Freitag, 4. Dezember 1998 02:53 Subject: (IPng 6836) RFC 2467 on IPv6 over FDDI > >A new Request for Comments is now available in online RFC libraries. > > > RFC 2467: > > Title: Transmission of IPv6 Packets over FDDI Networks > Author(s): M. Crawford > Status: Proposed Standard > Date: December 1998 > Mailbox: crawdad(a)fnal.gov > Pages: 9 > Characters: 16028 > Obsoletes: 2019 > I-D Tag: draft-ietf-ipngwg-trans-fddi-net-05.txt > > > URL: ftp://ftp.isi.edu/in-notes/rfc2467.txt > > >This document specifies the frame format for transmission of IPv6 >packets and the method of forming IPv6 link-local addresses and >statelessly autoconfigured addresses on FDDI networks. It also >specifies the content of the Source/Target Link-layer Address option >used in Router Solicitation, Router Advertisement, Neighbor >Solicitation, Neighbor Advertisement and Redirect messages when >those messages are transmitted on an FDDI network. > >This document is a product of the IPNG Working Group of the IETF. > >This is now a Proposed Standard Protocol. > >This document specifies an Internet standards track protocol for >the Internet community, and requests discussion and suggestions >for improvements. Please refer to the current edition of the >"Internet Official Protocol Standards" (STD 1) for the >standardization state and status of this protocol. Distribution >of this memo is unlimited. > >This announcement is sent to the IETF list and the RFC-DIST list. >Requests to be added to or deleted from the IETF distribution list >should be sent to IETF-REQUEST(a)IETF.ORG. Requests to be >added to or deleted from the RFC-DIST distribution list should >be sent to RFC-DIST-REQUEST(a)RFC-EDITOR.ORG. > >Details on obtaining RFCs via FTP or EMAIL may be obtained by sending >an EMAIL message to rfc-info(a)RFC-EDITOR.ORG with the message body >help: ways_to_get_rfcs. For example: > > To: rfc-info(a)RFC-EDITOR.ORG > Subject: getting rfcs > > help: ways_to_get_rfcs > >Requests for special distribution should be addressed to either the >author of the RFC in question, or to RFC-Manager(a)RFC-EDITOR.ORG. Unless >specifically noted otherwise on the RFC itself, all RFCs are for >unlimited distribution.echo >Submissions for Requests for Comments should be sent to >RFC-EDITOR(a)RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC >Authors, for further information. > > >Joyce K. Reynolds and Alegre Ramos >USC/Information Sciences Institute > >... > >Below is the data which will enable a MIME compliant Mail Reader >implementation to automatically retrieve the ASCII version >of the RFCs. >Content-Type: text/plain >Content-ID: <981203163158.RFC(a)RFC-EDITOR.ORG> > >RETRIEVE: rfc >DOC-ID: rfc2467 > ><ftp://ftp.isi.edu/in-notes/rfc2467.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

Fw: (IPng 6832) RFC 2452 on TCP MIB for IPv6
by Thomas Trede 08 Dec '98

08 Dec '98

FYI. Regards, Thomas Trede -----Original Message----- From: RFC Editor (by way of Bob Hinden <hinden(a)iprg.nokia.com>) <rfc-ed(a)ISI.EDU> To: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Date: Freitag, 4. Dezember 1998 02:04 Subject: (IPng 6832) RFC 2452 on TCP MIB for IPv6 > >A new Request for Comments is now available in online RFC libraries. > > > RFC 2452: > > Title: IP Version 6 Management Information Base > for the Transmission Control Protocol > Author(s): M. Daniele > Status: Proposed Standard > Date: December 1998 > Mailbox: daniele(a)zk3.dec.com > Pages: 10 > Characters: 19070 > Updates/Obsoletes/See Also: None > I-D Tag: draft-ietf-ipngwg-ipv6-tcp-mib-02.txt > > > URL: ftp://ftp.isi.edu/in-notes/rfc2452.txt > > >This memo defines an experimental portion of the Management >Information Base (MIB) for use with network management protocols in >IPv6-based internets. > >This document is a product of the IPNG Working Group of the IETF. > >This is now a Proposed Standard Protocol. > >This document specifies an Internet standards track protocol for >the Internet community, and requests discussion and suggestions >for improvements. Please refer to the current edition of the >"Internet Official Protocol Standards" (STD 1) for the >standardization state and status of this protocol. Distribution >of this memo is unlimited. > >This announcement is sent to the IETF list and the RFC-DIST list. >Requests to be added to or deleted from the IETF distribution list >should be sent to IETF-REQUEST(a)IETF.ORG. Requests to be >added to or deleted from the RFC-DIST distribution list should >be sent to RFC-DIST-REQUEST(a)RFC-EDITOR.ORG. > >Details on obtaining RFCs via FTP or EMAIL may be obtained by sending >an EMAIL message to rfc-info(a)RFC-EDITOR.ORG with the message body >help: ways_to_get_rfcs. For example: > > To: rfc-info(a)RFC-EDITOR.ORG > Subject: getting rfcs > > help: ways_to_get_rfcs > >Requests for special distribution should be addressed to either the >author of the RFC in question, or to RFC-Manager(a)RFC-EDITOR.ORG. Unless >specifically noted otherwise on the RFC itself, all RFCs are for >unlimited distribution.echo >Submissions for Requests for Comments should be sent to >RFC-EDITOR(a)RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC >Authors, for further information. > > >Joyce K. Reynolds and Alegre Ramos >USC/Information Sciences Institute > >... > >Below is the data which will enable a MIME compliant Mail Reader >implementation to automatically retrieve the ASCII version >of the RFCs. >Content-Type: text/plain >Content-ID: <981203122519.RFC(a)RFC-EDITOR.ORG> > >RETRIEVE: rfc >DOC-ID: rfc2452 > ><ftp://ftp.isi.edu/in-notes/rfc2452.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