IETF Logo Mail Archive

[shara] Shara scope

<pierre.levis@orange-ftgroup.com> Mon, 26 January 2009 12:45 UTC

Return-Path: <shara-bounces@ietf.org>
X-Original-To: shara-archive@ietf.org
Delivered-To: ietfarch-shara-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 935D53A6B7A; Mon, 26 Jan 2009 04:45:53 -0800 (PST)
X-Original-To: shara@core3.amsl.com
Delivered-To: shara@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A36133A6B7A for <shara@core3.amsl.com>; Mon, 26 Jan 2009 04:45:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.504
X-Spam-Level:
X-Spam-Status: No, score=-2.504 tagged_above=-999 required=5 tests=[AWL=-0.745, BAYES_05=-1.11, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 4MX3cxFMExs4 for <shara@core3.amsl.com>; Mon, 26 Jan 2009 04:45:51 -0800 (PST)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by core3.amsl.com (Postfix) with ESMTP id 553D63A6A9F for <shara@ietf.org>; Mon, 26 Jan 2009 04:45:50 -0800 (PST)
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959); Mon, 26 Jan 2009 13:45:29 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 26 Jan 2009 13:45:06 +0100
Message-ID: <D109C8C97C15294495117745780657AE0B27BADC@ftrdmel1>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Shara scope
Thread-Index: Acl/s+fQbqY5EJjFQASUaGt+lEYm/w==
From: <pierre.levis@orange-ftgroup.com>
To: <shara@ietf.org>
X-OriginalArrivalTime: 26 Jan 2009 12:45:29.0133 (UTC) FILETIME=[F7E085D0:01C97FB3]
Subject: [shara] Shara scope
X-BeenThere: shara@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Sharing of an IPv4 Address discussion list <shara.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shara>, <mailto:shara-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/shara>
List-Post: <mailto:shara@ietf.org>
List-Help: <mailto:shara-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shara>, <mailto:shara-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1040854467=="
Sender: shara-bounces@ietf.org
Errors-To: shara-bounces@ietf.org

Hi,

So, shara deals with "port range" and softwire deals with DS-lite, which
is fine with me, even if all IPv4 shared address solutions in the same
WG would also make sense.

But what about other solutions? I'm thinking of CGN in its Double NAT
version. It is a solution already deployed in some ISPs' networks and
the only one currently available on shelves (even if DS-lite
implementations make quick progress).

Shouldn't we integrate a BCP document in the "Proposed Work" section to
cover this item? Basically considerations of where to locate the CGN and
how to route the traffic between customers and CGN?



Pierre

_______________________________________________
shara mailing list
shara@ietf.org
https://www.ietf.org/mailman/listinfo/shara

v2.8.7 | Report a Bug | By Email