[137890] in North American Network Operators' Group
RE: [arin-ppml] NAT444 rumors (was Re: Looking for an IPv6
daemon@ATHENA.MIT.EDU (Dan Wing)
Tue Feb 22 11:00:48 2011
From: "Dan Wing" <dwing@cisco.com>
To: "'Chris Grundemann'" <cgrundemann@gmail.com>
In-Reply-To: <AANLkTi=ESU19fGC+X09o5TftySqsD0eifu3Dmu8c1Y88@mail.gmail.com>
Date: Tue, 22 Feb 2011 08:00:37 -0800
Cc: 'NANOG list' <nanog@nanog.org>, 'ARIN-PPML List' <arin-ppml@arin.net>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
> -----Original Message-----
> From: Chris Grundemann [mailto:cgrundemann@gmail.com]
> Sent: Monday, February 21, 2011 8:17 PM
> To: Dan Wing
> Cc: Owen DeLong; Benson Schliesser; NANOG list; ARIN-PPML List
> Subject: Re: [arin-ppml] NAT444 rumors (was Re: Looking for an IPv6
> naysayer...)
>=20
> On Mon, Feb 21, 2011 at 19:08, Dan Wing <dwing@cisco.com> wrote:
>=20
> > Its title, filename, abstract, and introduction all say the problems
> > are specific to NAT444. =A0Which is untrue.
>=20
> I just re-read the filename, abstract and introduction, and I disagree
> that any of those say that the problems are specific to NAT444. They
> all do state that these problems are present in NAT444, but not that
> it's the only technology/scenario/configuration where you might find
> them.
>=20
> More importantly, I am unsure the point of this argument.
My point is that: NAT breaks things, but NAT444 is /not/ the only=20
case where breakage occurs.
> Are you
> trying to say that the items listed as broken in the draft are not
> actually broken? Because in my experience they are. IMHO, the fact
> that they are also broken in other (similar) scenarios is not evidence
> that they are not broken in this one. On the contrary, this scenario
> seems to be evidence to the brokenness in the others (until we get a
> chance to test and document them all - are you volunteering? ;).
Vendor test results don't carry much value.
The authors of draft-donley-nat444-impacts did testing, and
I sincerely hope will publish results that split the impacts of
access bandwidth starvation from home NAT from CGN from NAT444.
-d
> Cheers,
> ~Chris
>=20
>=20
> > -d
> >
> >
> >
>=20
>=20
>=20
>=20
> --
> @ChrisGrundemann
> weblog.chrisgrundemann.com
> www.burningwiththebush.com
> www.theIPv6experts.net
> www.coisoc.org
