IETF Logo Mail Archive

Re: [v6ops] draft-ietf-v6ops-64share

Alexandru Petrescu <alexandru.petrescu@gmail.com> Tue, 29 January 2013 16:20 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 CE1EF21F8834 for <v6ops@ietfa.amsl.com>; Tue, 29 Jan 2013 08:20:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.779
X-Spam-Level:
X-Spam-Status: No, score=-9.779 tagged_above=-999 required=5 tests=[AWL=-0.130, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, 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 9U-YNbfF8aYf for <v6ops@ietfa.amsl.com>; Tue, 29 Jan 2013 08:20:14 -0800 (PST)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id F034621F882C for <v6ops@ietf.org>; Tue, 29 Jan 2013 08:20:13 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r0TGKCiW029289 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <v6ops@ietf.org>; Tue, 29 Jan 2013 17:20:12 +0100
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r0TGKCLE013380 for <v6ops@ietf.org>; Tue, 29 Jan 2013 17:20:12 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r0TGK3fb026978 for <v6ops@ietf.org>; Tue, 29 Jan 2013 17:20:12 +0100
Message-ID: <5107F6B2.8070708@gmail.com>
Date: Tue, 29 Jan 2013 17:20:02 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: v6ops@ietf.org
References: <CAD6AjGSEOva1RzDXJqmstFk=13JnPUSWM9rQ3PmXCXPQQwcBDQ@mail.gmail.com> <1358681491.98785.YahooMailNeo@web142502.mail.bf1.yahoo.com> <CAD6AjGSfJHTwL-TM+U68h6SOtcid5JD_0ZJpFufyG3P-bOYtsQ@mail.gmail.com> <1358883507.57517.YahooMailNeo@web142506.mail.bf1.yahoo.com> <CAD6AjGQfpMvR4ETEAyW_WJssdj=bN1PRbQ29K1zNmOX4OgLL7w@mail.gmail.com> <C82845F42F09E94DBCB19F4D06A9DC4B013D3A76E322@HE111490.emea1.cds.t-internal.com>
In-Reply-To: <C82845F42F09E94DBCB19F4D06A9DC4B013D3A76E322@HE111490.emea1.cds.t-internal.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Subject: Re: [v6ops] draft-ietf-v6ops-64share
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: Tue, 29 Jan 2013 16:20:14 -0000

Le 29/01/2013 16:25, holger.metschulat@telekom.de a écrit :
> -----Ursprüngliche Nachricht----- Von: v6ops-bounces@ietf.org
> [mailto:v6ops-bounces@ietf.org] Im Auftrag von Cameron Byrne
> Gesendet: Dienstag, 22. Januar 2013 21:34 An: Mark Smith Cc:
> v6ops@ietf.org Betreff: Re: [v6ops] draft-ietf-v6ops-64share
>
> Cameron,
>
>> I think would rather avoid any of this translational bridging
>> business.  And in fact, i am only trying to document  running code
>> to avoid multiple divergent methods of achieving the same goal.
>
>> That said, it appears a few folks (Rajiv and Alex) have some
>> indigestion over having one IP address in multiple places.  It
>> works for me, but i can accept that it may not work well for
>> others.
>
> I personally also don't like the idea of having the same IP address
> in two places. I always look at this as the UE's own IPv6 address
> attached to an internal interface int0 inside the UE, and the UE
> building a "virtual brigde" connecting the wlan0, int0 and wwan0
> interface together. In front of the wwan0 interface, there is a
> matching logic adapting Ethernet L2 towards the WWAN L2

The bridging of the virtual interface and the other two real interface-
I could visualize it, with a single address attributed to the virtual
interface.

However, I wonder what this bridging may mean to routing.  If all the
interfaces on this machine are 'bridged' (maybe brconfig, brctl) then is
there any IP routing possible on this machine.

I guess the two subnets - the one on wwan0 and the one on wlan0 - shoudl
stay separate scope.  One wouldn't want a NS sent by a Host in the WLAN
subnetwork be transmitted to the WWAN subnetwork.

> the same way as it was done when connecting Frame Relay PPP
> connections into Ethernet interfaces (Juniper calls this
> "translational crossconnects"; I am sure other vendors have similar
> implementations as well).

I guess the figure there would be similar, but I have never seen a Frame
Relay.

Alex

> However, I don't have a good word for describing such a scenario.
>
> Holger _______________________________________________ v6ops mailing
> list v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>
>

v2.23.0 | Report a Bug | By Email