- ipv6-wg - mailman.ripe.net

[fink@es.net: first production IPv6 prefix allocated by ARIN to ESnet (2001:0400::/35)]
by David Kessens 07 Aug '99

07 Aug '99

----- Forwarded message from Bob Fink <fink(a)es.net> ----- X-Sender: rlfink(a)imap2.es.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 06 Aug 1999 13:01:12 -0700 To: 6BONE List <6bone(a)ISI.EDU> From: Bob Fink <fink(a)es.net> Subject: first production IPv6 prefix allocated by ARIN to ESnet (2001:0400::/35) Precedence: bulk IPv6 community, Good news! The first production IPv6 prefix has been assigned by ARIN to ESnet (2001:0400::/35). This is a milestone for IPv6. Those networks that had previously requested sTLAs should now reapply to their respective registries (APNIC, ARIN and RIPE-NCC) for them. I have already been getting requests from these registries for validation that requestors qualify under the 6bone bootstrap policy. I would like to thank everyone involved over the last 2 1/2 years in the development of the Aggregatable Global Unicast Address Format and the policies regarding their allocation/assignment. I've included a short history and timeline of this effort below. I would especially like to commend the registries, both for their efforts to provide meaningful stewardship over the IPv6 address space, and for quickly starting the allocation process after IAB/IANA/RIR agreements on allocation policy were finalized. So many thanks to the APNIC, ARIN and RIPE-NCC staff! Regards, Bob === Fall 1996 - Mike O'Dell 8+8 (aka GSE) proposal to replace Provider Based Unicast Addressing for IPv6 Feb 1997 - Interim IPng WG meeting in Palo Alto to review 8+8 - some ideas kept, some discarded Apr 1997 - IPng WG meeting in Memphis - first idea of Aggregatable Unicast Addressing formulated May 1997 - Aggregatable Unicast Addressing draft and 6bone Test TLA draft released Oct 1997 - 6bone converts to Aggregatable Unicast Addressing under 3FFE::/16 Test TLA Jan 1998 - discussions begin between IAB/IETF, IANA, ARIN, APNIC and RIPE-NCC on policy to assign production TLAs Jul 1998 - RFC 2374, An IPv6 Aggregatable Global Unicast Address Format, published as Proposed Standard Aug 1998 - First requests for SubTLAs (sTLA) made to ARIN, APNIC and RIPE-NCC Jul 1999 - Oslo IETF - Final policy on assigning sTLAs reached (July 14) <http://www.arin.net/ipv6/IPv6.txt> Jul 20 1999 - First sTLA request (by ESnet) made under new policy submitted to ARIN Jul 21 1999 - First sTLA request approved (for ESnet) by ARIN (July 21) pending billing Jul 31 1999 - First IPv6 production prefix (sTLA = 2001:0400::/35) assigned (to ESnet) -end ----- End forwarded message -----

1 0

Reg.id:fi.ppo
by Vesa Haapaniemi 03 Aug '99

03 Aug '99

What does mean the sentence "The requesting organisation's network must have IPv4 BGP peering relationships with at least three other public Autonomous Systems in the default-free zone", in document RIPE 195? We are trying to translate these documents in Finnish and we didn't exactly understand this. Could You help us? Regards, Mr. Vesa Haapaniemi Vesa Haapaniemi PPO / Finnet-group Ratakatu 1 84100 Ylivieska (08) 4291 207 050 302 4803

1 0

[Fwd: Any calls for IPv6 over MS-DOS]
by Thomas Trede 30 Jul '99

30 Jul '99

FYI. Regards, Thomas Trede

1 0

[Fwd: Protocol Action: IPv6 Jumbograms to Proposed Standard]
by Thomas Trede 29 Jul '99

29 Jul '99

FYI. Regards, Thomas Trede

1 0

[Fwd: Protocol Action: IPv6 Jumbograms to Proposed Standard]
by Thomas Trede 29 Jul '99

29 Jul '99

FYI. Regards, Thomas Trede

1 0

[Fwd: Protocol Action: IPv6 Jumbograms to Proposed Standard]
by Thomas Trede 28 Jul '99

28 Jul '99

FYI. Regards, Thomas Trede

1 0

New Document available: RIPE-195
by RIPE NCC Document Announcement Service 28 Jul '99

28 Jul '99

New/Revised RIPE Document Announcement -------------------------------------- Two new documents are available from the RIPE document store. Ref: ripe-195 Title: IPv6 subTLA Request Form Author: RIPE NCC Date: 26 July 1999 Format: TXT=14354 and Ref: ripe-196 Title: Provisional IPv6 Assignment and Allocation Policy Document Author: RIPE NCC Date: 26 July 1999 Format: TXT=53579 Short content description ------------------------- ripe-195 is the form that a LIR needs to fill out if they want to request an IPv6 sub-TLA from the RIPE NCC. ripe-196 is the policy document for IPv6 assignments and allocations and explains the criteria for qualifying for a sub-TLA allocation. Accessing the RIPE document store --------------------------------- The RIPE document store is available via anonymous FTP to ftp.ripe.net, in the directory ripe/docs. The URLs for the new documents on the FTP-server are: ftp://ftp.ripe.net/ripe/docs/ripe-195.txt plain text version ftp://ftp.ripe.net/ripe/docs/ripe-196.txt plain text version You can also access the RIPE documents in HTML format via WWW, at the following URLs: http://www.ripe.net/docs/ripe-195.html http://www.ripe.net/docs/ripe-196.html

1 0

[Fwd: I-D ACTION:draft-ietf-ipngwg-hbh-ext-csi-01.txt]
by Thomas Trede 23 Jul '99

23 Jul '99

FYI. Regards, Thomas Trede

1 0

[Fwd: W.G. Last Call on "Preferred Format for Literal IPv6 Addressesin URL's"]
by Thomas Trede 21 Jul '99

21 Jul '99

FYI. Regards, Thomas Trede

1 0

[Fwd: Request to Advance "IPv6 Router Alert Option"]
by Thomas Trede 20 Jul '99

20 Jul '99

FYI. Regards, Thomas Trede

1 0