|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: Death of IPv6 Site-Local (was Re: Private port numbers?)
The IETF IPNG WG home page can be found at: http://playground.sun.com/ipng The decision regarding site-local was made during the San Francisco IETF meeting and then later confirmed on the mailing lists although there has been quite some debate over it all since then. IIRC the SF IETF meeting was in April which would have been before 3513. The WG is still trying to nail everything down as there are a number of I-D's out but still some are calling for SL to be included to some degree thus none have been able to work their way to becoming an RFC. If you have nothing to do for a couple days reading through the hundreds of posts regarding SL can definately kill the time... Regards, Jeremy On Thu, Aug 14, 2003 at 02:49:10PM -0700, Crist Clark wrote: > Without trying to find the mailing lists for the IPv6 working groups, > this must have been pretty recent. I just check up on RFCs every once > in a while and RFC 3513, dated April 2003, still talks about Site-Local. > > RFC 3587, from this month, talks about losing Top Level Aggregators > and Next Level Aggregators, but that's something different. > > I don't doubt you though, even though it's being deployed, IPv6 is far > from completely specified. The details still move around faster than > I'll be followoing. Heck, no one really has found a good way to use the > DIFSERV fields of IPv4 yet. > -- > Crist J. Clark [email protected] > Globalstar Communications (408) 933-4387 > > The information contained in this e-mail message is confidential, > intended only for the use of the individual or entity named above. > If the reader of this e-mail is not the intended recipient, or the > employee or agent responsible to deliver it to the intended recipient, > you are hereby notified that any review, dissemination, distribution or > copying of this communication is strictly prohibited. If you have > received this e-mail in error, please contact [email protected] Attachment:
pgp00037.pgp
|