IETF Logo Mail Archive

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

Ross Chandler <ross@eircom.net> Thu, 07 August 2014 10:53 UTC

Return-Path: <ross@eircom.net>
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 7E3521B2A5F for <v6ops@ietfa.amsl.com>; Thu, 7 Aug 2014 03:53:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-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 BgxL_zz-xUyW for <v6ops@ietfa.amsl.com>; Thu, 7 Aug 2014 03:53:56 -0700 (PDT)
Received: from mail01.svc.cra.dublin.eircom.net (mail01.svc.cra.dublin.eircom.net [159.134.118.17]) by ietfa.amsl.com (Postfix) with SMTP id 50AA71B2A5B for <v6ops@ietf.org>; Thu, 7 Aug 2014 03:53:56 -0700 (PDT)
Received: (qmail 6069 messnum 5469359 invoked from network[213.94.190.14/avas02.vendorsvc.cra.dublin.eircom.net]); 7 Aug 2014 10:53:55 -0000
Received: from avas02.vendorsvc.cra.dublin.eircom.net (213.94.190.14) by mail01.svc.cra.dublin.eircom.net (qp 6069) with SMTP; 7 Aug 2014 10:53:55 -0000
Received: from mac1.home.ross.net ([159.134.196.35]) by avas02.vendorsvc.cra.dublin.eircom.net with Cloudmark Gateway id bmtr1o01C0mJ9Tz01mtujD; Thu, 07 Aug 2014 11:53:55 +0100
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ross Chandler <ross@eircom.net>
In-Reply-To: <AFAB9759B1DE4F4187483FC509B501990119F9006A42@HE111490.emea1.cds.t-internal.com>
Date: Thu, 07 Aug 2014 11:53:50 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1E4A4E4A-321E-4821-85EF-8E1AC29C8528@eircom.net>
References: <256EAE0B-5C11-42C7-BCA1-CEC7EE6713A7@cisco.com> <53DFD634.4020304@fud.no> <DE860EBC-171E-46E7-A3B6-5E8B79A453CC@cisco.com> <53DFEC6C.3010707@gmail.com> <CAD6AjGRUWxT5XiNxMi_S5VgYtGMLb_FVHXN-ZfGpcY=geix15g@mail.gmail.com> <53E06AC9.9010908@fud.no> <CAD6AjGTwt-20gXs=RUH5zbhT+g3HKrvXHX3FnShjF1srqU21Fw@mail.gmail.com> <94146541-768B-4853-A011-7558655C361C@eircom.net> <53E11795.7060305@fud.no> <DF75AC0C-098C-4EC8-9598-6F003E1887AA@eircom.net> <CAM+vMERzKa64qyUmmp8j_0e+Sxe4zXdUQwkjrRQe910=Rz+==A@mail.gmail.com> <3B143C5A-875A-4E6F-B34A-A354758E1893@eircom.net> <CAM+vMERpZYt3VyWJgp_+GVsMLDj=4rp+MAts5veL2uKCQp_LQg@mail.gmail.com> <3268A775-40CE-4FEA-9B09-846D35376ADD@eircom.net> <AFAB9759B1DE4F4187483FC509B501990119F9006A42@HE111490.emea1.cds.t-internal.com>
To: holger.metschulat@telekom.de
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/exrzjaUEqCR7TaJCIF7_HnFZYME
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: Thu, 07 Aug 2014 10:53:58 -0000

On 7 Aug 2014, at 11:47, <holger.metschulat@telekom.de> <holger.metschulat@telekom.de> wrote:

>> No.  I'm noting that the first stage for a Mobile operator in adopting IPv6 in the user plane is to prepare 
>> their RANs and SGSN/MMEs for it.
> 
>> When that is done an easy next step is to let visitors from other operators that are ahead in deploying IPv6 
>> establish IPv6 PDP/PDN connections to their home GGSN/PGW.
> 
> But then, ticking the correct "I am IPv6 capable" and "I am IPv4v6 capable" boxes in the IR.21 database should not be forgotten...
> 
> Holger

Yes. There should be a reference to their IR.21 responsibilities. 

Ross

v2.23.0 | Report a Bug | By Email