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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 18 June 2015 09:26 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 D57701A7034 for <6lo@ietfa.amsl.com>; Thu, 18 Jun 2015 02:26:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.084
X-Spam-Level:
X-Spam-Status: No, score=-3.084 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 5sUjw1aKfgXO for <6lo@ietfa.amsl.com>; Thu, 18 Jun 2015 02:26:53 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71E8B1A1EFC for <6lo@ietf.org>; Thu, 18 Jun 2015 02:26:53 -0700 (PDT)
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 t5I9QpQG014551; Thu, 18 Jun 2015 11:26:51 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id B0472204251; Thu, 18 Jun 2015 11:29:37 +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 A2D22204326; Thu, 18 Jun 2015 11:29:37 +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 t5I9Qkav031885; Thu, 18 Jun 2015 11:26:50 +0200
Message-ID: <55828ED6.7050103@gmail.com>
Date: Thu, 18 Jun 2015 11:26:46 +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: Carsten Bormann <cabo@tzi.org>
References: <5EF40C5436D7B040B95EE286EE383A9C0BF20226@ESESSMB101.ericsson.se> <5581A8BA.2010202@gmail.com> <5581B60E.1010707@tzi.org>
In-Reply-To: <5581B60E.1010707@tzi.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/6lo/YQC0_fM4flvzB3twwfBycEszyCo>
Cc: 6lo@ietf.org
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 09:26:56 -0000

Carsten,

Le 17/06/2015 20:01, Carsten Bormann a écrit :
> Alexandru Petrescu wrote:
>> The section 8 is about HC.
>>
>> I would like to ask whether HC means to eliminate the IPv6 Base
>> Header and if yes then the subsequent question is whether we can
>> still consider this to be "IPv6 over..." when there is no IPv6.
>>
>> Because RFC2460 says that the IPv6 Base Header is mandatory.
>
> Alex,
>
> you are trying to make this point again and again.

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.

> Indeed, header compression is a concept that is usually not taught at
> universities.  My standard talk about header compression starts with
> pointing out that there isn't even a Wikipedia page about this
> subject!

I am not sure a wikipedia page on Header Compression is necessarily good 
for HC altogether.

If one wants to study Header Compression there is plethora of 
authoritative information in the Information Theory section of your 
University Library.

> However, as manifested in RFC 1144, there is a long tradition of
> using header compression in link layer mappings for the Internet.

I think RFC1144 is no longer in use.  It should be declared Historic.

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.

Am I missing something?

> The fact that you cannot make out the IPv6 header when looking at
> the bytes on the air in a 6LoWPAN doesn't mean it is not being sent.
> It is just encoded in an efficient way.

What is meant by 'encoded in an efficient way'?

If what is meant is substituting a shorter header for the IPv6 Base 
Header then that's obviously not IPv6.  Because the IPv6 Base Header 
must be transmitted in full in clear in network byte-order.  The only 
modifs the network can make to it is decrementing the Hop Limit.

To further understand what is meant by 'encoded in an efficient way' I 
looked at the wireshark dumps using 6lowpan headers on 15.4 at:
http://svn.tools.ietf.org/svn/wg/6lowpan/packets/
(e.g. dis_option7.pcap)
They exhibit that there is a 15.4 header, a 6lowpan header _and_ an IPv6 
Base Header.  Efficiency couldnt mean to insert an additional header:

Ethernet II header                    Ethernet II header
IEEE 802.15.4 Data header             IEEE 802.15.4 Data header
6LoWPAN header                vs.     IPv6 Base Header
IPv6 Base Header                      ICMPv6 header
ICMPv6 header

This is why I dont understand what is meant by 'encoded in an efficient 
way'.

> (This is different from the confused idea of "header stripping",
> where the IP header actually is not made available to the recipient
> in a way such that it can be decoded.)

Well, please clarify: is the IPv6 Base Header present or not?  If it's 
not then it's stripped, right?

Alex

>
> Grüße, Carsten
>
>