Hans Kruse wrote: > > This may be a nit -- but wouldn't it make more sense then to call you > preferred course of action "B", and publish 2002:RFC1918 as the (temporary) > replacement?
I can't see a single argument in favour of importing the RFC1918 mess into IPv6. Such addresses would be worse than FEC0::/10, because they would appear to be globally routeable, but wouldn't be. > I guess I am suggesting that the WG pursue its work in such a way that we > do not create a vacuum; I feel strongly that the set of IPv6 standards > documents should clearly define the address space to use for the cases that > folks have suggested are currently covered by site-local. That is exactly the purpose of the trio of documents we are working on. Brian - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Brian E Carpenter Distinguished Engineer, Internet Standards & Technology, IBM NEW ADDRESS <[EMAIL PROTECTED]> PLEASE UPDATE ADDRESS BOOK > > --On Tuesday, August 05, 2003 16:07 +0100 Zefram <[EMAIL PROTECTED]> wrote: > > > The three options are really the same. We already have alternatives > > to site-local addresses: 6to4 addresses based on PI or RFC1918 > > IPv4 addresses. We didn't have these alternatives a few > > years ago. These aren't perfect, which is why we must develop > > draft-hinden-ipv6-global-local-addr, but they're enough that > > fec0::/10 seems rather unnecessary in any current IPv6 deployment. > > They particularly handle the requirements of those organisations that > > want site-locals because that's what they had with IPv4 and they want > > the same again. > > > > So I support option A, deprecate site-locals independent of further > > development of alternatives. We have sufficiently good stopgap solutions. > > > > I'm expecting, by the way, that the deprecation will leave fec0::/10 > > to be treated as global-scope unicast addresses, rather than making > > fec0::/10 addresses cease to function altogether. > > > > -zefram > > -------------------------------------------------------------------- > > 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] > > -------------------------------------------------------------------- > > Hans Kruse, Associate Professor > J. Warren McClure School of Communication Systems Management > Adjunct Associate Professor of Electrical Engineering and Computer Science > Ohio University, Athens, OH, 45701 > 740-593-4891 voice, 740-593-4889 fax > -------------------------------------------------------------------- > 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] > -------------------------------------------------------------------- -------------------------------------------------------------------- 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] --------------------------------------------------------------------
