IETF Logo Mail Archive

Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call- "harmfully broad"?

<mohamed.boucadair@orange.com> Fri, 20 February 2015 13:05 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E52111A8AED for <v6ops@ietfa.amsl.com>; Fri, 20 Feb 2015 05:05:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.599
X-Spam-Level:
X-Spam-Status: No, score=-1.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2OHpDRPimZvI for <v6ops@ietfa.amsl.com>; Fri, 20 Feb 2015 05:05:10 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 720DF1A8A16 for <v6ops@ietf.org>; Fri, 20 Feb 2015 05:05:10 -0800 (PST)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 44E2E3243E9; Fri, 20 Feb 2015 14:05:08 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.56]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 265074C12D; Fri, 20 Feb 2015 14:05:08 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.231]) by OPEXCLILH04.corporate.adroot.infra.ftgroup ([10.114.31.56]) with mapi id 14.03.0224.002; Fri, 20 Feb 2015 14:05:08 +0100
From: mohamed.boucadair@orange.com
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Thread-Topic: [v6ops] draft-ietf-v6ops-mobile-device-profile last call- "harmfully broad"?
Thread-Index: AQHQTQzDixBJZ1L350WogIuKXDMPO5z5gK1A
Date: Fri, 20 Feb 2015 13:05:08 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B9330049114CA@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <787AE7BB302AE849A7480A190F8B9330049091C2@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CAKD1Yr0Zkic6-ydV-u==xjDGdY9GYWb8KwciBPnfk8zO=6FFqQ@mail.gmail.com> <CAKD1Yr0qS-Vg-XB7mNWwephkkL5rCG+NJO7uDJg_4W3LT+Q9Ew@mail.gmail.com> <6536E263028723489CCD5B6821D4B21303E088AE@UK30S005EXS06.EEAD.EEINT.CO.UK> <CAKD1Yr00Ri8hQMsJcSqMAw+g_T-mU8GxG1G8rTHgo=McaKdW8Q@mail.gmail.com> <26150_1424277597_54E4C05D_26150_800_1_A729C0B3952BEE45A1AA136ADD556BE80493F147@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CAKD1Yr2+BMSifTS3x0WD5LqKYe-Yse8CGf4Egaijp=8DVSf5UA@mail.gmail.com> <fdc7ab8c-4f63-43eb-a77b-4764f24d9486@OPEXCLILH01.corporate.adroot.infra.ftgroup> <D10B3F46.1A731%dave.michaud@rci.rogers.com> <CAKD1Yr0zig7DY6npfe6JiKjmhojxTohV2==+C26zLVAU5CMo3w@mail.gmail.com> <D10B47D6.1A74E%dave.michaud@rci.rogers.com> <54E5EC11.4070002@gmail.com> <787AE7BB302AE849A7480A190F8B93300491144D@OPEXCLILM23.corporate.adroot.infra.ftgroup> <54E72F31.5030703@gmail.com>
In-Reply-To: <54E72F31.5030703@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.2.20.124219
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/hSwlQ7A7WN0z6h7gcYmum18O3Ec>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call- "harmfully broad"?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Feb 2015 13:05:12 -0000

Re-,

Please see inline.


> -----Message d'origine-----
> De : Alexandru Petrescu [mailto:alexandru.petrescu@gmail.com]
> Envoyé : vendredi 20 février 2015 13:57
> À : BOUCADAIR Mohamed IMT/OLN
> Cc : v6ops@ietf.org
> Objet : Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call-
> "harmfully broad"?
> 
> Le 20/02/2015 13:39, mohamed.boucadair@orange.com a écrit :
> > Hi Alex,
> >
> > It is obvious that CLAT has nothing to do with native IPv6
> > communications (i.e., communications between IPv6-enabled nodes over
> > an IPv6-enabled network).
> >
> > The CLAT recommendation in the profile I-D starts with: "In order to
> > ensure IPv4 service continuity in an IPv6-only deployment context,"
> >
> > That's IMHO clear enough to avoid "others to think that IPv6 is
> > possible only if CLAT is there.".
> 
> YEs, I agree.  That text is sufficient.

Cool! Thank you.

Cheers,
Med

> 
> As a side note, I would be doubtful naming an IPv6-only access network
> something that uses IPv4 as well (464xlat, dns64).  I would rather call
> it a "mostly" IPv6 access network, with a little of IPv4 however.
> 
> This is just a matter of terminology.
> 
> Also, since we last discussed we went trying eliminate the IPv4 stack
> from a linux kernel.  That is not possible.  So any 'pure' IPv6 machine
> that would connect to an IPv6-only access network is just a speculation
> at this point, years away from any deployment.
> 
> Alex
> 
> >
> > Cheers, Med
> >
> >> -----Message d'origine----- De : v6ops
> >> [mailto:v6ops-bounces@ietf.org] De la part de Alexandru Petrescu
> >> Envoyé : jeudi 19 février 2015 14:59 À : v6ops@ietf.org Objet :
> >> Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call-
> >> "harmfully broad"?
> >>
> >>
> >> Among those two (IPv6 and CLAT) one would certainly suggest IPv6
> >> implementation in the terminal, but CLAT should be a "MAY".  One
> >> wouldn't want others to think that IPv6 is possible only if CLAT
> >> is there.
> >>
> >> Alex
>

v2.23.0 | Report a Bug | By Email