Re: [6lo] New I-D draft-delcarpio-6lo-wlanah-00.txt - HC

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 18 June 2015 12:09 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B215F1A92E5 for <6lo@ietfa.amsl.com>; Thu, 18 Jun 2015 05:09:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 MTdoA074lAu6 for <6lo@ietfa.amsl.com>; Thu, 18 Jun 2015 05:09:47 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42F4B1A894C for <6lo@ietf.org>; Thu, 18 Jun 2015 05:09:47 -0700 (PDT)
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 t5IC9i8f016821 for <6lo@ietf.org>; Thu, 18 Jun 2015 14:09:44 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 821D320452D for <6lo@ietf.org>; Thu, 18 Jun 2015 14:12:31 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 78DBF2044CA for <6lo@ietf.org>; Thu, 18 Jun 2015 14:12:31 +0200 (CEST)
Received: from [127.0.0.1] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t5IC9dgC018151 for <6lo@ietf.org>; Thu, 18 Jun 2015 14:09:44 +0200
Message-ID: <5582B503.1080907@gmail.com>
Date: Thu, 18 Jun 2015 14:09:39 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: 6lo@ietf.org
References: <mailman.2570.1434619616.3530.6lo@ietf.org> <5582A0E6.6040901@ericsson.com>
In-Reply-To: <5582A0E6.6040901@ericsson.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/6lo/HdkIGSBd38tIpJ0EiOTFL8oHj4w>
Subject: Re: [6lo] New I-D draft-delcarpio-6lo-wlanah-00.txt - HC
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jun 2015 12:09:50 -0000

Hi Ines

Le 18/06/2015 12:43, Ines Robles a écrit :
> Hi Alex,
>
> Thank you for your feedback, please find answer below in [IR]
>
>
> On 06/18/2015 12:26 PM, 6lo-request@ietf.org wrote:
>>
>> Ok, let me summarize  instead of turning in circles:
>>
>> I would like to request a modification of that Internet Draft -
>> please add a statement saying that the IPv6 Base Header is
>> mandatory, in clear, in network byte order.
>>
> [IR] IPv6 is part of the stack proposed, sorry I do not understand
> your point. Could you please clarify it. Thanks!

Stacks exhibit layers, not headers.  I am talking headers.

I think you refer to the stack in figure 6, right?

>                               +---------------------+
>                               |    Upper Layers     |
>                               +---------------------+
>                               |       IPv6          |
>                               +---------------------+
>                               |      6LoWPAN        |
>                               +---------------------+
>                               |      802 LLC        |
>                               +---------------------+
>                               | MAC Layer(802.11ah) |
>                               +---------------------+
>                               | PHY Layer(802.11ah) |
>                               +---------------------+


Does that stack correspond to a packet like this(?):

  +--------------------+------------+-------------+------------+-------+
  | 802.11 Data Header | LLC Header | 6lowpan IPHC|IPv6 Header |Payload|
  +--------------------+------------+-------------+------------+-------+

Yes?

>> ROHC (RObust Header Compression RFC6846) is not applied to IP
>> layer, as far as I know, but to upper layers.  Despite being touted
>> decades ago as absolutely necessary for WiFi and cellular, what we
>> use today on these links is pure IP.
>
> [IR]RFC 3843 defines ROHC for IP

RFC3483 "Framework for Policy Usage Feedback for COPS Policy
Provisioning" can not have much to do about compressing IPv6 Base Header.

Or do you think otherwise?

>> and an implementation can be found here
>> http://www.acticom.de/robust-header-compression-2/

Thanks for pointing at it.

That implementation asks for money and I dont have money for it.  So I 
cant look at it.

On another hand, the page seems to be describing the use of ROHC of many
headers ("IPv6" is cited, although not "IPv6 Base HEader") on LTE or 
satellite links.

Running IPv6 over LTE does not require any money - it's open source IPv6
stack on off-the-shelf hardware.  I dont know whether some form of
Header Compression is involved below IP (may or may not).  But I know 
IPv6 runs ok on LTE without any modifications - precisely as it runs on 
Ethernet.

A specification of IPv6 over LTE can not _require_ Header Compression -
it simply does not care whether or not HC is present below it.

Whether LTE link layer uses forms of Header Compression it is not of 
interest to IP.  IP runs over it without caring there is HC or not. 
IPv6-over-LTE can not REQUIRE HC.

For satellite links - I dont know.

> Especially in wireless networks with high error probabilities and
> scarce resources, RoHC and RoHCv2 are the best choice to compress the
> overhead of IP, IPv6, UDP or RTP data.

I wonder what do they mean by the "overhead of IPv6".

Alex

>
>
> Thanks,
>
> Ines.
>
>>
>
>
>
> _______________________________________________ 6lo mailing list
> 6lo@ietf.org https://www.ietf.org/mailman/listinfo/6lo
>