Re: [apps-discuss] APPSDIR review of draft-ietf-behave-64-analysis-05

<mohamed.boucadair@orange.com> Fri, 17 February 2012 09:16 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2392D21F887E; Fri, 17 Feb 2012 01:16:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.186
X-Spam-Level:
X-Spam-Status: No, score=-2.186 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CsODJABMgQ+j; Fri, 17 Feb 2012 01:16:02 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 466EF21F885C; Fri, 17 Feb 2012 01:16:02 -0800 (PST)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id F105C3B4212; Fri, 17 Feb 2012 10:16:00 +0100 (CET)
Received: from PUEXCH41.nanterre.francetelecom.fr (unknown [10.101.44.30]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id CBF384C060; Fri, 17 Feb 2012 10:16:00 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.12]) by PUEXCH41.nanterre.francetelecom.fr ([10.101.44.30]) with mapi; Fri, 17 Feb 2012 10:16:00 +0100
From: mohamed.boucadair@orange.com
To: S Moonesamy <sm+ietf@elandsys.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>, "draft-ietf-behave-64-analysis.all@tools.ietf.org" <draft-ietf-behave-64-analysis.all@tools.ietf.org>
Date: Fri, 17 Feb 2012 10:15:59 +0100
Thread-Topic: APPSDIR review of draft-ietf-behave-64-analysis-05
Thread-Index: AcztSr3tCEngTmJBQsGF8VcTugRUcAAB/jRg
Message-ID: <94C682931C08B048B7A8645303FDC9F35D8868D42C@PUEXCB1B.nanterre.francetelecom.fr>
References: <6.2.5.6.2.20120216094738.08f96280@elandnews.com> <94C682931C08B048B7A8645303FDC9F35D8868D387@PUEXCB1B.nanterre.francetelecom.fr> <6.2.5.6.2.20120216232557.0915c0a0@elandnews.com>
In-Reply-To: <6.2.5.6.2.20120216232557.0915c0a0@elandnews.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.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.2.17.85414
X-Mailman-Approved-At: Fri, 17 Feb 2012 11:59:09 -0800
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [apps-discuss] APPSDIR review of draft-ietf-behave-64-analysis-05
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2012 09:16:03 -0000

Re-,

Thank you for the clarifications. I updated the document accordingly.

Cheers,
Med 

> -----Message d'origine-----
> De : S Moonesamy [mailto:sm+ietf@elandsys.com] 
> Envoyé : vendredi 17 février 2012 08:57
> À : BOUCADAIR Mohamed OLNC/NAD/TIP; apps-discuss@ietf.org; 
> draft-ietf-behave-64-analysis.all@tools.ietf.org
> Cc : behave@ietf.org
> Objet : RE: APPSDIR review of draft-ietf-behave-64-analysis-05
> 
> Hi Med,
> At 22:51 16-02-2012, mohamed.boucadair@orange.com wrote:
> >In some deployment it can be SPOF but in others no. This depends if 
> >the a distributed NAT model is adopted, if NAT state synchronization 
> >mechanisms are enabled, etc. Do we need to clarify this in 
> the document?
> 
> It would help the reader if that could be clarified.
> 
> >The IPv4 address pool used by the NAT64 to service IPv6 hosts. 
> >Several IPv6 hosts may share the same IPv4 address. Do you think 
> >this need a clarification in the document?
> 
> I recommend a clarification as there is a proposal about 
> shared address space.
> 
> >Sorry, but I don't understand this comment. Can you please 
> clarify? Thanks.
> 
> If we are talking about the BEHAVE WG, IETF participants either know 
> about it or can look it up.  If you say "which complies with BEHAVE 
> NAT", a wider audience would not know what BEHAVE is.  It's easier to 
> say "complies with NAT recommendations in [RFC4787][RFC5382]".
> 
> >I can do but IMHO the document does not introduce new 
> security concerns, no?
> 
> I don't think so but I'll defer to the Security Directorate on this.
> 
> Thanks for the feedback.
> 
> Regards,
> S. Moonesamy 
> 
>