> -----Original Message----- > From: Kevin Kargel [mailto:[EMAIL PROTECTED] > Sent: Friday, June 22, 2007 6:18 AM > To: Templin, Fred L; Leo Vegoda; Scott Leibrand > Cc: [email protected] > Subject: RE: draft-ietf-ipv6-ula-central-02.txt > > I believe the implication comes when people assume that ULA-C > addresses > will be applied on hosts that need direct communication with the DFZ. > As ULA-C is "non-routable" then NAT or some sort of proxy would be > required.
But, don't the multi-addressing capabilities of IPv6 already solve that? If the communications scope is within a site (or, between two merged sites) then ULA-C can be used. If instead the scope crosses the DFZ, then a globally-routable address must be used. Why would we ask site border routers to NAT IPv6 when the problem is solved by address selection at the source and filtering at the site border routers? Fred [EMAIL PROTECTED] > In a network I was designing it would be a non-issue. If a host > required access to the DFZ it would get a PI address. Why make things > complicated when you can make them simple? > > > -----Original Message----- > > From: Templin, Fred L [mailto:[EMAIL PROTECTED] > > Sent: Thursday, June 21, 2007 5:27 PM > > To: Leo Vegoda; Scott Leibrand > > Cc: [email protected] > > Subject: RE: draft-ietf-ipv6-ula-central-02.txt > > > > Maybe I am missing the point, but there seems to be an > > implication that ULA-C necessarily implies IPv6 NAT; am I > > misinterpreting? If not, then I don't quite understand why > > this implication is being drawn. Can someone please explain? > > > > Thanks - Fred > > [EMAIL PROTECTED] > > > > -------------------------------------------------------------------- > > IETF IPv6 working group mailing list > > [email protected] > > Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 > > -------------------------------------------------------------------- > > > -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
