Re: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-04.txt> (Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC

Ray Hunter <v6ops@globis.net> Fri, 06 September 2013 14:33 UTC

Return-Path: <v6ops@globis.net>
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 935C911E82BF; Fri, 6 Sep 2013 07:33:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.179
X-Spam-Level:
X-Spam-Status: No, score=-2.179 tagged_above=-999 required=5 tests=[AWL=-0.180, BAYES_00=-2.599, J_CHICKENPOX_41=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00fyEd49yMOa; Fri, 6 Sep 2013 07:33:12 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 1A77411E82C2; Fri, 6 Sep 2013 07:33:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 9619087007D; Fri, 6 Sep 2013 16:32:46 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n5PiRlQ5ro0E; Fri, 6 Sep 2013 16:32:46 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 62BA4870076; Fri, 6 Sep 2013 16:32:46 +0200 (CEST)
Message-ID: <5229E788.5030805@globis.net>
Date: Fri, 06 Sep 2013 16:32:40 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Gert Doering <gert@space.net>
References: <20130819135219.8236.40060.idtracker@ietfa.amsl.com> <CAKD1Yr1VpJne1h-Q5xbNMYRhpr_n0Wmn6UqfeG3vEg2MY6ms1g@mail.gmail.com> <94C682931C08B048B7A8645303FDC9F36EF033638D@PUEXCB1B.nanterre.francetelecom.fr> <CAKD1Yr0pqeO9KdcKFWVqWP_5pmZ6fgQ5h4tQ=vOO57d-dg5+DA@mail.gmail.com> <10526_1378283356_5226EF5C_10526_843_1_1B2E7539FECD9048B261B791B1B24A7C511C52CE60@PUEXCB1A.nanterre.francetelecom.fr> <CAKD1Yr3SddZio-vHGHK=5smb94HP58cY05_TGgWQpkS3=Ay8_w@mail.gmail.com> <94C682931C08B048B7A8645303FDC9F36EF033645A@PUEXCB1B.nanterre.francetelecom.fr> <CAKD1Yr0CUzSDv9H1eCUpMRUjBDS2OCkfsfE+S+3J8Z-_6=uVSg@mail.gmail.com> <20130904093105.GM65295@Space.Net>
In-Reply-To: <20130904093105.GM65295@Space.Net>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-04.txt> (Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC
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, 06 Sep 2013 14:33:12 -0000

Gert Doering wrote:
> Hi,
>
> On Wed, Sep 04, 2013 at 06:25:17PM +0900, Lorenzo Colitti wrote:
>>> Sure, but the majority are mandatory, and don't forget that some of them
>>> are quite large (e.g., "implement RFC 6204"). Also, I believe it's not the
>>> IETF's role to produce vendor requirements documents. The considerations
>>> that the IETF deals with are primarily technical, and "we want this stuff
>>> from our vendors" is not a technical issue.****
>>>
>>> *[Med] With all due respect, you are keeping the same argument since the
>>> initial call for adoption and you seem ignore we are not in that stage.
>>> That?s not fair at all.*
>>>
>> I'm just saying it here so that everyone in the community can see it. If
>> it's an IETF document it has to have IETF consensus, and since I feel that
>> the arguments were not properly taken into account in the WG (read:
>> ignored), I think it's important that the community see them before we
>> publish this document.
>
> +1
>
> Gert Doering
>         -- NetMaster

I know I'm formally a couple of days late on the WGLC (work!).

I agree with Lorenzo.

And in any case it isn't ready to ship IMHO. e.g. How can REQ#33 and
REQ#34 be enforced by a manufacturer (during compliance testing)?

-- 
Regards,
RayH