It's my general understanding that the principle behind NAT (of any flavor) is to abstract the internal architecture from the external advertisement of that architecture. Having a change to ones external architecture automatically cause a corresponding change to the internal architecture would seem to run counter to that principle, even ignoring feasability issues.
Christopher Engel Network Infrastructure Manager SponsorDirect [email protected] www.SponsorDirect.com p(914) 729-7218 f (914) 729-7201 > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Roger Marquis > Sent: Thursday, October 21, 2010 1:29 PM > To: [email protected] > Cc: [email protected] > Subject: [SPAM] - Re: [nat66] Fwd: New Version Notification > for draft-mrw-nat66-00 - Email has different SMTP TO: and > MIME TO: fields in the email addresses > > > > Not all tools are suitable for all cases. > > True. Working implementations should be required of all > common cases. I am not, however, aware of any working > implementations of stateful internal connections being > successfully renumbered. > > > Renumbering of enterprise network is quite a different case > than few > > laptops > > Are you saying that NAT66 would not need to be extensible, to > both scenarios? > > Roger Marquis > _______________________________________________ > nat66 mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/nat66 > _______________________________________________ nat66 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nat66
