- ipv6-wg - mailman.ripe.net

Fw: W.G. Last Call on "Transmission of IPv6 Packets over IEEE 1394 Networks"
by Thomas Trede 29 Nov '00

29 Nov '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: "Bob Hinden" <hinden(a)iprg.nokia.com> To: <ipng(a)sunroof.eng.sun.com> Sent: Wednesday, November 29, 2000 1:02 AM Subject: W.G. Last Call on "Transmission of IPv6 Packets over IEEE 1394 Networks" > This is a IPng working group last call for comments on advancing the > following document as a Proposed Standard: > > Title : Transmission of IPv6 Packets over IEEE 1394 Networks > Author(s) : K. Fujisawa, A. Onoe > Filename : draft-ietf-ipngwg-1394-00.txt > Pages : 7 > Date : 14-Nov-00 > > Please send substantive comments to the ipng mailing list, and minor > editorial comments to the authors. This last call period will end two > week from today on December 12, 2000. > > Bob Hinden / Steve Deering > > -------------------------------------------------------------------- > 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: I-D ACTION:draft-haberman-ipngwg-auto-prefix-00.txt]
by Thomas Trede 27 Nov '00

27 Nov '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: "Brian Haberman" <haberman(a)nortelnetworks.com> To: "IPng Mailing List" <ipng(a)sunroof.eng.sun.com> Sent: Monday, November 27, 2000 3:19 PM Subject: [Fwd: I-D ACTION:draft-haberman-ipngwg-auto-prefix-00.txt] > All, > The following is an individual submission discussing automated > prefix delegation. The basic idea is that routers can request a prefix > to use within a network. Right now, we restrict its use to leaf > networks, but are working on expanding it. Comments welcome. > > Regards, > Brian > > Internet-Drafts(a)ietf.org wrote: > > > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > > > Title : Automatic Prefix Delegation Protocol for Internet > > Protocol Version 6 (IPv6) > > Author(s) : B. Haberman, J. Martin > > Filename : draft-haberman-ipngwg-auto-prefix-00.txt > > Pages : 11 > > Date : 22-Nov-00 > > > > The expansion of the IP address space provided by IPv6 makes it both > > possible and reasonable to allocate entire subnets to environments > > that had been previously limited to a few individual IP addresses. > > Other protocols such as Neighbor Discovery and Stateless Address > > Autoconfiguration allow hosts within those subnets to be > > automatically configured. The router between this subnet and the > > upstream world requires just one more piece to make this process > > automatic, a network prefix. > > This document describes a mechanism for the automated delegation of > > an IPv6 network prefix. It allows routers to request a specific size > > prefix and inform the upstream router of the routing protocols of > > which it is capable. Upon authorizing the request the delegating > > router then returns a prefix, the desired routing protocol, and a > > lifetime for the use of the prefix. > > > > A URL for this Internet-Draft is: > > http://www.ietf.org/internet-drafts/draft-haberman-ipngwg-auto-prefix-00.txt > > > > Internet-Drafts are also 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-haberman-ipngwg-auto-prefix-00.txt". > > > > A list of Internet-Drafts directories can be found in > > http://www.ietf.org/shadow.html > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > Internet-Drafts can also be obtained by e-mail. > > > > Send a message to: > > mailserv(a)ietf.org. > > In the body type: > > "FILE /internet-drafts/draft-haberman-ipngwg-auto-prefix-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. > > > ------------------------------------------------------------------------ > -------------------------------------------------------------------- > 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: I-D ACTION:draft-ietf-ipngwg-prefix-rr-disc-00.txt
by Thomas Trede 27 Nov '00

27 Nov '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: <Internet-Drafts(a)ietf.org> To: <IETF-Announce: ;> Cc: <ipng(a)sunroof.eng.sun.com> Sent: Saturday, November 25, 2000 12:56 AM Subject: I-D ACTION:draft-ietf-ipngwg-prefix-rr-disc-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 : Discovery of Resource Records Designating IPv6 Address > prefixes > Author(s) : M. Crawford > Filename : draft-ietf-ipngwg-prefix-rr-disc-00.txt > Pages : 4 > Date : 22-Nov-00 > > The A6 resource record type [A6] was introduced to store IPv6 > addresses in a manner which facilitates prefix changes and > assignment of addresses from multiple prefixes. In order to allow > use of dynamic DNS updates while still respecting whatever prefix > hierarchy may be in use in a site's > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-prefix-rr-disc-00.txt > > Internet-Drafts are also 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-prefix-rr-disc-00.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv(a)ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-ipngwg-prefix-rr-disc-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

Fw: Last Call: IP Version 6 Addressing Architecture to Draft Standard
by Thomas Trede 23 Nov '00

23 Nov '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: "The IESG" <iesg-secretary(a)ietf.org> To: <IETF-Announce: ;> Cc: <ipng(a)sunroof.eng.sun.com> Sent: Wednesday, November 22, 2000 9:22 PM Subject: Last Call: IP Version 6 Addressing Architecture to Draft Standard > > The IESG has received a request from the IPNG Working Group to consider > IP Version 6 Addressing Architecture > <draft-ietf-ipngwg-addr-arch-v3-02.txt> as a Draft Standard, replacing > RFC2373, currently a Proposed Standard. > > The IESG plans to make a decision in the next few weeks, and solicits7 > final comments on this action. Please send any comments to the > iesg(a)ietf.org or ietf(a)ietf.org mailing lists by December 6, 2000. > > Files can be obtained via > http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-addr-arch-v3-02.txt > > The Implementation Report can be found at > http://www.ietf.org/IESG/Implementations/address-architecture.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: I-D ACTION:draft-ietf-ion-ipv6-ind-05.txt
by Thomas Trede 22 Nov '00

22 Nov '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: <Internet-Drafts(a)ietf.org> To: <IETF-Announce: ;> Cc: <ipng(a)sunroof.eng.sun.com> Sent: Wednesday, November 22, 2000 12:03 PM Subject: I-D ACTION:draft-ietf-ion-ipv6-ind-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 : Extensions to IPv6 Neighbor Discovery for Inverse > Discovery Specification > Author(s) : A. Conta > Filename : draft-ietf-ion-ipv6-ind-05.txt > Pages : 22 > Date : 21-Nov-00 > > This memo describes extensions to the IPv6 Neighbor Discovery that > allow a node to determine and advertise an IPv6 address corresponding > to a given link-layer address. These extensions are called Inverse > Neighbor Discovery. The Inverse Neighbor Discovery (IND) was > originally developed for Frame Relay networks, but may also apply to > other networks with similar behavior. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ion-ipv6-ind-05.txt > > Internet-Drafts are also 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-ion-ipv6-ind-05.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv(a)ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-ion-ipv6-ind-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

Fw: I-D ACTION:draft-kitamura-ipv6-record-route-00.txt
by Thomas Trede 20 Nov '00

20 Nov '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: <Internet-Drafts(a)ietf.org> To: <IETF-Announce: ;> Cc: <ipng(a)sunroof.eng.sun.com> Sent: Monday, November 20, 2000 12:16 PM Subject: I-D ACTION:draft-kitamura-ipv6-record-route-00.txt > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > > Title : Record Route for IPv6 (RR6) Hop-by-Hop Option > Extension > Author(s) : H. Kitamura > Filename : draft-kitamura-ipv6-record-route-00.txt > Pages : 15 > Date : 17-Nov-00 > > This document proposes a 'Record Route for IPv6 (RR6)' mechanism. It > is composed of one new IPv6 hop-by-hop option (RR6 option) extension. > The RR6 mechanism is redesigned to establish an optimized record > route mechanism for IPv6. Two types of new features are introduced. > 1. In order to prevent scalability problems and to make the mechanism > flexible, the beginning and ending points of the data recording range > are controlled by using their specifiers. > 2. In order to record long IPv6 addresses efficiently, a simple > address compression method is introduced. Since the compression is > achieved by utilizing characteristics of recorded IPv6 addresses > effectively, the mechanism is efficient and optimized for IPv6. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-kitamura-ipv6-record-route-00.txt > > Internet-Drafts are also 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-kitamura-ipv6-record-route-00.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv(a)ietf.org. > In the body type: > "FILE /internet-drafts/draft-kitamura-ipv6-record-route-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

Fw: I-D ACTION:draft-ietf-ipngwg-1394-00.txt
by Thomas Trede 15 Nov '00

15 Nov '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: <Internet-Drafts(a)ietf.org> To: <IETF-Announce: ;> Cc: <ipng(a)sunroof.eng.sun.com> Sent: Wednesday, November 15, 2000 12:40 PM Subject: I-D ACTION:draft-ietf-ipngwg-1394-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 : Transmission of IPv6 Packets over IEEE 1394 Networks > Author(s) : K. Fujisawa, A. Onoe > Filename : draft-ietf-ipngwg-1394-00.txt > Pages : 7 > Date : 14-Nov-00 > > IEEE Std 1394-1995 is a standard for a High Performance Serial Bus. > This document describes the frame format for transmission of IPv6 > [IPV6] packets and the method of forming IPv6 link-local addresses > and statelessly autoconfigured addresses on IEEE1394 networks. > It also describes the content of the Source/Target Link-layer Address > option used in Neighbor Discovery [DISC] when the messages are > transmitted on an IEEE1394 network. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-1394-00.txt > > Internet-Drafts are also 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-1394-00.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv(a)ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-ipngwg-1394-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

Fw: MLDv3 - Internet Draft
by Thomas Trede 09 Nov '00

09 Nov '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: "Vida Rolland" <Rolland.Vida(a)lip6.fr> To: <ipng(a)sunroof.eng.sun.com>; <ssm-interest(a)external.cisco.com>; "Supratik Bhattacharyya" <supratik(a)sprintlabs.com> Sent: Wednesday, November 08, 2000 6:30 PM Subject: MLDv3 - Internet Draft > Dear All, > > The revised IPng Working Group Charter published on the 5th of October > on the mailing list of the IPng WG contained a call for contribution on > "Extending MLD to include functionality of IGMPv3". > > Here is the abstract of an Internet Draft proposal, called "Multicast > Listener Discovery Version 3 (MLDv3) for IPv6" > (<draft-vida-mld-v3-00.txt>) > > ************* > Abstract: > > This document specifies Version 3 of the Multicast Listener Discovery > protocol, MLDv3. MLD is the protocol used by an IPv6 router to > discover the presence of multicast listeners (that is, nodes wishing > to receive multicast packets) on its directly attached links, and to > discover specifically which multicast addresses are of interest to > those neighboring nodes. > > MLDv3 is derived from version 3 of IPv4's Internet Group Management > Protocol, IGMPv3. Compared to the previous version, MLDv3 adds > support for "source filtering", that is, the ability for a node to > report interest in listening to packets *only* from specific source > addresses, or from *all but* specific source addresses, sent to a > particular multicast address. That information may be used by > multicast routing protocols to avoid delivering multicast packets > from specific sources to links where there are no interested > listeners. When compared to IGMPv3, one important difference > to note is that MLDv3 uses ICMPv6 (IP Protocol 58) message > types, rather than IGMP (IP Protocol 2) message types. > > ************ > > The full text of the draft can be found at: > http://www-rp.lip6.fr/~vida/draft-vida-mld-v3-00.txt > > We welcome any comments or suggestions on the text. > > Best regards, > > Rolland Vida, > LIP6, Paris, France. > > ----------------------------------------------------------------------- > "Not everything that can be counted counts, and not everything that > counts can be counted. " - Albert Einstein > Rolland Vida > Universite Paris VI "Pierre et Marie Curie" tel: +33 (0)144 277 126 > Laboratoire LIP6 - CNRS, C669 fax: +33 (0)144 277 495 > 8, Rue de Capitaine Scott, 75015, Paris mailto:vida@rp.lip6.fr > ----------------------------------------------------------------------- > > > > > > > -------------------------------------------------------------------- > 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: I-D ACTION:draft-ietf-ipngwg-rfc2292bis-02.txt
by Thomas Trede 08 Nov '00

08 Nov '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: <Internet-Drafts(a)ietf.org> To: <IETF-Announce: ;> Cc: <ipng(a)sunroof.eng.sun.com> Sent: Wednesday, November 08, 2000 11:59 AM Subject: I-D ACTION:draft-ietf-ipngwg-rfc2292bis-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 : Advanced Sockets API for IPv6 > Author(s) : R. Stevens, M. Thomas, E. Nordmark > Filename : draft-ietf-ipngwg-rfc2292bis-02.txt > Pages : 74 > Date : 07-Nov-00 > > A separate specification [RFC-2553] contain changes to the sockets > API to support IP version 6. Those changes are for TCP and UDP-based > applications and will support most end-user applications in use > today: Telnet and FTP clients and servers, HTTP clients and servers, > and the like. > But another class of applications exists that will also be run under > IPv6. We call these 'advanced' applications and today this includes > programs such as Ping, Traceroute, routing daemons, multicast routing > daemons, router discovery daemons, and the like. The API feature > typically used by these programs that make them 'advanced' is a raw > socket to access ICMPv4, IGMPv4, or IPv4, along with some knowledge > of the packet header formats used by these protocols. To provide > portability for applications that use raw sockets under IPv6, some > standardization is needed for the advanced API features. > There are other features of IPv6 that some applications will need to > access: interface identification (specifying the outgoing interface > and determining the incoming interface) and IPv6 extension headers > that are not addressed in [RFC-2553]: The Routing header (source > routing), Hop-by-Hop options, and Destination options. This document > provides API access to these features too. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-rfc2292bis-02.txt > > Internet-Drafts are also 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-rfc2292bis-02.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv(a)ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-ipngwg-rfc2292bis-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

Fw: Protocol Action: IP Version 6 Management Information Base for the Multicast Listener Discovery Protocol to Proposed Standard
by Thomas Trede 28 Oct '00

28 Oct '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: "The IESG" <iesg-secretary(a)ietf.org> To: <IETF-Announce: ;> Cc: "RFC Editor" <rfc-editor(a)isi.edu>; "IANA" <iana(a)iana.org>; "Internet Architecture Board" <iab(a)isi.edu>; <ipng(a)sunroof.eng.sun.com> Sent: Friday, October 27, 2000 6:55 PM Subject: Protocol Action: IP Version 6 Management Information Base for the Multicast Listener Discovery Protocol to Proposed Standard > > > The IESG has approved the Internet-Draft 'IP Version 6 Management > Information Base for the Multicast Listener Discovery Protocol' > <draft-ietf-ipngwg-mld-mib-05.txt> as a Proposed Standard. This > document is the product of the IPNG Working Group. The IESG contact > persons are Erik Nordmark and Thomas Narten. > > > > > Technical Summary > > This document defines a portion of the Management Information Base > (MIB) for use with network management protocols in Internet Protocol > Version 6 internets. Specifically, this document is the MIB module > that defines managed objects for implementations of the Multicast > Listener Discovery Protocol (RFC2710). > > Working Group Summary > > There was consensus within the WG for this document, and no issues > were raised during IETF Last Call. > > Protocol Quality > > This protocol has been reviewed for the IESG by Juergen Schoenwaelder > 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