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

joel jaeggli <joelja@bogus.com> Sun, 19 October 2014 22:54 UTC

Return-Path: <joelja@bogus.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3059F1A1A0D; Sun, 19 Oct 2014 15:54:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.769
X-Spam-Level:
X-Spam-Status: No, score=0.769 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RDNS_DYNAMIC=0.982] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LBxvBZV9lQfR; Sun, 19 Oct 2014 15:54:07 -0700 (PDT)
Received: from minorthreat.org (ec2-54-68-221-247.us-west-2.compute.amazonaws.com [54.68.221.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D58FC1A0673; Sun, 19 Oct 2014 15:54:06 -0700 (PDT)
Received: from mb-aye.local (c-67-188-0-113.hsd1.ca.comcast.net [67.188.0.113]) (authenticated bits=0) by minorthreat.org (8.14.9/8.14.9) with ESMTP id s9JMreFi034296 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 19 Oct 2014 22:53:40 GMT (envelope-from joelja@bogus.com)
Message-ID: <54444107.2000908@bogus.com>
Date: Sun, 19 Oct 2014 15:53:59 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:33.0) Gecko/20100101 Thunderbird/33.0
MIME-Version: 1.0
To: ietf@ietf.org
References: <20141002154553.11969.98465.idtracker@ietfa.amsl.com>
In-Reply-To: <20141002154553.11969.98465.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="7m8SH4QQttGT1LF7CfR7O497OCuBbiLgr"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/P7pg87a-daShy95gmqIenbKiQzU
Cc: v6ops@ietf.org, V6ops Chairs <v6ops-chairs@tools.ietf.org>, "<draft-ietf-v6ops-mobile-device-profile@tools.ietf.org>" <draft-ietf-v6ops-mobile-device-profile@tools.ietf.org>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-13.txt> (An Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 19 Oct 2014 22:54:09 -0000

Summarizing What I see here.

The concerns about the breadth or appropriateness of the document are
well understood. The will never be entirely ameliorated but I think we
can live with them.

The substantial changes between the previous last call around draft 8
and the present one draft 13 produced something that I think with minor
misgivings represents working group output and IETF consensus.

Concerns with requirements  for PCP exist related the privacy
implications for such direct mappings,  we were mindful of in the
context of RFC 6887 which we saw fit to publish so I don't see a reason
understanding that, that we would take PcP off the table at this time.

I would characterize the consensus as good enough and would thank those
who invested the time, in commenting and contributing.

Thanks
joel

On 10/2/14 8:45 AM, The IESG wrote:
> 
> The IESG has received a request from the IPv6 Operations WG (v6ops) to
> consider the following document:
> - 'An Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices'
>   <draft-ietf-v6ops-mobile-device-profile-13.txt> as Informational RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2014-10-16. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> This is the second iteration of this document to be IETF Last Called having
> previously been here at draft 04. Substantial changes to the document have 
> occurred inclusive of the removal of much of the normative language. 
> 
> Abstract
> 
> 
>    This document defines an IPv6 profile that a number of operators
>    recommend in order to connect 3GPP mobile devices to an IPv6-only or
>    dual-stack wireless network (including 3GPP cellular network and IEEE
>    802.11 network).
> 
>    This document defines a different profile than the one for general
>    connection to IPv6 cellular networks defined in the IPv6 for Third
>    Generation Partnership Project (3GPP) Cellular Hosts document.  In
>    particular, this document identifies also features to deliver IPv4
>    connectivity service over an IPv6-only transport.
> 
>    Both hosts and devices with capability to share their WAN (Wide Area
>    Network) connectivity are in scope.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-v6ops-mobile-device-profile/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-v6ops-mobile-device-profile/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
>