> -----Original Message-----
> From: Keith Moore [mailto:[email protected]]
> Sent: Friday, October 29, 2010 11:11 AM
> To: Chris Engel
> Cc: 'Rémi Després'; [email protected]; Roger Marquis; HappyFunBall
> Subject: Re: [nat66] e2e New Version Notification
>
>
> >
> > Yes they can. The point I'm making here is that NAT isn't
> doing much
> > HARM to the Enterprise since it's not breaking anything
> they wouldn't
> > want broken anyways.
>
> Why should all enterprises have to deal with your extremely
> simplistic and naive view of what their security needs are
> and what their security strategy should be?
>
> Keith
>

Who's saying they will?  I'm not forcing them to use NAT anymore then I'm 
telling them what their FW rules must be...or what OS to standardize their 
hosts/servers on.

Nowhere, either in this draft or any of the hypothetical cases people have 
argued for Statefull NAT66 have I seen ANYONE try to argue that there should be 
ANY standard which REQUIRES an Enterprise to implement any flavor of NAT.

The only argument I've ventured is that there ARE legitimate usage cases for 
NAT (both the flavor being described in this document and a statefull NAT 
similar to what exists in IPv4 today). IF that's true, then it would be helpful 
(IMO) to EVERYONE that some standards be published that provide recommendations 
on how those technologies might be expected to behave.

If the argument is that an RFC should only be published if the usage case which 
it describes must be applicable to 100% of the internet community (rather then 
some subset)...then I think you are going to need to invalidate 99.99999% of 
the RFC's out there.

Furthermore, if you believe that that the technology goals which I have 
described are atypical of Enterprises...I will simply state that your 
experience of the Enterprise environment must run entirely counter to my own.



Christopher Engel
Network Infrastructure Manager
SponsorDirect
[email protected]
www.SponsorDirect.com
p(914) 729-7218
f (914) 729-7201
_______________________________________________
nat66 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nat66

Reply via email to