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

Ted Lemon <Ted.Lemon@nominum.com> Mon, 09 September 2013 21:20 UTC

Return-Path: <Ted.Lemon@nominum.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 6F51921E8179; Mon, 9 Sep 2013 14:20:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.393
X-Spam-Level:
X-Spam-Status: No, score=-106.393 tagged_above=-999 required=5 tests=[AWL=0.206, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 by4vVwK9Lku5; Mon, 9 Sep 2013 14:20:44 -0700 (PDT)
Received: from exprod7og128.obsmtp.com (exprod7og128.obsmtp.com [64.18.2.121]) by ietfa.amsl.com (Postfix) with ESMTP id 7E6D621F99DC; Mon, 9 Sep 2013 14:19:53 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob128.postini.com ([64.18.6.12]) with SMTP ID DSNKUi47eR/KVpojX6X25u51DbFch7Y8C8pr@postini.com; Mon, 09 Sep 2013 14:19:53 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 304851B80E5; Mon, 9 Sep 2013 14:19:53 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 26A73190074; Mon, 9 Sep 2013 14:19:53 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 9 Sep 2013 14:19:48 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Owen DeLong <owen@delong.com>
Thread-Topic: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-04.txt> (Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC
Thread-Index: AQHOraCxfmd6tFh7TEyulzq88K5MgJm+XraA
Date: Mon, 09 Sep 2013 21:19:46 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077527D9A6@mbx-01.win.nominum.com>
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> <CAKHUCzwYrjyobah-oPWD3vwUeUH5XZ7U=Fqof-f28tneS8jAvQ@mail.gmail.com> <CAKD1Yr0_yOaDjrH-5K696YaziZZR+EMxdRCf=JZBW5LZgWS45Q@mail.gmail.com> <94C682931C08B048B7A8645303FDC9F36EF06D0A6F@PUEXCB1B.nanterre.francetelecom.fr> <CAKD1Yr3cgJ-xumsMK3eL3zySGsPqXU9uw4L857bJ0VEGcA5mBQ@mail.gmail.com> <94C682931C08B048B7A8645303FDC9F36EF06D0AF5@PUEXCB1B.nanterre.francetelecom.fr> <17! 9F53B5-6217-49A0-B5FE-A88011533860@delong.com> <1808340F7EC362469DDFFB112B37E2FCD2BABB5CCD@SRVHKE02.rdm.cz> <36E78FC1-5CC3-4A22-B231-6E3E10963836@delong.com>
In-Reply-To: <36E78FC1-5CC3-4A22-B231-6E3E10963836@delong.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <BB1CEEE48A01C7409377D4D5CECF73B1@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>, Dave Cridland <dave@cridland.net>
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: Mon, 09 Sep 2013 21:20:51 -0000

Owen, do you have any technical objection to raise about this document, or are you just replying because you like the sound the keys make as you type?

The working group adopted the document, so it's too late to object that the working group shouldn't be working on it.   You can object by pointing out that it doesn't do what it says it's going to do, but if so you'd need to actually make the case that it doesn't do that, not just assert that it doesn't do that.

Your point about RFC 2119 language has been addressed, so there's no sense in re-raising it unless you have some specific objection to state about the way in which it was addressed ("I'm not satisfied" is not a specific objection).

Etc.