
From fred@cisco.com  Wed Jan  5 02:27:04 2011
Return-Path: <fred@cisco.com>
X-Original-To: nat66@core3.amsl.com
Delivered-To: nat66@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B97783A6949 for <nat66@core3.amsl.com>; Wed,  5 Jan 2011 02:27:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.406
X-Spam-Level: 
X-Spam-Status: No, score=-110.406 tagged_above=-999 required=5 tests=[AWL=0.193, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j-WOg4YXwirK for <nat66@core3.amsl.com>; Wed,  5 Jan 2011 02:27:03 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id D2DCF3A6DE3 for <nat66@ietf.org>; Wed,  5 Jan 2011 02:27:02 -0800 (PST)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAELWI02rRN+K/2dsb2JhbACkJXOmKZhhhUwEhGiGIoMf
X-IronPort-AV: E=Sophos;i="4.60,277,1291593600"; d="scan'208";a="396272441"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-1.cisco.com with ESMTP; 05 Jan 2011 10:29:10 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id p05AT4xL000965; Wed, 5 Jan 2011 10:29:09 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Wed, 05 Jan 2011 02:29:09 -0800
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Wed, 05 Jan 2011 02:29:09 -0800
Mime-Version: 1.0 (Apple Message framework v1082)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <20110105061202.41DD93A6B1D@core3.amsl.com>
Date: Wed, 5 Jan 2011 02:28:54 -0800
Message-Id: <4CF7DC15-F670-42CF-A1E6-5C635E862F0F@cisco.com>
References: <20110105061202.41DD93A6B1D@core3.amsl.com>
To: NAT66 HappyFunBall <nat66@ietf.org>
X-Mailer: Apple Mail (2.1082)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: mrw@painless-security.com
Subject: Re: [nat66] New Version Notification for draft-mrw-nat66-06
X-BeenThere: nat66@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for discussion of IPv6-to-IPv6 NAT." <nat66.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nat66>, <mailto:nat66-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nat66>
List-Post: <mailto:nat66@ietf.org>
List-Help: <mailto:nat66-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nat66>, <mailto:nat66-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2011 10:27:04 -0000

Posted a new version this evening, with updates from Merike Kaeo in the =
Security Considerations section.
	http://tinyurl.com/2f2mdre

On Jan 4, 2011, at 10:12 PM, IETF I-D Submission Tool wrote:

>=20
> A new version of I-D, draft-mrw-nat66-06.txt has been successfully =
submitted by Fred Baker and posted to the IETF repository.
>=20
> Filename:	 draft-mrw-nat66
> Revision:	 06
> Title:		 IPv6-to-IPv6 Network Prefix Translation
> Creation_date:	 2011-01-04
> WG ID:		 Independent Submission
> Number_of_pages: 31
>=20
> Abstract:
> This document describes a stateless, transport-agnostic IPv6-to-IPv6
> Network Prefix Translation (NPTv6) function that provides the address
> independence benefit associated with IPv4-to-IPv4 NAT (NAT44), and in
> addition provides a 1:1 relationship between addresses in the
> "inside" and "outside" prefixes, preserving end to end reachability
> at the network layer.
>=20
> Requirements Terminology
>=20
> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
> document are to be interpreted as described in RFC 2119 [RFC2119].
>=20
>=20
>=20
> The IETF Secretariat.
>=20
>=20


From arifumi@nttv6.net  Mon Jan 31 21:23:49 2011
Return-Path: <arifumi@nttv6.net>
X-Original-To: nat66@core3.amsl.com
Delivered-To: nat66@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A9F03A6A2B for <nat66@core3.amsl.com>; Mon, 31 Jan 2011 21:23:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.288
X-Spam-Level: 
X-Spam-Status: No, score=-101.288 tagged_above=-999 required=5 tests=[AWL=-0.240, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lP+h7I+97ull for <nat66@core3.amsl.com>; Mon, 31 Jan 2011 21:23:48 -0800 (PST)
Received: from mail.nttv6.net (mail.nttv6.net [IPv6:2001:fa8::25]) by core3.amsl.com (Postfix) with ESMTP id C52F63A6B73 for <nat66@ietf.org>; Mon, 31 Jan 2011 21:23:42 -0800 (PST)
Received: from [10.46.10.100] ([192.47.162.190]) by mail.nttv6.net (8.14.4/8.14.4) with ESMTP id p115PPqX007118; Tue, 1 Feb 2011 14:25:25 +0900 (JST) (envelope-from arifumi@nttv6.net)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Arifumi Matsumoto <arifumi@nttv6.net>
In-Reply-To: <4CF7DC15-F670-42CF-A1E6-5C635E862F0F@cisco.com>
Date: Tue, 1 Feb 2011 14:25:25 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <0A0469B5-987C-41BD-87ED-94211C8A2752@nttv6.net>
References: <20110105061202.41DD93A6B1D@core3.amsl.com> <4CF7DC15-F670-42CF-A1E6-5C635E862F0F@cisco.com>
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.1082)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (mail.nttv6.net [192.16.178.5]); Tue, 01 Feb 2011 14:25:27 +0900 (JST)
Cc: mrw@painless-security.com, NAT66 HappyFunBall <nat66@ietf.org>
Subject: [nat66] -07 intends experimental status Re: New Version Notification for draft-mrw-nat66-06
X-BeenThere: nat66@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for discussion of IPv6-to-IPv6 NAT." <nat66.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nat66>, <mailto:nat66-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nat66>
List-Post: <mailto:nat66@ietf.org>
List-Help: <mailto:nat66-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nat66>, <mailto:nat66-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 05:23:49 -0000

Hi all,

I realized -07 was published yesterday, and the intended status was =
changed to Experimental. Have we discussed about it here or anywhere =
else ?
I'm not against this change, but I just want to see what happened on =
this.

http://bit.ly/h4q9wl

On 2011/01/05, at 19:28, Fred Baker wrote:

> Posted a new version this evening, with updates from Merike Kaeo in =
the Security Considerations section.
> 	http://tinyurl.com/2f2mdre
>=20
> On Jan 4, 2011, at 10:12 PM, IETF I-D Submission Tool wrote:
>=20
>>=20
>> A new version of I-D, draft-mrw-nat66-06.txt has been successfully =
submitted by Fred Baker and posted to the IETF repository.
>>=20
>> Filename:	 draft-mrw-nat66
>> Revision:	 06
>> Title:		 IPv6-to-IPv6 Network Prefix Translation
>> Creation_date:	 2011-01-04
>> WG ID:		 Independent Submission
>> Number_of_pages: 31
>>=20
>> Abstract:
>> This document describes a stateless, transport-agnostic IPv6-to-IPv6
>> Network Prefix Translation (NPTv6) function that provides the address
>> independence benefit associated with IPv4-to-IPv4 NAT (NAT44), and in
>> addition provides a 1:1 relationship between addresses in the
>> "inside" and "outside" prefixes, preserving end to end reachability
>> at the network layer.
>>=20
>> Requirements Terminology
>>=20
>> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>> document are to be interpreted as described in RFC 2119 [RFC2119].
>>=20
>>=20
>>=20
>> The IETF Secretariat.
>>=20
>>=20
>=20
> _______________________________________________
> nat66 mailing list
> nat66@ietf.org
> https://www.ietf.org/mailman/listinfo/nat66


--
Arifumi Matsumoto
  NGN System Architecture Project
  NTT Service Integration Laboratories
  E-mail: arifumi@nttv6.net
  TEL +81-422-59-3334 FAX +81-422-59-6364


From fred@cisco.com  Mon Jan 31 23:06:55 2011
Return-Path: <fred@cisco.com>
X-Original-To: nat66@core3.amsl.com
Delivered-To: nat66@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D17E43A6965 for <nat66@core3.amsl.com>; Mon, 31 Jan 2011 23:06:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.249
X-Spam-Level: 
X-Spam-Status: No, score=-110.249 tagged_above=-999 required=5 tests=[AWL=0.350, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BWJuogp+EDUO for <nat66@core3.amsl.com>; Mon, 31 Jan 2011 23:06:53 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 84B643A68BD for <nat66@ietf.org>; Mon, 31 Jan 2011 23:06:53 -0800 (PST)
Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0LAB9AR02Q/khLgWdsb2JhbACgAAEDgRWDaBUBARYiJKAKiyuQCYVRBIZqhFJlg0KDFwE
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 01 Feb 2011 07:10:08 +0000
Received: from [192.168.12.236] (dhcp-10-55-81-209.cisco.com [10.55.81.209]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p117A8qQ029537; Tue, 1 Feb 2011 07:10:08 GMT
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Fred Baker <fred@cisco.com>
In-Reply-To: <0A0469B5-987C-41BD-87ED-94211C8A2752@nttv6.net>
Date: Tue, 1 Feb 2011 07:10:08 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <12C3785D-4072-487B-9055-8FEA7D9F189C@cisco.com>
References: <20110105061202.41DD93A6B1D@core3.amsl.com> <4CF7DC15-F670-42CF-A1E6-5C635E862F0F@cisco.com> <0A0469B5-987C-41BD-87ED-94211C8A2752@nttv6.net>
To: Arifumi Matsumoto <arifumi@nttv6.net>
X-Mailer: Apple Mail (2.1082)
Cc: mrw@painless-security.com, NAT66 HappyFunBall <nat66@ietf.org>, Ron Bonica <ron@bonica.org>
Subject: Re: [nat66] -07 intends experimental status Re: New Version Notification for draft-mrw-nat66-06
X-BeenThere: nat66@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for discussion of IPv6-to-IPv6 NAT." <nat66.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nat66>, <mailto:nat66-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nat66>
List-Post: <mailto:nat66@ietf.org>
List-Help: <mailto:nat66-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nat66>, <mailto:nat66-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 07:06:56 -0000

On Feb 1, 2011, at 5:25 AM, Arifumi Matsumoto wrote:

> Hi all,
>=20
> I realized -07 was published yesterday, and the intended status was =
changed to Experimental. Have we discussed about it here or anywhere =
else ?
> I'm not against this change, but I just want to see what happened on =
this.

In short form, I talked about it with Ron Bonica, who agreed to carry it =
through the IESG as an individual submission. We talked about standards =
track vs informational vs experimental status. In short, the IESG can =
put any document to whatever status they want, but depending on status =
the bar is higher or lower and the process varies a bit. Experimental =
has the lowest bar; Ron and I thought it might make the process in the =
IETF (which has already been highly contentious) easiest.

Like you, I'm not particularly concerned with the status. We have any =
number of instances where technology has been published as experimental =
or informational and later moved to the standards track. However, if =
there is a strong opinion on this list, I (and I think Ron) can also be =
convinced to change it.

> http://bit.ly/h4q9wl
>=20
> On 2011/01/05, at 19:28, Fred Baker wrote:
>=20
>> Posted a new version this evening, with updates from Merike Kaeo in =
the Security Considerations section.
>> 	http://tinyurl.com/2f2mdre
>>=20
>> On Jan 4, 2011, at 10:12 PM, IETF I-D Submission Tool wrote:
>>=20
>>>=20
>>> A new version of I-D, draft-mrw-nat66-06.txt has been successfully =
submitted by Fred Baker and posted to the IETF repository.
>>>=20
>>> Filename:	 draft-mrw-nat66
>>> Revision:	 06
>>> Title:		 IPv6-to-IPv6 Network Prefix Translation
>>> Creation_date:	 2011-01-04
>>> WG ID:		 Independent Submission
>>> Number_of_pages: 31
>>>=20
>>> Abstract:
>>> This document describes a stateless, transport-agnostic IPv6-to-IPv6
>>> Network Prefix Translation (NPTv6) function that provides the =
address
>>> independence benefit associated with IPv4-to-IPv4 NAT (NAT44), and =
in
>>> addition provides a 1:1 relationship between addresses in the
>>> "inside" and "outside" prefixes, preserving end to end reachability
>>> at the network layer.
>>>=20
>>> Requirements Terminology
>>>=20
>>> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>>> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>>> document are to be interpreted as described in RFC 2119 [RFC2119].
>>>=20
>>>=20
>>>=20
>>> The IETF Secretariat.
>>>=20
>>>=20
>>=20
>> _______________________________________________
>> nat66 mailing list
>> nat66@ietf.org
>> https://www.ietf.org/mailman/listinfo/nat66
>=20
>=20
> --
> Arifumi Matsumoto
>  NGN System Architecture Project
>  NTT Service Integration Laboratories
>  E-mail: arifumi@nttv6.net
>  TEL +81-422-59-3334 FAX +81-422-59-6364
>=20

