Re: [v6ops] draft-binet-v6ops-cellular-host-requirements-01

jouni korhonen <jouni.nospam@gmail.com> Tue, 20 November 2012 08:35 UTC

Return-Path: <jouni.nospam@gmail.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 383A321F85EF for <v6ops@ietfa.amsl.com>; Tue, 20 Nov 2012 00:35:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.241
X-Spam-Level:
X-Spam-Status: No, score=-3.241 tagged_above=-999 required=5 tests=[AWL=-0.242, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
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 u96HBbUQCwLV for <v6ops@ietfa.amsl.com>; Tue, 20 Nov 2012 00:35:57 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id CD34521F85EA for <v6ops@ietf.org>; Tue, 20 Nov 2012 00:35:56 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so4723967lbk.31 for <v6ops@ietf.org>; Tue, 20 Nov 2012 00:35:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=KDVGeNgkEbsAffBhVOimnWPyqz6oFuFOJfSPXJoDyWk=; b=aBZEUoy7ExtvbtCpDLBKZg8rm5h3SoqjTaQOWfI/vXUzr5lT5gcmx5A9LxpMavoXNn ZVOhuTXfXgA9zXcRzscEN8d0nH/49x+TqG57iCu3aG8onEA0PddfcYNYAUZpiWpWBptd ZM72acnnWT6GT8UTQ1VmkBsoYTs8WEZj+NtmNVzKeoyNGX8s3YoyIVD7kT6tqQ2fzAiP bGgxYtOMJBFZbkcN06Nwv5ef04QLCNOfvV2bnxhQ3UD2GiLDDc0fNzlW+opPgpQbAcez x5NQd8Mws5P6rRa3IK+QWz+W9UUa8kIrkJeUqkDxMXv2pME48yFzv35zAcYzp7D0ioh8 wG+Q==
Received: by 10.152.128.9 with SMTP id nk9mr6950314lab.17.1353400555546; Tue, 20 Nov 2012 00:35:55 -0800 (PST)
Received: from ?IPv6:2001:1bc8:101:f101:226:bbff:fe18:6e9c? ([2001:1bc8:101:f101:226:bbff:fe18:6e9c]) by mx.google.com with ESMTPS id lv1sm4438313lab.14.2012.11.20.00.35.51 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 20 Nov 2012 00:35:54 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset="iso-8859-1"
From: jouni korhonen <jouni.nospam@gmail.com>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36E9751E536@PUEXCB1B.nanterre.francetelecom.fr>
Date: Tue, 20 Nov 2012 10:35:50 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E0D2406E-3C78-4366-AE29-ABDC5B85AA0D@gmail.com>
References: <94C682931C08B048B7A8645303FDC9F36E95C9F86C@PUEXCB1B.nanterre.francetelecom.fr> <2A43389B-7D02-4B9B-B2CD-A3CDC4E6E26E@gmail.com> <94C682931C08B048B7A8645303FDC9F36E9751E273@PUEXCB1B.nanterre.francetelecom.fr> <8344869F-B4D0-440B-8455-024046F76AD9@gmail.com> <94C682931C08B048B7A8645303FDC9F36E9751E2D4@PUEXCB1B.nanterre.francetelecom.fr> <6F49F841-FD9E-4996-9C17-245F46C6EABE@gmail.com> <94C682931C08B048B7A8645303FDC9F36E9751E536@PUEXCB1B.nanterre.francetelecom.fr>
To: mohamed.boucadair@orange.com
X-Mailer: Apple Mail (2.1085)
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Subject: Re: [v6ops] draft-binet-v6ops-cellular-host-requirements-01
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: Tue, 20 Nov 2012 08:35:58 -0000

On Nov 19, 2012, at 9:30 AM, <mohamed.boucadair@orange.com> <mohamed.boucadair@orange.com> wrote:

> Hi Jouni,
> 
> The question of overlapping is not important IMHO as the two documents are targeting distinct objectives. I thought you agreed with this point (below an excerpt from the minutes):

I agree these document have different objectives. That is clear. Still it does not make sense to repeat IPv6 related requirements in normative language that are part of the generic cellular host IPv6 requirement. Even after the change I proposed, there still are many deployment & profile issues that are not covered anywhere except in draft-binet-*.

- Jouni

> 
> "
> Lorenzo C - Doc 1 is a shopping list document 2 is a treatis on how
> you implment ipv6 on 3316. they're not covering the same domain
> 
> Jouni K - Agree with Lorenzo - different objectives so they need to be
> treated differently
> "
> 
> If now you are claiming yours is also doing what draft-binet-* does, I'm puzzled then...
> 
> Cheers,
> Med 
> 
>> -----Message d'origine-----
>> De : jouni korhonen [mailto:jouni.nospam@gmail.com] 
>> Envoyé : dimanche 18 novembre 2012 00:14
>> À : BOUCADAIR Mohamed OLNC/OLN
>> Cc : v6ops@ietf.org WG
>> Objet : Re: [v6ops] draft-binet-v6ops-cellular-host-requirements-01
>> 
>> 
>> Hi,
>> 
>> Likewise rfc3316bis assumes IPv6-only or dual-stack. Point 
>> being, rfc3316bis does not do in direction that is not 
>> necessary to run IPv6 (in a possibly multi interfaced host). 
>> IMHO the rest like NAT related recommendations, transition 
>> recommendations, WLAN specifics, tethering recommendations are 
>> then well served in draft-bonet-*.
>> 
>> - Jouni
>> 
>> On Nov 16, 2012, at 3:17 PM, <mohamed.boucadair@orange.com> 
>> <mohamed.boucadair@orange.com> wrote:
>> 
>>> Re-,
>>> 
>>> draft-binet-* assumes both DS and IPv6-only deployment 
>> modes. Nothing specific there.
>>> 
>>> Cheers,
>>> Med
>>> 
>>>> -----Message d'origine-----
>>>> De : jouni korhonen [mailto:jouni.nospam@gmail.com] 
>>>> Envoyé : vendredi 16 novembre 2012 14:09
>>>> À : BOUCADAIR Mohamed OLNC/OLN
>>>> Cc : v6ops@ietf.org WG
>>>> Objet : Re: [v6ops] draft-binet-v6ops-cellular-host-requirements-01
>>>> 
>>>> 
>>>> Med,
>>>> 
>>>> I still see no reason to replicate information since what 
>>>> comes to "a pure IPv6 profile for a 3GPP link", it should be 
>>>> exactly the same in both documents. I am just trying to avoid 
>>>> misalignment now and in the future. I would also argue that 
>>>> draft-binet-* is a profile for a specific deployment(s) in 
>>>> mind, not a generic IPv6 profile for cellular. It is a way 
>>>> more (not that it would be a bad thing though..).
>>>> 
>>>> - Jouni
>>>> 
>>>> 
>>>> On Nov 16, 2012, at 2:07 PM, <mohamed.boucadair@orange.com> 
>>>> <mohamed.boucadair@orange.com> wrote:
>>>> 
>>>>> Hi Jouni,
>>>>> 
>>>>> What I understood from the v6ops meeting is that wg 
>>>> participants see these two documents have distinct objectives. 
>>>> As such the question of overlapping does not apply as these 
>>>> documents serve two distinct objectives. Furthermore, because 
>>>> draft-binet-*'s objective is to define an IPv6 profile for 
>>>> cellular, we prefer the document be self-contained and use 
>>>> consistent language for all requirements.
>>>>> 
>>>>> Cheers,
>>>>> Med 
>>>>> 
>>>>>> -----Message d'origine-----
>>>>>> De : Jouni [mailto:jouni.nospam@gmail.com] 
>>>>>> Envoyé : jeudi 15 novembre 2012 16:40
>>>>>> À : BOUCADAIR Mohamed OLNC/OLN
>>>>>> Cc : v6ops@ietf.org; Mikael Abrahamsson; Pete Vickers
>>>>>> Objet : Re: [v6ops] 
>> draft-binet-v6ops-cellular-host-requirements-01
>>>>>> 
>>>>>> 
>>>>>> Med,
>>>>>> 
>>>>>> I am slightly confused about the overlap of 
>>>>>> draft-binet-v6ops-* and draft-ietf-v6ops-rfc3316bis. My 
>>>>>> recollection was that overlaps were supposed to be removed and 
>>>>>> then concentrate on the remaining part in draft-binet-v6ops-*, 
>>>>>> no? This would concern requirements #1, #6, #7, #8, #9, #17, 
>>>>>> #22, #23, #25, #26, #27. My recommendation would be removing 
>>>>>> those and just reference to [draft-ietf-v6ops-rfc3316bis] 
>>>>>> because the base IPv6 compliancy would come from there and I 
>>>>>> see no reason to repeat those here.
>>>>>> 
>>>>>> Then a question about the relevance of #24. Given the current 
>>>>>> bandwidth in 3G/LTE is there really a need to compress 
>>>>>> headers? And if people really see it as a life critical 
>>>>>> feature to have, I would appreciate listing the ROHC profiles 
>>>>>> that are essential (e.g., align with IR.92 & IR.58 that will 
>>>>>> be implemented on the network side).
>>>>>> 
>>>>>> - Jouni
>>>>>> 
>>>>>> 
>>>>>> On Nov 15, 2012, at 4:59 PM, <mohamed.boucadair@orange.com> 
>>>>>> <mohamed.boucadair@orange.com> wrote:
>>>>>> 
>>>>>>> Dear all,
>>>>>>> 
>>>>>>> We submitted a new version of the draft to take into account 
>>>>>> the comments received from M. Abrahamsson and P. Vickers.
>>>>>>> 
>>>>>>> The main changes are:
>>>>>>> 
>>>>>>> * Add some clarification text for REQ#3
>>>>>>> * Mention stateless dhcpv6 is useful to retrieve other 
>>>>>> information than DNS
>>>>>>> * Re-word REQ#15
>>>>>>> * Cite "Happy Eyeballs" in REQ#16
>>>>>>> * Update the text of REQ#17
>>>>>>> * Add two sub-requirements to REQ#19: IPv6-only 
>>>> connectivity + SLAAC
>>>>>>> * Precise the ordering in REQ#21
>>>>>>> 
>>>>>>> A more detailed diff is available at:
>>>>>>> 
>>>>>> http://www.ietf.org/rfcdiff?url2=draft-binet-v6ops-cellular-hos
>>>>>> t-requirements-01
>>>>>>> 
>>>>>>> 
>>>>>>> Chairs, would it be possible to issue a Call For Adoption 
>>>>>> for this document? Thanks.
>>>>>>> 
>>>>>>> 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é : jeudi 15 novembre 2012 15:53
>>>>>>> À : i-d-announce@ietf.org
>>>>>>> Objet : I-D Action: 
>>>>>> draft-binet-v6ops-cellular-host-requirements-01.txt
>>>>>>> 
>>>>>>> 
>>>>>>> A New Internet-Draft is available from the on-line 
>>>>>> Internet-Drafts directories.
>>>>>>> 
>>>>>>> 
>>>>>>> 	Title           : Internet Protocol Version 6 (IPv6) 
>>>>>> Requirements for Cellular Hosts
>>>>>>> 	Author(s)       : David Binet
>>>>>>>                       Mohamed Boucadair
>>>>>>>                       Ales Vizdal
>>>>>>>                       Cameron Byrne
>>>>>>>                       Gang Chen
>>>>>>> 	Filename        : 
>>>>>> draft-binet-v6ops-cellular-host-requirements-01.txt
>>>>>>> 	Pages           : 16
>>>>>>> 	Date            : 2012-11-15
>>>>>>> 
>>>>>>> Abstract:
>>>>>>> This document lists a set of IPv6-related requirements to be
>>>>>>> supported by cellular hosts.
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> The IETF datatracker status page for this draft is:
>>>>>>> 
>>>>>> https://datatracker.ietf.org/doc/draft-binet-v6ops-cellular-hos
>>>>>> t-requirements
>>>>>>> 
>>>>>>> There's also a htmlized version available at:
>>>>>>> 
>>>>>> http://tools.ietf.org/html/draft-binet-v6ops-cellular-host-requ
>>>>>> irements-01
>>>>>>> 
>>>>>>> A diff from the previous version is available at:
>>>>>>> 
>>>>>> http://www.ietf.org/rfcdiff?url2=draft-binet-v6ops-cellular-hos
>>>>>> t-requirements-01
>>>>>>> 
>>>>>>> 
>>>>>>> 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
>>>>>> 
>>>> 
>>