Re: [v6ops] draft-ietf-v6ops-ipv6-roaming-analysis WGLC

Mikael Abrahamsson <swmike@swm.pp.se> Mon, 28 July 2014 07:15 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 23BA91A02DB for <v6ops@ietfa.amsl.com>; Mon, 28 Jul 2014 00:15:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.652
X-Spam-Level:
X-Spam-Status: No, score=-1.652 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] 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 3jvwuaHqoGuS for <v6ops@ietfa.amsl.com>; Mon, 28 Jul 2014 00:15:42 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E22021A02CF for <v6ops@ietf.org>; Mon, 28 Jul 2014 00:15:28 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 0C9D1A1; Mon, 28 Jul 2014 09:15:26 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1406531727; bh=XtaV0JdU5FPSG8p3cl25ZgvfflAH4IIixQwX3x3WqJ8=; h=Date:From:To:Subject:In-Reply-To:References:From; b=GllSnArplJL7PqhLrzSoJYJRrsshKaFWlP1wodCVSSpurbtrpOwahIzhXzQHL80Jr EV+leWop2oN+47/M0QEGwfxWGJ1XsfWfunrAS0AriU0RLJB7uksJyRw/ZTQkcsAC1G o8M9lwuIfZxrzlkkHdxVbTzj7RQ6vzM1rchUT6rc=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 002D99F for <v6ops@ietf.org>; Mon, 28 Jul 2014 09:15:26 +0200 (CEST)
Date: Mon, 28 Jul 2014 09:15:26 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: v6ops@ietf.org
In-Reply-To: <201407271800.s6RI04sj008989@irp-lnx1.cisco.com>
Message-ID: <alpine.DEB.2.02.1407280906590.7929@uplift.swm.pp.se>
References: <201407271800.s6RI04sj008989@irp-lnx1.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; charset="US-ASCII"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/-DUgBOeVqknTma68j6jkGuHrXTk
Subject: Re: [v6ops] draft-ietf-v6ops-ipv6-roaming-analysis WGLC
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: Mon, 28 Jul 2014 07:15:44 -0000

On Sun, 27 Jul 2014, fred@cisco.com wrote:

> This is to initiate a two week working group last call of
> http://tools.ietf.org/html/draft-ietf-v6ops-ipv6-roaming-analysis.
> Please read it now. If you find nits (spelling errors, minor suggested
> wording changes, etc), comment to the authors; if you find greater
> issues, such as disagreeing with a statement or finding additional
> issues that need to be addressed, please post your comments to the
> list.
>
> We are looking specifically for comments on the importance of the
> document as well as its content. If you have read the document and
> believe it to be of operational utility, that is also an important
> comment to make.

I have re-read the document. I still find it useful. However, when reading 
it I can't help of feeling that this document isn't ready for publication 
yet. It definitely needs a do-over when it comes to language and spelling.

Also, on the technical side, I feel the document could be clearer, but I 
don't know exactly how. I know my comment here isn't really helpful, apart 
from saying that the document might need more work.

One thing that came to mind though, would be a section on how to best 
provision users in HLR. At least one vendor I know of, doesn't support 
setting "IPv4v6" on a user in their HLR. In order to support all cases of 
"IPv4", "IPv6" and "IPv4+IPv6" (dual bearer) and "IPv4v6", one needed to 
give the user two profiles, one being IPv4+ext_pdp IPv6, and also 
IPv6+ext_pdp, otherwise the user couldn't connect using IPv6 only.

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