[v6ops] about the draft /64 'sharing' 'tethering' draft-byrne-v6ops-64share-03

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 08 November 2012 18:35 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2888421F8438 for <v6ops@ietfa.amsl.com>; Thu, 8 Nov 2012 10:35:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.217
X-Spam-Level:
X-Spam-Status: No, score=-10.217 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EYbHrrwmf2oT for <v6ops@ietfa.amsl.com>; Thu, 8 Nov 2012 10:35:05 -0800 (PST)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) by ietfa.amsl.com (Postfix) with ESMTP id 5082C21F842B for <v6ops@ietf.org>; Thu, 8 Nov 2012 10:35:04 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id qA8IZ3vD026715 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <v6ops@ietf.org>; Thu, 8 Nov 2012 19:35:03 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id qA8IZ3Ow028515 for <v6ops@ietf.org>; Thu, 8 Nov 2012 19:35:03 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (arletty1-201-4.intra.cea.fr [132.166.201.4]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id qA8IYmHx029534 for <v6ops@ietf.org>; Thu, 8 Nov 2012 19:35:03 +0100
Message-ID: <509BFB47.2080501@gmail.com>
Date: Thu, 08 Nov 2012 19:34:47 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "v6ops@ietf.org" <v6ops@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [v6ops] about the draft /64 'sharing' 'tethering' draft-byrne-v6ops-64share-03
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Nov 2012 18:35:06 -0000

Hello,

I have the following comments about draft-byrne-v6ops-64share-03.

I walk a fine line of WG with respect to recommendations elsewhere.

This /64 tethering to make a cellular terminal act like an IPv6 hotspot
is highly needed.  The mobile routers I work with highly need this.  To
avoid it I use Mobile IPv6, but that requires HA in the infra.

This is needed not only for 3GPP terminals.  It's also for an ADSL box
which receives a /64 from operator and uses a ptp link from terminal to
infrastructure.

In netext, I wrote an individual submission draft about how to make a
"prefix division" for a Mobile Router (with Proxy MIP in the infra).
It's section 2.1 "HNP Division" of draft-petrescu-netext-pmip-nemo-01.txt.

With respect to technical detail to your draft...

I think an example is very good.  You give an example but it could be
better illustrated.

Then,

> When tethering a LAN, the UE may then assign that same address to its
> LAN interface with a /64 subnet

I have some doubts about this, but they could be clarified.  For example,

When the same address is present on both interfaces, will an application
choose rightly the outgoing interface, or are there risks of choosing
the wrong interface?

To that end, it would be good to explain in the example what are the
routing table entries, exemplify.  Or say that never applications run on
this device, but on the Hosts attached to hotspot.

The reason I am asking this is the following.  In the past there was
much discussion about making an HA (Home Agent) work from MIP to
MIP/NEMO.  The initial proposals also considered this HA to have same
address on an egress and on an ingress interface.  It could work, but as
spec went on we realized there were some problems and dropped that.  I
want to make sure we have no reason here to drop this.

Alex