Re: [v6ops] draft-binet-v6ops-cellular-host-requirements-00.txt

Hesham Soliman <hesham@elevatemobile.com> Mon, 19 November 2012 13:37 UTC

Return-Path: <hesham@elevatemobile.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 54A3E21F8616 for <v6ops@ietfa.amsl.com>; Mon, 19 Nov 2012 05:37:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 I+Fy-nxIj7Q5 for <v6ops@ietfa.amsl.com>; Mon, 19 Nov 2012 05:37:33 -0800 (PST)
Received: from smtp-1.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by ietfa.amsl.com (Postfix) with ESMTP id 5D15021F8608 for <v6ops@ietf.org>; Mon, 19 Nov 2012 05:37:32 -0800 (PST)
Received: from [118.209.240.249] (helo=[192.168.0.2]) by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.69 #1 (Debian)) id 1TaRXS-0005ZS-MQ; Tue, 20 Nov 2012 00:37:27 +1100
User-Agent: Microsoft-MacOutlook/14.2.4.120824
Date: Tue, 20 Nov 2012 00:37:13 +1100
From: Hesham Soliman <hesham@elevatemobile.com>
To: Lorenzo Colitti <lorenzo@google.com>, <mohamed.boucadair@orange.com>
Message-ID: <CCD0810B.2DD5C%hesham@elevatemobile.com>
Thread-Topic: [v6ops] draft-binet-v6ops-cellular-host-requirements-00.txt
In-Reply-To: <CAKD1Yr0PcobuWwu+Dp36NHaFRyinD1SRV0WPk792h9EwwsuFmQ@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-Authenticated-User: hesham@elevatemobile.com
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] draft-binet-v6ops-cellular-host-requirements-00.txt
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: Mon, 19 Nov 2012 13:37:34 -0000

I made several comments on this document and are all included in Lorenzo's
comments below. Therefore I'm of the same opinion regarding WG adoption.

Hesham

-----Original Message-----
From: Lorenzo Colitti <lorenzo@google.com>
Date: Monday, 19 November 2012 7:39 PM
To: <mohamed.boucadair@orange.com>
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] draft-binet-v6ops-cellular-host-requirements-00.txt

>I do not think this document is ready for WG adoption.
>
>To start with, I see a few general issues.
>
>First, the document is attempting to standardize behaviours that are
>already standardized by 3GPP. This is leads to many of the requirements
>being redundant because they are already included in 3GPP specs. If the
>manufacturer is violating those specs already, I doubt that an RFC that
>says "don't violate those specs" is going to have any effect at all. This
>also presents the problem that if the 3GPP standards are updated, the
>text becomes out of date.
>
>Second, most of this document attempts to standardize feature sets, not
>protocols or interoperability. I'm not sure this is is in scope for the
>IETF, and even more so for an operations group inside the IETF.
>
>Third, IETF work is supposed to proceed in parallel with running code,
>not in the absence of running code. I very doubt there are two
>interoperable implementations that satisfy all these requirements
>(actually, I doubt that any real implementation satisfies even half of
>them). Attempting to specify these requirements will not change that.
>
>
>Moving on, at least these requirements are redundant and should be
>removed or replaced by a reference to the appropriate specs:
>
>
>REQ#3: Redundant with 3GPP specs.
>REQ#4: Redundant with 3GPP specs.
>REQ#5: Redundant with 3GPP specs.
>REQ#6: Redundant with IPv6 node requirements.
>REQ#7: Redundant with IPv6 node requirements.
>REQ#7: Redundant with IPv6 node requirements and 3GPP specs.
>
>REQ#15: Redundant with RFC 6724.
>REQ#17: Redundant with 3GPP specs.
>
>
>
>A few specific comments as well:
>
>REQ#1: why do you need to cite RFC 5952? It has nothing to do with
>connecting to cellular networks, and it's already in RFC 6434 (IPv6 Node
>Requirements).
>
>
>REQ#10: Not clear what happens if more than one provisioning method
>provides DNS. Should the phone just information from one of them? Or
>should it list all of them in priority order?
>
>REQ#11: Not clear to me what this means. I understand the "implement the
>NAT64 discovery heuristic" requirement, but not the part that references
>RFC 6052. What does the host need to implement from RFC 6052?
>
>
>REQ#18: Meaningless. Saying "MAY" in a requirements document is no better
>than saying nothing.
>
>REQ#25: What is the point of supporting RFC 5175 if it defines no new
>flags?
>
>REQ#27: Why support DHCPv6 PD if no mobile networks will support it for a
>number of years?
>
>REQ#28: Duplicate of #12.
>
>On Sun, Nov 11, 2012 at 10:47 PM,  <mohamed.boucadair@orange.com> wrote:
>
>
>
>
>Dear all,
>
>As discussed in the v6ops meeting, we re-submitted a new version of the
>text which does not update RFC3316.
>
>We hope this new version is ready for the WG adoption.
>
>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é : lundi 12 novembre 2012 07:42
>À : i-d-announce@ietf.org
>Objet : I-D Action: draft-binet-v6ops-cellular-host-requirements-00.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-00.txt
>        Pages           : 15
>        Date            : 2012-11-11
>
>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-host-requireme
>nts
>
>There's also a htmlized version available at:
>http://tools.ietf.org/html/draft-binet-v6ops-cellular-host-requirements-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 
><https://www.ietf.org/mailman/listinfo/i-d-announceInternet-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
>
>
>
>
>
>
>
>_______________________________________________
>v6ops mailing list
>v6ops@ietf.org
>https://www.ietf.org/mailman/listinfo/v6ops