Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call

Mikael Abrahamsson <swmike@swm.pp.se> Fri, 20 February 2015 18:30 UTC

Return-Path: <swmike@swm.pp.se>
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 EF7761A6F21 for <v6ops@ietfa.amsl.com>; Fri, 20 Feb 2015 10:30:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.961
X-Spam-Level:
X-Spam-Status: No, score=-3.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 18i35qoE6l0d for <v6ops@ietfa.amsl.com>; Fri, 20 Feb 2015 10:30:38 -0800 (PST)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 537391A020D for <v6ops@ietf.org>; Fri, 20 Feb 2015 10:30:38 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 3BA0AA2; Fri, 20 Feb 2015 19:30:17 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424457017; bh=Gl0MRNe2BAVxmS2hsmrVRSURAFPukUq0Dc9vlHoZt6U=; h=Date:From:To:Subject:In-Reply-To:References:From; b=bfbjnhOVZr9zKEqUUv3FfuzPksAetcIMZB3S4xTLoNwnphGezKHpnD2ZPs/YG9v2t OFsiziF3E9Nq673Za4Ot2TxH8Ym47HBqwAWZcelZ/CzgYY3OPu02wLZtCZ6zqA0Ub7 LZWpQCzVZBmffdeUKm+NDg1rt/Zs51R5Ww1NAoIc=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 34129A1 for <v6ops@ietf.org>; Fri, 20 Feb 2015 19:30:17 +0100 (CET)
Date: Fri, 20 Feb 2015 19:30:17 +0100
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: V6 Ops List <v6ops@ietf.org>
In-Reply-To: <8B808F0C-1AA8-4ABE-A06E-80652B9C1498@cisco.com>
Message-ID: <alpine.DEB.2.02.1502201513320.4007@uplift.swm.pp.se>
References: <8B808F0C-1AA8-4ABE-A06E-80652B9C1498@cisco.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/5ecaMpORI4bZtI64xDoUZeCr71E>
Subject: Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call
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: Fri, 20 Feb 2015 18:30:40 -0000

On Wed, 28 Jan 2015, Fred Baker (fred) wrote:

> Please read it now, and comment. This WGLC will run until 15 February.

I have re-read the latest incarnation just now. I am going to treat it as 
if I never read it before:

1.2.

I know what a "shorter prefix than /64" is. A lot of readers might not, so 
I would like to insert at "(larger)" in there, or similar text.

C_REC#2:

Second paragraph, suggest text to clarify that adding the second PDP 
context is to achieve dual stack connectivity by means of these two PDP 
contexts.

C_REC#6:

"restarts the ongoing applications". I don't like this wording, "will 
interrupt existing network connections" or similar text would be better.

C_REC#7:

typo:

"The purpose of the of the roaming profile is"

C_REC#8:

I don't understand the reference to 6052. Is this a referral to networks 
with NAT64 and/or 464XLAT? Then I think this should be clearer.

L_REC#4: Isn't this a duplication of one of the C_RECs?

Summary:

I think this kind of document is valuable. Many operators do not have 
staff with right skill level to put in the requirements towards equipment 
manufacturers, and in some markets, the equipment manufacturers are 
selling directly to consumers without discussing details with operators. I 
also feel that the vendors of mobile equipment would benefit from having a 
more unified set of requirements from the operators.

Either these requirements can be gathered within the IETF for IP related 
matters, or operators can try to do it in another venue. I don't see why 
the IETF can't be the venue for this.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se