[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Avoiding the terminology confusion with NAT66

To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: Avoiding the terminology confusion with NAT66
From: Simon Leinen <simon.leinen@switch.ch>
Date: Fri, 06 Aug 2010 21:40:08 +0200
Cc: Randy Bush <randy@psg.com>, RÃmi DesprÃs <remi.despres@free.fr>, Dan Wing <dwing@cisco.com>, IPv6 v6ops <v6ops@ops.ietf.org>, Behave WG <behave@ietf.org>
In-reply-to: <AANLkTim2_XjBcJaBOBr8rG6LVUbXPJz7L=nPEF9ftP_1@mail.gmail.com> (Bob Hinden's message of "Thu, 5 Aug 2010 18:39:52 -0700")
References: <4FAA72A8-6223-4956-9CB1-D3DB4E555209@cisco.com> <4C577BF2.9000807@gmail.com> <148F4D91-A203-4660-B2D1-59808D86A876@cisco.com> <3D4F97DE-E523-4206-BB87-61281C4A73B4@apnic.net> <A15C6A1E-6F2C-485B-AD33-3D5DDE651E15@cisco.com> <A0BD7E22-D691-4091-8D35-95286F9882A7@free.fr> <040401cb332e$2f5ce380$8e16aa80$@com> <86F21EF8-9C98-4C2A-BAF5-29F4AD6D1426@free.fr> <055d01cb334d$65f478d0$31dd6a70$@com> <47295AD4-7F50-4751-A9EC-45D48D928CD7@free.fr> <m24ofbbcea.wl%randy@psg.com> <B42A8196-484C-4FC7-9507-C29AC3B9C41D@gmail.com> <m2hbj87el9.wl%randy@psg.com> <AANLkTim2_XjBcJaBOBr8rG6LVUbXPJz7L=nPEF9ftP_1@mail.gmail.com>
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (darwin)

> How about pomegraNATe :-)

As in "Prefix-Only Modification for Enhanced Guidance,
which Ran^Hdicals Accuse of Nasty Address-Torturing Evilness"?
-- 
Simon.

References:
- Avoiding the terminology confusion with NAT66
  - From: Rémi Després <remi.despres@free.fr>
- Re: Avoiding the terminology confusion with NAT66
  - From: Randy Bush <randy@psg.com>
- Re: Avoiding the terminology confusion with NAT66
  - From: Bob Hinden <bob.hinden@gmail.com>
- Re: Avoiding the terminology confusion with NAT66
  - From: Randy Bush <randy@psg.com>
- Re: Avoiding the terminology confusion with NAT66
  - From: Bob Hinden <bob.hinden@gmail.com>

Prev by Date: Re: draft-ietf-v6ops-cpe-simple-security-12.txt feedback
Next by Date: Re: draft-ietf-v6ops-cpe-simple-security-12.txt feedback
Previous by thread: Re: Avoiding the terminology confusion with NAT66
Next by thread: Re: Avoiding the terminology confusion with NAT66
Index(es):
- Date
- Thread