IETF Logo Mail Archive

Re: [BEHAVE] CGN REQ: Port Set Assignment

<mohamed.boucadair@orange-ftgroup.com> Thu, 17 March 2011 07:12 UTC

Return-Path: <mohamed.boucadair@orange-ftgroup.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 25F4D3A67FC for <behave@core3.amsl.com>; Thu, 17 Mar 2011 00:12:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.764
X-Spam-Level:
X-Spam-Status: No, score=-1.764 tagged_above=-999 required=5 tests=[AWL=-0.116, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_43=0.6, UNPARSEABLE_RELAY=0.001]
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 ycE+EruSOrMi for <behave@core3.amsl.com>; Thu, 17 Mar 2011 00:12:45 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) by core3.amsl.com (Postfix) with ESMTP id 630613A67AA for <behave@ietf.org>; Thu, 17 Mar 2011 00:12:45 -0700 (PDT)
Received: from omfeda08.si.francetelecom.fr (unknown [xx.xx.xx.201]) by omfeda11.si.francetelecom.fr (ESMTP service) with ESMTP id 857551B81D1; Thu, 17 Mar 2011 08:14:12 +0100 (CET)
Received: from puexch31.nanterre.francetelecom.fr (unknown [10.101.44.29]) by omfeda08.si.francetelecom.fr (ESMTP service) with ESMTP id 6540138403C; Thu, 17 Mar 2011 08:14:12 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.11]) by puexch31.nanterre.francetelecom.fr ([10.101.44.29]) with mapi; Thu, 17 Mar 2011 08:14:12 +0100
From: mohamed.boucadair@orange-ftgroup.com
To: Dan Wing <dwing@cisco.com>, 'Reinaldo Penno' <rpenno@juniper.net>, "draft-ietf-behave-lsn-requirements@tools.ietf.org" <draft-ietf-behave-lsn-requirements@tools.ietf.org>
Date: Thu, 17 Mar 2011 08:14:10 +0100
Thread-Topic: [BEHAVE] CGN REQ: Port Set Assignment
Thread-Index: AcvjIqvyHEN/PZAJQFafEA4YjAjBJAAF4EfQAACQgjEAATpYcAAATtl/AAU6NjAAAd3SygAAUxxAAADVbCQAADD60AAPk29wABItJQAAIccDMA==
Message-ID: <94C682931C08B048B7A8645303FDC9F33C4DBA413C@PUEXCB1B.nanterre.francetelecom.fr>
References: <13e001cbe361$06f7b120$14e71360$@com> <C9A53B9D.3C324%rpenno@juniper.net> <140501cbe364$9ca93240$d5fb96c0$@com> <94C682931C08B048B7A8645303FDC9F33C4DBA3CC8@PUEXCB1B.nanterre.francetelecom.fr> <164801cbe3eb$a43a3950$ecaeabf0$@com>
In-Reply-To: <164801cbe3eb$a43a3950$ecaeabf0$@com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.5.9.395186, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.3.17.51527
Cc: DENG Xiaohong ESP/PEK <xiaohong.deng@orange-ftgroup.com>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] CGN REQ: Port Set Assignment
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: Thu, 17 Mar 2011 07:12:47 -0000

 

-----Message d'origine-----
De : Dan Wing [mailto:dwing@cisco.com] 
Envoyé : mercredi 16 mars 2011 16:06
À : BOUCADAIR Mohamed OLNC/NAD/TIP; 'Reinaldo Penno'; draft-ietf-behave-lsn-requirements@tools.ietf.org
Cc : DENG Xiaohong ESP/PEK; behave@ietf.org
Objet : RE: [BEHAVE] CGN REQ: Port Set Assignment

> 
> I am thinking of A+P-like schemes.
> 
> Med: Which ones? Dynamic modes have been proposed in A+P; see
> http://tools.ietf.org/html/draft-rqb-dynamic-port-ranges-02. Port
> randomization requirement can be fairly honored.
> 
>  No implementation magic can
> change the number of ports allocated by those schemes, because
> those schemes generally stick port information into the IPv6
> address or into a tunnel header.
> 
> Med: This is true for the stateless A+P mode but not the binding mode
> (see: http://tools.ietf.org/html/draft-ymbk-aplusp-09#section-4.4 for
> more details).

Most of the benefits attributed to A+P is that it's stateless in the
SP's network. 

Med: The binding mode adds only one (few) per-subscriber state compared to a per-session state for the NAT. 

 I haven't seen anyone excited about that, but I don't
talk to everyone.

Med: You should ;-). The binding mode is similar to the DS-Lite but with AFTR=PRR (Port Range Router).

v2.23.0 | Report a Bug | By Email