On Thu, 6 Feb 2003, Michel Py wrote: > I say, ship it. Agree.
> If the RFC number could be consecutive to the one to be > assigned to draft-ietf-ipngwg-addr-arch-v3-11.txt same as 2373/2374 it > would be nice if it does not delay the process. Surely it can, as this one cannot be published before draft-ietf-ipngwg-addr-arch-v3-11.txt is published. > Although the suppression of the documentation prefix is a worthy > trade-off for speed of publication, it does not suppress the need for a > documentation prefix RFC IMHO, even if some RIRs have or will allocate > one on their own. Agree. > As many other people, I was not aware of the APNIC > prefix, and did like 2000:0001::/32 as it is something that my feeble > brain can remember. Agree. -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings -------------------------------------------------------------------- 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 [EMAIL PROTECTED] --------------------------------------------------------------------
