- ipv6-wg - mailman.ripe.net

draft minutes of the IPv6 wg at RIPE33
by David Kessens 28 May '99

28 May '99

Hi, Please see below for the minutes of our session. I would like to thank Petra Zeidler for being so kind to take the minutes. Please send minor corrections directly to me. I will declare the minutes with corrections final when no major comments are received in two weeks from now. David K. --- ----- Forwarded message from "S.P.Zeidler" <spz(a)serpens.de> ----- Minutes of the IPv6 WG meeting at RIPE 33 Agenda: - Administrative Stuff Scribe is Petra Zeidler Agenda bashing was rather bashful (no changes) - Status of 6BONE (presented by David Kessens) http://www.ip.qwest.net/~david/presentations/ Questions: 1) what about efforts to harden the 6BONE? was being discussed at the last IETF, see minutes of that 2) what's the status of 6REN? 6REN was being in full progress, and one should contact Bob Fink for specifics - IPv6 in practice (presented by Jan Czmok) http://engr.gigabell.net/ipv6/pres/ Questions: 1) what was the difficulty with multi-homing? unresolved issue as to how to do that with customer-type address ranges 2) why was porting applications to IPv6 so important? "Bump-in-the-stack" exists, but one reason to go to IPv6 right now are the IPv6 network client configuration niceties 3) there are reverse DNS tools for IPv6, why was this considered a problem? The current tools need too much know-how, they're not "customer-safe" 4) which applications needed porting the most? those that users won't want to do without in the context of using the Internet, i.e. mainly web browsers 5) (Comment, rather) IPv6 over IPv4 with dynamically assigned addresses wasn't a problem any more with the availability of the tunnel brokers. - European developments and initaitives regarding IPv6 (audience) - Bernard Tuy was working on IPv6 over ATM and can be contacted regarding that - Wilfried Woeber reported having held a presentation about a test program lately. An IPv6 native backbone in Europe would be desirable, one should look out for 6EIX and also see the developments until September. Deploying IPv6 in a production environment would be more an administrative than a technical problem. - Francis Dupont asked who actually used IPv4 non-tunneled multicast and if the current lack of IPv6 multicast capabilities in the current IPv6 Cisco IOS was perceived as a problem - IPv6 should be on the terminal-LAN of RIPE 34 as well - IPv6 allocation progress (presented by Miriam Kuehne) see slides for the talk Discussion: - the documentation mentions default-free zones, a definition ought to be added - Q: Allocations are based on track record, why not use IPv4 address usage track record? A: the two need not necessarily compare - Q: why mention the future possible end of this Sub-TLA-space in the document? A: Decision processes slow down, one should be kept aware that new provisions will have to have been taken by then - Q: what is the term of the policy? A: it will be under constant review - Q: how would one get IPv6 customers or peerings without address space? A: in the beginning one'd have gotten space by the bootstrap procedures, or via 6BONE, later through ones upstream - Q: are the numbers (>= 3 peerings, >= 42 customers) ok? A: there was no dispute that 42 was the answer - Q: why have 2 valid reasons to get space currently, wouldn't the latter suffice? A: it should give those considering a request a frame of for what size a Sub-TLA would be seen appropriate; also, it's a heirloom from the ARIN allocation policy - a rewording of "immediate intent" was suggested, as it sounded none too realistic - Q: is further delay in the accepting of the policies expected? A: Not really, there were unwritten parts, but that shouldn't stop starting out. - Q: are there essential parts that should go in before this becomes policy? A: there were no objections to go ahead with the current state of the document - Q: was there input on the missing sections? A: - - address space not being owned by the assignee ought to be worded more clearly - "you might be required to renumber in the future" was very vague, suggestion to clarify that to: "in order to continue taking part in the Internet a renumbering may be neccessary for technical reasons". - the policy should reference the appropriate IETF documents - Q: why bother to slow-start S-TLAs? A: in order to get a range of prefix-lengths - Q: how long will the period to comment the policy be? A: not much longer - this policy is a common product of all the RIRs and will be shared Action points: 33.1 RIPE NCC and the other regional registries will finalize the allocation draft document and start allocating IPv6 addresses as soon as possible ----------------------------------------------------------------------

1 0

Fw: (IPng 7550) I-D ACTION:draft-ietf-ipngwg-url-literal-00.txt
by Thomas Trede 25 May '99

25 May '99

FYI. Regards, Thomas Trede -----Original Message----- From: Internet-Drafts(a)ietf.org <Internet-Drafts(a)ietf.org> To: IETF-Announce: ; <IETF-Announce: ;> Cc: ipng(a)sunroof.eng.sun.com <ipng(a)sunroof.eng.sun.com> Date: Mittwoch, 19. Mai 1999 15:15 Subject: (IPng 7550) I-D ACTION:draft-ietf-ipngwg-url-literal-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 : Preferred Format for Literal IPv6 Addresses in URL's > Author(s) : B. Hinden, B. Carpenter > Filename : draft-ietf-ipngwg-url-literal-00.txt > Pages : 3 > Date : 18-May-99 > >This document defines the preferred format for literal IPv6 Addresses >in URL's for implementation in World Wide Web browsers. This format >has been implemented in the IPv6 versions of several widely deployed >browsers including Microsoft Internet Explorer and Mozilla. > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-url-literal-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-url-literal-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-url-literal-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. > ENCODING mime FILE /internet-drafts/draft-ietf-ipngwg-url-literal-00.txt

1 0

Presentation of RIPE33 / Hands on Practical Experience
by Jan Ahrent Czmok 14 May '99

14 May '99

Hi all! My slides from the Presentation at RIPE 33 are now available under http://engr.gigabell.net/ipv6/pres/ Greetings Jan Czmok Gigabell AG Senior Network Engineer

1 0

MPLS99 conference
by Peter Lewis 27 Apr '99

27 Apr '99

The future is now. It is called MPLS. Overview of the capacity of MPLS in terms of traffic engineering, VPNs, QoS for an IP backbone. What will become of ATM? European conference in June: MPLS 99 For more details, please go to : http://www.upperside.fr/bampls.htm Thanks Peter Lewis

1 0

IPv6 assignment and Allocation Policy Document (fwd)
by Rute Sofia 27 Apr '99

27 Apr '99

I've read the IPv6 Assignment and Allocation Policy Document and think it is quite resonable now :-), at least for what concerns the initial deployment. However, I have some considerations: in point 4.2.2, "Criteria for sub-TLA Allocations in Transitional Bootstrap phase", point a. states that "the requesting organization's network...with at least three other public AS in the default-free zone". What is meant by "default-free zone"? I also think that it is of major importance in IPv6 to have section 6., DNS and Reverse Address Mapping in the initial deployment document. There is also the question of the now pseudo-TLA: even though I suppose that most of us are under the conditions of point 4.2.1, nothing is said about pseudo-TLA. Do we have to request for a sub-TLA again? Or what will be needed is only to renumber? Thanks, Rute Sofia

1 0

(IPng 7431) I-D ACTION:draft-ietf-msdp-mibdraft--00.txt (fwd)
by Thomas Trede 27 Apr '99

27 Apr '99

FYI. Regards, Thomas Trede ---------- Forwarded message ---------- Date: Thu, 22 Apr 1999 09:18:10 -0400 From: Internet-Drafts(a)ietf.org To: IETF-Announce: ; Cc: ipng(a)sunroof.eng.sun.com Subject: (IPng 7431) I-D ACTION:draft-ietf-msdp-mibdraft--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 : Multicast Source Discovery protocol MIB Author(s) : B. Fenner, D. Thaler Filename : draft-ietf-msdp-mibdraft-00.txt Pages : 22 Date : 21-Apr-99 This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing Multicast Source Discovery Protocol (MSDP) [17] speakers. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-msdp-mibdraft--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-msdp-mibdraft--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-msdp-mibdraft--00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.

1 0

(IPng 7430) I-D ACTION:draft-ietf-ion-nhrp-mib-06.txt (fwd)
by Thomas Trede 27 Apr '99

27 Apr '99

FYI. Regards, Thomas Trede ---------- Forwarded message ---------- Date: Thu, 22 Apr 1999 09:18:01 -0400 From: Internet-Drafts(a)ietf.org To: IETF-Announce: ; Cc: ipng(a)sunroof.eng.sun.com Subject: (IPng 7430) I-D ACTION:draft-ietf-ion-nhrp-mib-06.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 : Definitions of Managed Objects for the NBMA Next Hop Resolution Protocol (NHRP) Author(s) : M. Greene, J. Cucchiara, J. Luciani Filename : draft-ietf-ion-nhrp-mib-06.txt Pages : 67 Date : 21-Apr-99 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for the Next Hop Resolution Protocol (NHRP) as defined in RFC 2332. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ion-nhrp-mib-06.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-nhrp-mib-06.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-nhrp-mib-06.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

draft agenda (v1) for IPv6 working group RIPE33
by David Kessens 27 Apr '99

27 Apr '99

Hi, Below follows the first version of the IPv6 wg agenda. Note that on tuesday, we have scheduled, in addition to the regular wg session on wednesday, a tutorial about IPv6 (see the RIPE website for details). I anticipate that we will (and should) use most of our time for discussing the new IPv6 allocation draft. I would like to advise everybody to read the document: http://www.ripe.net/lir/registries/ipv6.html in order to allow us to have a focussed discussion. Note that we can give the most valuable input to the registries if we can come up with alternatives for pieces that we don't like, instead of telling them that we don't like something. Things to keep in mind when coming up with alternate proposals are: routability, conservation, verification of criteria, administrative overhead. Please let me know if you have other items that need to be discussed, David K. --- Proposed Agenda (draft v1) for the IPv6 Working Group Meeting RIPE33, May 1999, Vienna A. Administrative stuff (David Kessens) - appointment of scribe - agenda bashing B. Status of 6bone (David Kessens) C. IPv6 in practice (Jan Czmok) D. European developments/initiatives regarding IPv6 (input from the audience) E. IPv6 allocation progress (RIPE NCC): http://www.ripe.net/lir/registries/ipv6.html Z. AOB ---

1 0

(IPng 7426) Request to Advance "IPv6 Jumbograms" (fwd)
by Thomas Trede 21 Apr '99

21 Apr '99

FYI. Regards, Thomas Trede ---------- Forwarded message ---------- Date: Wed, 21 Apr 1999 08:58:54 -0700 From: Bob Hinden <hinden(a)iprg.nokia.com> To: narten(a)raleigh.ibm.com, nordmark(a)eng.sun.com Cc: scoya(a)cnri.reston.va.us, deering(a)cisco.com, ipng(a)sunroof.eng.sun.com Subject: (IPng 7426) Request to Advance "IPv6 Jumbograms" Erik, Thomas, The chairs of the IP Next Generation working group, on behalf of the working group, request that the following document be published as a Proposed Standard: Title : IPv6 Jumbograms Author(s) : D. Borman, S. Deering, R. Hinden Filename : draft-ietf-ipngwg-jumbograms-00.txt Pages : 8 Date : 01-Mar-99 A working group last call for this document was completed on April 7, 1999. Bob Hinden / Steve Deering IPng Working Group Co-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 7427) Request to Advance "Router Renumbering for IPv6" (fwd)
by Thomas Trede 21 Apr '99

21 Apr '99

FYI. Regards, Thomas Trede ---------- Forwarded message ---------- Date: Wed, 21 Apr 1999 09:03:02 -0700 From: Bob Hinden <hinden(a)iprg.nokia.com> To: narten(a)raleigh.ibm.com, nordmark(a)eng.sun.com Cc: scoya(a)cnri.reston.va.us, deering(a)cisco.com, ipng(a)sunroof.eng.sun.com Subject: (IPng 7427) Request to Advance "Router Renumbering for IPv6" Erik, Thomas, The chairs of the IP Next Generation working group, on behalf of the working group, request that the following document be published as a Proposed Standard: Title : Router Renumbering for IPv6 Author(s) : M. Crawford Filename : draft-ietf-ipngwg-router-renum-08.txt Pages : 30 Date : 01-Mar-99 A working group last call for this document was completed on April 7, 1999. This version of the document reflects comments received during an earlier IETF last call and IESG review. Bob Hinden / Steve Deering IPng Working Group Co-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