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

Lorenzo Colitti <lorenzo@google.com> Mon, 19 November 2012 08:39 UTC

Return-Path: <lorenzo@google.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 C8C6521F8488 for <v6ops@ietfa.amsl.com>; Mon, 19 Nov 2012 00:39:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.64
X-Spam-Level:
X-Spam-Status: No, score=-102.64 tagged_above=-999 required=5 tests=[AWL=-0.264, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 0aOSH4am3Znn for <v6ops@ietfa.amsl.com>; Mon, 19 Nov 2012 00:39:50 -0800 (PST)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id D5EAC21F847C for <v6ops@ietf.org>; Mon, 19 Nov 2012 00:39:49 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id ef5so4957367obb.31 for <v6ops@ietf.org>; Mon, 19 Nov 2012 00:39:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=xl5VjbWqkzVNhQ0ugtiPjiaM20fg50t1Rv2oPpGxHC4=; b=GBHG8InnwrdXIe400l5dSz6ybI5c2v7WYxPK7oLQhihCkhLJSrjnDcANy6mzVF9J5Y JW+eX/O2FLgh7VHtUR+7JsokbAahXccJUPbDd2EqvHwRZ/MpCw9i4r0gHNtEqH6n3jdK LsxPAcoHxV4APYCBSbvxcT4Jd/KbgZxfUGgk0P9jy93uKXV+H1n0KxbxTJoOj00VToMy rUGAbNjP+teYH9QyOGhTcLsTB58+S18l2zDyA4Uap7E1CpYIHcNAZx3VsmCKTPMaCPjz KTC5ZTsc9g6Dnwxk28Y/I+PpM05Oi3+D7C7uWticjoi/d9zw576wOtZ6y48HOJq6Vk5O +Stw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=xl5VjbWqkzVNhQ0ugtiPjiaM20fg50t1Rv2oPpGxHC4=; b=Xzsl5/A3+ZmIWtB1CUj00tB4p3OxmRMp5LhktN79U8aMTGJRluTbSxKeWtMGmr0VYR QxpwuRr6EigxXo95Yh4soCmtsviGgd1WrY5NNCoJHuMm8CWOYgDyjn06VeF5scUwjB3T ATxE1+SsE8n7ojkuWgDXTNXUErn+PhhkLLaWUZ25BhL2z2/7P0pWHE1yLeW3374x0KJ1 z87LKDdDW9I6284i6KXZ98UFy0QXpTgO6X1D8MVL90Teh8Yqv1gB7NIblORVGSn0W8Ng DyTi1W/RMOydCs442kaK6+w2IloFQquK80wGCDrls7O9CM1DXXLeOhL/IMo5ETJ1XGCJ hdCQ==
Received: by 10.60.32.135 with SMTP id j7mr9619415oei.132.1353314389062; Mon, 19 Nov 2012 00:39:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.111.99 with HTTP; Mon, 19 Nov 2012 00:39:28 -0800 (PST)
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36E947B1328@PUEXCB1B.nanterre.francetelecom.fr>
References: <94C682931C08B048B7A8645303FDC9F36E947B1328@PUEXCB1B.nanterre.francetelecom.fr>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 19 Nov 2012 17:39:28 +0900
Message-ID: <CAKD1Yr0PcobuWwu+Dp36NHaFRyinD1SRV0WPk792h9EwwsuFmQ@mail.gmail.com>
To: mohamed.boucadair@orange.com
Content-Type: multipart/alternative; boundary=e89a8fb1f8266df2d904ced50fdd
X-Gm-Message-State: ALoCoQkgn6LMkHx1UT1neOi2dz4zM+FVvQvEgNdUtZ0ZpTm86Vh8myRnj3G+cIKT5AE7VOGBp/QQ3ODEGhJL96ZI71+raqspMgfCNX2+7pUXkL7U/HoTvqSVIruF/3emgLivlXLugch1FecJQbRMk6eKHrX7uuCanPn8cf1Og1S/rS5w/zgOTTvOmw01xzfnEHiCDcNKGlIq
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 08:39:50 -0000

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-requirements
>
> 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>directoriestories:
> 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
>