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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 24 January 2013 13:00 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 C5A9921F89EE for <v6ops@ietfa.amsl.com>; Thu, 24 Jan 2013 05:00:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.799
X-Spam-Level:
X-Spam-Status: No, score=-9.799 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3, 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 p82t1wAvPoUQ for <v6ops@ietfa.amsl.com>; Thu, 24 Jan 2013 05:00:51 -0800 (PST)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) by ietfa.amsl.com (Postfix) with ESMTP id ED89C21F8960 for <v6ops@ietf.org>; Thu, 24 Jan 2013 05:00:50 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r0OD0n2A024550 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 24 Jan 2013 14:00:49 +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 r0OD0nLT016721; Thu, 24 Jan 2013 14:00:49 +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 r0OD0jaP018131; Thu, 24 Jan 2013 14:00:49 +0100
Message-ID: <5101307D.8050402@gmail.com>
Date: Thu, 24 Jan 2013 14:00:45 +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: Vízdal Aleš <ales.vizdal@t-mobile.cz>
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> <1808340F7EC362469DDFFB112B37E2FCC6CF9C940A@SRVHKE02.rdm.cz> <51010548.3010104@gmail.com> <1808340F7EC362469DDFFB112B37E2FCC6CF9C98B3@SRVHKE02.rdm.cz>
In-Reply-To: <1808340F7EC362469DDFFB112B37E2FCC6CF9C98B3@SRVHKE02.rdm.cz>
Content-Type: text/plain; charset="ISO-8859-2"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
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: Thu, 24 Jan 2013 13:00:51 -0000

Le 24/01/2013 13:58, Vízdal Aleš a écrit :
>> -----Original Message----- From: v6ops-bounces@ietf.org
>> [mailto:v6ops-bounces@ietf.org] On Behalf Of Alexandru Petrescu
>> Sent: Thursday, January 24, 2013 10:56 AM To: v6ops@ietf.org
>> Subject: Re: [v6ops] draft-ietf-v6ops-64share
>
> Alex,
>
>>> To my understanding there is no link-layer addressing at the
>>> 3GPP interface, so it wouldn't be easy to do l2 bridging.
>>
>> Well it depends.
>>
>> In general I think very many cellular interfaces on the UE do not
>> use link-layer addressing.  The devices have 'all-zero' MAC
>> address, use the "NO_ARP" flag and so on.
>
> What are you seeing is not the 3GPP link traffic, but the Ethernet
> emulation done by the modem firmware.

YEs to some extent.

But what that firmware does may be more than simple emulation.

(an emulator would not generate packets at its will but only upon request).

An IP stack is happier to work with an emulator than with a 3GPP link.

> To be able to sniff on the 3GPP interface level you would need a
> tracer to see what's happening there.

Ok, but what is a tracer?  Where can I obtain one?

Do you mean wireshark?

Alex

>
>> However, more recent devices (e.g. USB keys for LTE: bandrich
>> C502, huawei e392, more) using qualcomm chipsets in some instances,
>> using 'qmi' interfaces and drivers, exhibit a form of link-layer
>> addressing.
>>
>> First, these devices use centrally-allocated IEEE identifiers for
>> Company_ID.  Suprisingly to some, the well known file oui.txt
>> exhibits such id's for manufacturers of 3GPP-compatible equipment
>> (traditionally it mentions only manufacturers of IEEE-compatible
>> equipment).
>>
>> Second, some kernel modules, for instance in the 'qmi' family, form
>> the last 3 bytes of a 48bit address.
>>
>> Finally, wireshark dumps of packets emitted by these cellular
>> interfaces show Ethernet headers with MAC src and dst addresses,
>> and interprets them according to oui.txt (wireshark interpretation
>> is a good indicator about the width of the spread of some
>> protocol).
>>
>> These three aspects make me think that maybe the new and future
>> cellular interfaces may be more and more link-layer addressable.
>>
>> One consequence is the arrival of the use of classical ND on these
>> links, and, why not, the bridging forms which are customary on
>> Ethernet links.
>>
>> (caveat emptor: yes much intelligence exists in the small computer
>> in a USB key that may make some things appear what they are not -
>> proxying, on behalf of, etc. - yet they don't run the IP stack,
>> it's the USB Host computer which runs the stack).
>>
>> Alex
>
> Ales
>
>