Re: [BEHAVE] Expand "RFC 1918" things into the SP space?
"Dan Wing" <dwing@cisco.com> Tue, 28 July 2009 12:24 UTC
Return-Path: <dwing@cisco.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6AEE13A6D81 for <behave@core3.amsl.com>; Tue, 28 Jul 2009 05:24:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.188
X-Spam-Level:
X-Spam-Status: No, score=-6.188 tagged_above=-999 required=5 tests=[AWL=0.411, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 fMSZwQjkvkkz for <behave@core3.amsl.com>; Tue, 28 Jul 2009 05:24:03 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 115753A6BBE for <behave@ietf.org>; Tue, 28 Jul 2009 05:23:38 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApsEAPuKbkqrR7PD/2dsb2JhbACLDLAJiCePWAWEDIFN
X-IronPort-AV: E=Sophos;i="4.43,283,1246838400"; d="scan'208";a="190267533"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-2.cisco.com with ESMTP; 28 Jul 2009 12:23:19 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n6SCNJdK022461; Tue, 28 Jul 2009 05:23:19 -0700
Received: from dwingwxp01 ([10.21.119.29]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n6SCNHPf021705; Tue, 28 Jul 2009 12:23:18 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Jacni Qin' <jacniq@gmail.com>, behave@ietf.org
References: <e1a14dfb0907280433h570c03dfjfc9cc216a25ef62e@mail.gmail.com>
Date: Tue, 28 Jul 2009 14:23:13 +0200
Message-ID: <013c01ca0f7e$306aec10$5f7d150a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcoPd0qQPXal+4HJT9yGvj0EWgLEEAABThVw
In-Reply-To: <e1a14dfb0907280433h570c03dfjfc9cc216a25ef62e@mail.gmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1200; t=1248783799; x=1249647799; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dwing@cisco.com; z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com> |Subject:=20RE=3A=20[BEHAVE]=20Expand=20=22RFC=201918=22=20 things=20into=20the=20SP=20space? |Sender:=20; bh=obaYvHc+i+S9++DgCrHbDxh9hllbeGrSyAP6wHSJjEI=; b=Y7v5Hb2kNNDdb5mQ3Deru3j9MjfvMnlWHVahziuNYwlVTLJ1ZmXFyvc827 /1W/me3ZPLTc53H9zkYDj6plyq90P+v+lmgnPIy4U4MzGdBgHS6ln2NKbb5V cH4JxyN0tF;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
Cc: ai-nakagawa@kddi.com
Subject: Re: [BEHAVE] Expand "RFC 1918" things into the SP space?
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2009 12:24:04 -0000
> -----Original Message----- > From: behave-bounces@ietf.org > [mailto:behave-bounces@ietf.org] On Behalf Of Jacni Qin > Sent: Tuesday, July 28, 2009 1:33 PM > To: behave@ietf.org > Subject: [BEHAVE] Expand "RFC 1918" things into the SP space? > > Dear chairs and others, > > seeing some 44 NATs used in SP space discussed, > may i ask that is there any conclusion of whether the IETF > should address this? No conclusion yet. > i remember back to the co-existence interim meeing last year, > this point was ever metioned. > > or maybe i missed something? In the IETF, there are at least three I-Ds on the topic (draft-shirasaki-nat444-isp-shared-addr, draft-shirasaki-isp-shared-addr-02, draft-ford-shared-addressing-issues-00) and there have been at least 3 presentations to some different working groups. > quite appreciate if someone could give me the clarification. It is my understanding that Akira Nagakawa is presenting on the topic of SP-operated NAT44 devices in "Summarized story about NAT444" for 15 minutes at Thursday's OPSAREA open meeting, and I believe his presentation will discuss http://tools.ietf.org/agenda/75/opsarea.html -d