IETF Logo Mail Archive

Re: Last Call: draft-ietf-v6ops-natpt-to-historic (Reasons to Move NAT-PT to Historic Status) to Informational RFC

Fred Baker <fred@cisco.com> Wed, 28 February 2007 22:00 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMWqv-0001y4-8M; Wed, 28 Feb 2007 17:00:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMWqt-0001sd-41 for ietf@ietf.org; Wed, 28 Feb 2007 17:00:47 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMWqp-0005rj-Nx for ietf@ietf.org; Wed, 28 Feb 2007 17:00:47 -0500
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-3.cisco.com with ESMTP; 28 Feb 2007 14:00:43 -0800
X-IronPort-AV: i="4.14,232,1170662400"; d="scan'208"; a="467639485:sNHT49016768"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l1SM0hZh011987; Wed, 28 Feb 2007 14:00:43 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l1SM0WVA009596; Wed, 28 Feb 2007 14:00:43 -0800 (PST)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 28 Feb 2007 14:00:32 -0800
Received: from [10.32.244.221] ([10.32.244.221]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 28 Feb 2007 14:00:32 -0800
In-Reply-To: <198A730C2044DE4A96749D13E167AD370114793E@MOU1WNEXMB04.vcorp.ad.vrsn.com>
References: <198A730C2044DE4A96749D13E167AD370114793E@MOU1WNEXMB04.vcorp.ad.vrsn.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <93C67B6E-FEF7-4A99-ABFB-CBDD15512A34@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Date: Wed, 28 Feb 2007 14:00:30 -0800
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 28 Feb 2007 22:00:32.0246 (UTC) FILETIME=[DDBEC960:01C75B83]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2058; t=1172700043; x=1173564043; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:=20Fred=20Baker=20<fred@cisco.com> |Subject:=20Re=3A=20Last=20Call=3A=20draft-ietf-v6ops-natpt-to-historic=2 0(Reasons=20to=20Move=20NAT-PT=20to=20Historic=20Status)=20to=20Informatio nal=20RFC |Sender:=20; bh=TEVJUW54EsnXnfUhvgW1CF5YQCtS8W5uwDbdHxuY00E=; b=nQ2qAftAptSbhI9C3zhWLzEgw/Qn4H/RQP8h/HD+koL95xLbUPaJqWbvQqGqLLMCXJS+Qwmb W/xwIUt1pimb9en2NpFrE9W4r+/xblmEGIn3GVHWeIVKlZq4PUGOYp/z;
Authentication-Results: sj-dkim-2; header.From=fred@cisco.com; dkim=pass (si g from cisco.com/sjdkim2002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: v6ops@ops.ietf.org, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
Subject: Re: Last Call: draft-ietf-v6ops-natpt-to-historic (Reasons to Move NAT-PT to Historic Status) to Informational RFC
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

On Feb 28, 2007, at 12:40 PM, Hallam-Baker, Phillip wrote:

> Is there a document that describes a deployment plan under a two  
> stack transition?

Well, I can't say they are exacty what you're looking for, but you  
might glance at:

http://www.ietf.org/rfc/rfc2767.txt
2767 Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS).
      K. Tsuchiya, H. Higuchi, Y. Atarashi. February 2000. (Format:
      TXT=26402 bytes) (Status: INFORMATIONAL)

http://www.ietf.org/rfc/rfc3338.txt
3338 Dual Stack Hosts Using "Bump-in-the-API" (BIA). S. Lee, M-K.
      Shin, Y-J. Kim, E. Nordmark, A. Durand. October 2002. (Format:
      TXT=34480 bytes) (Status: EXPERIMENTAL)

http://www.ietf.org/rfc/rfc3750.txt
3750 Unmanaged Networks IPv6 Transition Scenarios. C. Huitema, R.
      Austein, S. Satapati, R. van der Pol. April 2004. (Format:  
TXT=48153
      bytes) (Status: INFORMATIONAL)

http://www.ietf.org/rfc/rfc3974.txt
3974 SMTP Operational Experience in Mixed IPv4/v6 Environments. M.
      Nakamura, J. Hagino. January 2005. (Format: TXT=22729 bytes)  
(Status:
      INFORMATIONAL)

http://www.ietf.org/rfc/rfc4038.txt
4038 Application Aspects of IPv6 Transition. M-K. Shin, Ed., Y-G.
      Hong, J. Hagino, P. Savola, E. M. Castro. March 2005. (Format:
      TXT=69727 bytes) (Status: INFORMATIONAL)

http://www.ietf.org/rfc/rfc4215.txt
4215 Analysis on IPv6 Transition in Third Generation Partnership
      Project (3GPP) Networks. J. Wiljakka, Ed.. October 2005. (Format:
      TXT=52903 bytes) (Status: INFORMATIONAL)

http://www.ietf.org/rfc/rfc4241.txt
4241 A Model of IPv6/IPv4 Dual Stack Internet Access Service. Y.
      Shirasaki, S. Miyakawa, T. Yamasaki, A. Takenouchi. December 2005.
      (Format: TXT=20580 bytes) (Status: INFORMATIONAL)

http://www.ietf.org/rfc/rfc4779.txt
4779 ISP IPv6 Deployment Scenarios in Broadband Access Networks. S.
      Asadullah, A. Ahmed, C. Popoviciu, P. Savola, J. Palet. January  
2007.
      (Format: TXT=188511 bytes) (Status: INFORMATIONAL)

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email