This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/
[ipv6-wg at ripe.net] New IPv6 Address Block Allocated to RIPE NCC
- Previous message (by thread): [ipv6-wg at ripe.net] New IPv6 Address Block Allocated to RIPE NCC
- Next message (by thread): [ipv6-wg at ripe.net] New IPv6 Address Block Allocated to RIPE NCC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
JORDI PALET MARTINEZ
jordi.palet at consulintel.es
Sun Jun 20 13:38:29 CEST 2004
Hi all, My take on this ... I talked this week in Santa Monica to Doug Barton (copied) IANA General Manager. If I didn't misunderstood him, the only reason they are allocating /23 blocks to the RIRs is because they can't do anything on that, unless IETF change it. Actually they are following rules that were designed for the initial allocations, expected only for the 1st 2 years. I believe the document being followed for this is RFC2450 (ftp://ftp.rfc-editor.org/in-notes/rfc2450.txt), authored by Bob Hinden (copied). So the only way for IANA to allocate /8 will be to update RFC2450. Is that right Doug ? If this is the case, I will be interested in helping in the process of updating RFC2450, and I guess also Bob as the original author. I'm also sure some other could volunteer in this community. Bob, what is the trigger or showstopper to update this document, if any ? Actually, I think after having updated RFC2374 with RFC3587, makes a lot of sense, right ? Regards, Jordi ----- Original Message ----- From: "Carlos Friacas" <cfriacas at fccn.pt> To: <ipv6-wg at ripe.net> Sent: Thursday, June 17, 2004 3:59 PM Subject: Re: [ipv6-wg at ripe.net] New IPv6 Address Block Allocated to RIPE NCC > > On Thu, 17 Jun 2004, Kurt Erik Lindqvist wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > > > On 2004-06-17, at 09.18, Jeroen Massar wrote: > > > > > > > > Or like NIKE says: Just do it. > > > > > > And give ARIN + APNIC + LACNIC + AFRINIC a /8 too. > > > AFRINIC and LACNIC won't be able to 'justify' it that easily but they > > > will *never* (I hope ;) run out, even if every single tree that is > > > still > > > standing in the rainforests get a /64 ;) > > > > Well, the point is that there is nothing to justify. Have each of the > > RIRs request a /8. Have IANA assign it (after all the iterations > > between IAB, IANA, IESG, IANA, etc). Done. > > > > - - kurtis - > > What do we need to see this happen *soon*? > 200 signatures? ;-) > A chain letter supporting it? > > If someone able to kick-off this process is reading this, please do it... > > Thanks, > > ./Carlos > -------------- IPv6 -> http://www.ip6.fccn.pt > Wide Area Network Workgroup, CMF8-RIPE, CF596-ARIN > FCCN - Fundacao para a Computacao Cientifica Nacional http://www.fccn.pt > > "Internet is just routes (135072/470), naming (millions) and... people!" > > ********************************** Madrid 2003 Global IPv6 Summit Presentations and videos on line at: http://www.ipv6-es.com This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
- Previous message (by thread): [ipv6-wg at ripe.net] New IPv6 Address Block Allocated to RIPE NCC
- Next message (by thread): [ipv6-wg at ripe.net] New IPv6 Address Block Allocated to RIPE NCC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]