IETF Logo Mail Archive

Re: [BEHAVE] WGLC: draft-ietf-behave-nat64-learn-analysis-00

<mohamed.boucadair@orange-ftgroup.com> Thu, 08 September 2011 09:32 UTC

Return-Path: <mohamed.boucadair@orange-ftgroup.com>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8505321F8B1A for <behave@ietfa.amsl.com>; Thu, 8 Sep 2011 02:32:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.339
X-Spam-Level:
X-Spam-Status: No, score=-2.339 tagged_above=-999 required=5 tests=[AWL=-0.091, 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 8u6mUzypR6-x for <behave@ietfa.amsl.com>; Thu, 8 Sep 2011 02:32:42 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) by ietfa.amsl.com (Postfix) with ESMTP id C6D9221F8B10 for <behave@ietf.org>; Thu, 8 Sep 2011 02:32:41 -0700 (PDT)
Received: from omfeda05.si.francetelecom.fr (unknown [xx.xx.xx.198]) by omfeda11.si.francetelecom.fr (ESMTP service) with ESMTP id E04391B8860; Thu, 8 Sep 2011 11:34:30 +0200 (CEST)
Received: from PUEXCH71.nanterre.francetelecom.fr (unknown [10.101.44.33]) by omfeda05.si.francetelecom.fr (ESMTP service) with ESMTP id C5883180042; Thu, 8 Sep 2011 11:34:30 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.7]) by PUEXCH71.nanterre.francetelecom.fr ([10.101.44.33]) with mapi; Thu, 8 Sep 2011 11:34:30 +0200
From: mohamed.boucadair@orange-ftgroup.com
To: Dan Wing <dwing@cisco.com>, "behave@ietf.org" <behave@ietf.org>
Date: Thu, 08 Sep 2011 11:34:29 +0200
Thread-Topic: [BEHAVE] WGLC: draft-ietf-behave-nat64-learn-analysis-00
Thread-Index: AcxImw6xYcizfz1QRMOj/AxfKwvyXAlbhS0A
Message-ID: <94C682931C08B048B7A8645303FDC9F3516744765B@PUEXCB1B.nanterre.francetelecom.fr>
References: <000101cc48b3$a9f87500$fde95f00$@com>
In-Reply-To: <000101cc48b3$a9f87500$fde95f00$@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.9.8.85414
Cc: "draft-ietf-behave-nat64-learn-analysis@tools.ietf.org" <draft-ietf-behave-nat64-learn-analysis@tools.ietf.org>
Subject: Re: [BEHAVE] WGLC: draft-ietf-behave-nat64-learn-analysis-00
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 08 Sep 2011 09:32:42 -0000

Dear all,

The document is in a good shape and I support its publication.

I have one minor comment, the conclusion says: 

"None of the discussed solutions support learning of
   possible new or indicating support for multiple algorithms for
   address synthesis other than the one described in [RFC6052]."

Which is not actually true for one of the solutions discussed in Section 4.6. Please refer to http://tools.ietf.org/html/draft-boucadair-dhcpv6-shared-address-option-01#section-5 for more details.

Cheers,
Med
 

-----Message d'origine-----
De : behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] De la part de Dan Wing
Envoyé : vendredi 22 juillet 2011 23:10
À : behave@ietf.org
Cc : draft-ietf-behave-nat64-learn-analysis@tools.ietf.org
Objet : [BEHAVE] WGLC: draft-ietf-behave-nat64-learn-analysis-00

This starts a 3 week WGLC (extra time to accommodate IETF travel) for
draft-ietf-behave-nat64-learn-analysis-00.  This document analyzes the
available approaches for a host to learn its NAT64 prefix.  Abstract:

   Hosts and applications may benefit from the knowledge if an IPv6
   address is synthesized, which would mean a NAT64 is used to reach the
   IPv4 network or Internet.  This document analyses a number of
   proposed solutions for communicating whether the synthesis is taking
   place, used address format, and the IPv6 prefix used by the NAT64 and
   DNS64.  The solutions enable both NAT64 avoidance and intentional
   utilization by allowing local IPv6 address synthesis.  The document
   concludes by recommending selection of heuristic discovery based
   solution.

Please send comments to behave@ietf.org.  WGLC ends in 3 weeks on 
August 12.

-d


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

v2.23.0 | Report a Bug | By Email