Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roaming-analysis-02.txt

Mikael Abrahamsson <swmike@swm.pp.se> Mon, 04 August 2014 16:31 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 EF9CF1A0081 for <v6ops@ietfa.amsl.com>; Mon, 4 Aug 2014 09:31:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.952
X-Spam-Level:
X-Spam-Status: No, score=-3.952 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] 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 Yaiu1s8mZbbm for <v6ops@ietfa.amsl.com>; Mon, 4 Aug 2014 09:31:05 -0700 (PDT)
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 777201A040F for <v6ops@ietf.org>; Mon, 4 Aug 2014 09:31:05 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 63FFCA3; Mon, 4 Aug 2014 18:31:03 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1407169863; bh=Ke0MWFhM+jPPzvHSeuL+HJVS1zzVmWCabawXLZHoaQg=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=hr3XLbbSkce7e6smvprGPxdB9UZp4ESAMaVuMum59Ud9373te59LfgdN4u0YWnViN r+vQ0k83twhoMQ1Z33prwCtWl/Md+7QwEwZ/3kFj3GxLmMDl2IX6vAwgz2p1+02goj L8rFGjNfgMGhlXrnuXVjb+Qc/dYzWpwQmAlY2JKY=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 57CFFA2; Mon, 4 Aug 2014 18:31:03 +0200 (CEST)
Date: Mon, 04 Aug 2014 18:31:03 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ross Chandler <ross@eircom.net>
In-Reply-To: <8E890204-B4A8-4EDC-BFF6-FC33A2C30FC6@eircom.net>
Message-ID: <alpine.DEB.2.02.1408041827340.7929@uplift.swm.pp.se>
References: <20140804010755.5662.75071.idtracker@ietfa.amsl.com> <CAM+vMETtTvs9oeNtg5T7ReyyH1o3g7VXtpG+g-3bKbm6dpAoEQ@mail.gmail.com> <8E890204-B4A8-4EDC-BFF6-FC33A2C30FC6@eircom.net>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-137064504-855693784-1407169863=:7929"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/R9xNyOqUz06fMoCyLQ-NsPU2ZUA
Cc: v6ops@ietf.org
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roaming-analysis-02.txt
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, 04 Aug 2014 16:31:08 -0000

On Mon, 4 Aug 2014, Ross Chandler wrote:

> IMHO the main utility of this draft is to create a point of reference to the gap in
> the standards created by the introduction of support for dual-stack over a single
> radio bearer in separate 3GPP Releases for PDP/PDN context creation.
> To that end I’d like it to have clearer recommendations on how to close that gap.

My opinion is not that any part of the standard is the problem, but rather 
buggy implementations.

> e.g. New HLR/HSS functionality to by default restrict the sending 
> PDP-Ext-Type/IPv4v6 with a whitelist of known good networks. Also the 
> complement the default allow sending of PDP-Ext-Type/IPv4v6 with a 
> network blacklist.

These are operational requriements, and I fully support putting them in 
some kind of document, but the question is if it's really "roaming 
analysis" anymore. The language would need to be very careful not to make 
any recommendations then (?), but rather suggest possible ways of 
working around the problems seen.

> Section 7, discussions,  says “dual-stack deployment is recommended in most cases”.
> Is that still the consensus position?  Going straight to single-stack IPv6 is looking very viable now
> when the UE supports a method of providing translated IPv4 access over the IPv6 PDP/PDN
> connection.

I don't think there is consensus here. The draft could point out pros and 
cons with each approach.

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