IETF Logo Mail Archive

RE: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-04.txt> (Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC

<mohamed.boucadair@orange.com> Tue, 10 September 2013 06:58 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F44C21E811E; Mon, 9 Sep 2013 23:58:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.981
X-Spam-Level:
X-Spam-Status: No, score=-1.981 tagged_above=-999 required=5 tests=[AWL=0.266, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, 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 cn9PnQmgRsCF; Mon, 9 Sep 2013 23:58:05 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 3E66B21F8756; Mon, 9 Sep 2013 23:58:02 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 0DDFE18C13C; Tue, 10 Sep 2013 08:57:59 +0200 (CEST)
Received: from PUEXCH41.nanterre.francetelecom.fr (unknown [10.101.44.30]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id E1D43238055; Tue, 10 Sep 2013 08:57:58 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.233.200.25]) by PUEXCH41.nanterre.francetelecom.fr ([10.101.44.30]) with mapi; Tue, 10 Sep 2013 08:57:54 +0200
From: mohamed.boucadair@orange.com
To: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 10 Sep 2013 08:57:52 +0200
Subject: RE: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-04.txt> (Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC
Thread-Topic: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-04.txt> (Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC
Thread-Index: Ac6t8dDQE0Ex3P6GRNOi1org5og3jQAAGhpw
Message-ID: <94C682931C08B048B7A8645303FDC9F36EF0EE7D57@PUEXCB1B.nanterre.francetelecom.fr>
References: <20130819135219.8236.40060.idtracker@ietfa.amsl.com> <CAKD1Yr1VpJne1h-Q5xbNMYRhpr_n0Wmn6UqfeG3vEg2MY6ms1g@mail.gmail.com> <94C682931C08B048B7A8645303FDC9F36EF033638D@PUEXCB1B.nanterre.francetelecom.fr> <CAKD1Yr0pqeO9KdcKFWVqWP_5pmZ6fgQ5h4tQ=vOO57d-dg5+DA@mail.gmail.com> <10526_1378283356_5226EF5C_10526_843_1_1B2E7539FECD9048B261B791B1B24A7C511C52CE60@PUEXCB1A.nanterre.francetelecom.fr> <CAKD1Yr3SddZio-vHGHK=5smb94HP58cY05_TGgWQpkS3=Ay8_w@mail.gmail.com> <94C682931C08B048B7A8645303FDC9F36EF033645A@PUEXCB1B.nanterre.francetelecom.fr> <CAKD1Yr0CUzSDv9H1eCUpMRUjBDS2OCkfsfE+S+3J8Z-_6=uVSg@mail.gmail.com> <CAKHUCzwYrjyobah-oPWD3vwUeUH5XZ7U=Fqof-f28tneS8jAvQ@mail.gmail.com> <CAKD1Yr0_yOaDjrH-5K696YaziZZR+EMxdRCf=JZBW5LZgWS45Q@mail.gmail.com> <94C682931C08B048B7A8645303FDC9F36EF06D0A6F@PUEXCB1B.nanterre.francetelecom.fr> <CAKD1Yr3cgJ-xumsMK3eL3zySGsPqXU9uw4L857bJ0VEGcA5mBQ@mail.gmail.com> <94C682931C08B048B7A8645303FDC9F36EF06D0AF5@PUEXCB1B.nanterre.francetelecom.fr> <CAKD1Yr2WgEi7vg3K9yFgmG64jduZN0kDD5o0m0f1Lfy=dZ28Zw@mail.gmail.com>
In-Reply-To: <CAKD1Yr2WgEi7vg3K9yFgmG64jduZN0kDD5o0m0f1Lfy=dZ28Zw@mail.gmail.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR
Content-Type: multipart/alternative; boundary="_000_94C682931C08B048B7A8645303FDC9F36EF0EE7D57PUEXCB1Bnante_"
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.9.10.55415
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>, BINET David IMT/OLN <david.binet@orange.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2013 06:58:11 -0000

Re,

I have considered that Lorenzo. "is not required to deploy IPv6" would be accurate if this document is dealing only with dual-stack, but this is not true for the IPv6-only mode. The set of SHOULD recommendations are targeting that deployment model.

Cheers,
Med


De : Lorenzo Colitti [mailto:lorenzo@google.com]
Envoyé : mardi 10 septembre 2013 08:49
À : BOUCADAIR Mohamed IMT/OLN
Cc : Dave Cridland; v6ops@ietf.org WG; BINET David IMT/OLN; IETF Discussion
Objet : Re: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-04.txt> (Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC

On Mon, Sep 9, 2013 at 9:16 PM, <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> wrote:

NEW:

      NOTE WELL: This document is not a standard, and conformance with
      it is not required in order to claim conformance with IETF
      standards for IPv6.  It uses the normative keywords defined in the
      previous section only for precision.


That's better, thanks. I still think it's important for the document to say that it's not necessary to do all mountain of work to deploy IPv6, because otherwise there's the risk that product managers/implementors will say, "Wait, are you're saying that to deploy IPv6 we have to do all that work? We can't do all that. Let's focus on something else instead."

How about changing "is not required in order to claim conformance with IETF standards for IPv6" to "is not required to deploy IPv6 on other networks or to claim conformance with IETF standards for IPv6"?

v2.23.0 | Report a Bug | By Email