Re: [v6ops] draft-binet-v6ops-cellular-host-reqs-rfc3316update

<mohamed.boucadair@orange.com> Fri, 21 September 2012 05:56 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE0CC21F8613 for <v6ops@ietfa.amsl.com>; Thu, 20 Sep 2012 22:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.615
X-Spam-Level:
X-Spam-Status: No, score=-0.615 tagged_above=-999 required=5 tests=[AWL=-1.494, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MANGLED_EXTNSN=2.3, SARE_SUB_OBFU_Q1=0.227, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yNzsLeGrWYnQ for <v6ops@ietfa.amsl.com>; Thu, 20 Sep 2012 22:56:38 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 9501121F8555 for <v6ops@ietf.org>; Thu, 20 Sep 2012 22:56:38 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 35F1526458D; Fri, 21 Sep 2012 07:56:37 +0200 (CEST)
Received: from PUEXCH61.nanterre.francetelecom.fr (unknown [10.101.44.32]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 1CAFE4C086; Fri, 21 Sep 2012 07:56:37 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.8]) by PUEXCH61.nanterre.francetelecom.fr ([10.101.44.32]) with mapi; Fri, 21 Sep 2012 07:56:36 +0200
From: mohamed.boucadair@orange.com
To: GangChen <phdgang@gmail.com>
Date: Fri, 21 Sep 2012 07:56:35 +0200
Thread-Topic: [v6ops] draft-binet-v6ops-cellular-host-reqs-rfc3316update
Thread-Index: Ac2XQmRwvgB9eKq4TDyGJOoGmWYBegABlmmg
Message-ID: <94C682931C08B048B7A8645303FDC9F36E5B12338F@PUEXCB1B.nanterre.francetelecom.fr>
References: <94C682931C08B048B7A8645303FDC9F36E5A40D46C@PUEXCB1B.nanterre.francetelecom.fr> <CAM+vMET-T6Docv1En+GsLJp=t6Dwzu-FKnEdhcYWBVLBu0ue8w@mail.gmail.com>
In-Reply-To: <CAM+vMET-T6Docv1En+GsLJp=t6Dwzu-FKnEdhcYWBVLBu0ue8w@mail.gmail.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.9.21.40316
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] draft-binet-v6ops-cellular-host-reqs-rfc3316update
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Sep 2012 05:56:39 -0000

Hi Gang,

Thanks for the review. 

Please see inline.

Cheers,
Med 

>-----Message d'origine-----
>De : GangChen [mailto:phdgang@gmail.com] 
>Envoyé : jeudi 20 septembre 2012 17:13
>À : BOUCADAIR Mohamed OLNC/NAD/TIP
>Cc : IPv6 Ops WG
>Objet : Re: [v6ops] draft-binet-v6ops-cellular-host-reqs-rfc3316update
>
>Hello Med,
>
>Thanks for the work. I read the draft.
>In general, the requirements have been structured as Basic
>Connectivity, Advanced and APIs & Applications
>Just wondering to know what release of cellular host the requirements
>are targeting?
>What's the consideration to frame the context of each section?
>I have noticed that some basic IPv6 capability is mentioned in the
>part of Advanced Requirements.  That seems to me should belong to the
>Basic part.
>
>More details are as following.
>
>2.  Basic Connectivity Requirements
>REQ#1,
>REQ#2,
>REQ#3 and REQ#4 were already specified in 3GPP.
>Not sure it would add much discussions to the draft.

Med: The purpose of the draft is to have one place where an IPv6 profile for cellular device is device. There are several requirements on the UEs spread in various specification document. Listing those 3GPP spec is one part of the puzzle to define an IPv6 profile for cellular hosts.

>
>REQ#6 and REQ#7 should be combined IMHO, because it provides same
>outcome solving the issues related to compatibility of IPv4
>applications.>
>REQ#8: I don't understand the purpose of embed a DNS64 function.
>Especially, the sentence of "This allows to be compatible with DNSSEC"

Med: I see Ted already answered to this comment. 
>
>REQ#10 I guess I-D.ietf-behave-nat64-discovery-heuristic should be
>ranked as first priority compared to
>I-D.boucadair-pcp-nat64-prefix64-option

Med: Please refer to http://www.ietf.org/mail-archive/web/pcp/current/msg02273.html for the discussion I had with Teemu on this item.

>
>REQ#11: Preferring native IPv6 doesn't always achieve good effect. It
>may cause additional charge in some cases. Please refer to
>http://tools.ietf.org/html/draft-ietf-mif-happy-eyeballs-extens
>ion-00#page-3
>case 4 for further information

Med: I added a pointer to the MIF draft to record the issue.

>
>One additional requirement maybe worth to add for the completeness:
>
>REQ#XX The cellular device SHOULD embed a BIH function [RFC6535]
>facilitating the communication between IPv4 application and IPv6
>server

Med: As we have CLAT already listed there, what would be the motivation to include BIH?
I added a discussion note to the draft to record this point.    

>
>2.1.  WiFi Connectivity
>
>It may be complementary to add one additional requirement, like
>
>REQ#XX Prefix Delegation capabilities [RFC3633] MUST be supported on
>the Wi-Fi interface.

Med: Wouldn't this be redundant with what is the features discussed in Section 4?

>
>
>3.  Advanced Requirements
>
> REQ#16,
> REQ#17,
> REQ#18,
> REQ#19 and REQ#20 may be proper to be shifted to "2. Basic
>Connectivity Requirements", since those features are basic IPv6
>capability

Med: I will check.

>
>REQ#22:  it maybe proper to change the *SHOULD* to *MAY*

Med: What is the rationale behind that change?

>
>Best Regards
>
>Gang
>
>2012/9/20, mohamed.boucadair@orange.com <mohamed.boucadair@orange.com>:
>> Dear all,
>>
>> We submitted this new I-D.
>>
>> Review and comments are more than welcome.
>>
>> Cheers,
>> Med
>>
>>
>> -----Message d'origine-----
>> De : i-d-announce-bounces@ietf.org 
>[mailto:i-d-announce-bounces@ietf.org] De
>> la part de internet-drafts@ietf.org
>> Envoyé : mercredi 19 septembre 2012 14:57
>> À : i-d-announce@ietf.org
>> Objet : I-D Action:
>> draft-binet-v6ops-cellular-host-reqs-rfc3316update-00.txt
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>
>>
>> 	Title           : Internet Protocol Version 6 (IPv6) 
>for Cellular Hosts
>> 	Author(s)       : David Binet
>>                           Mohamed Boucadair
>> 	Filename        :
>> draft-binet-v6ops-cellular-host-reqs-rfc3316update-00.txt
>> 	Pages           : 14
>> 	Date            : 2012-09-19
>>
>> Abstract:
>>    This document lists a set of IPv6-related requirements to be
>>    supported by cellular hosts.
>>
>>    This document updates RFC3316.
>>
>>
>>
>> The IETF datatracker status page for this draft is:
>> 
>https://datatracker.ietf.org/doc/draft-binet-v6ops-cellular-hos
>t-reqs-rfc3316update
>>
>> There's also a htmlized version available at:
>> 
>http://tools.ietf.org/html/draft-binet-v6ops-cellular-host-reqs
>-rfc3316update-00
>>
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>>
>