Re: [Roll] [6lo] RPL artifact compression discussion

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 23 March 2015 22:48 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D5C51A00FA; Mon, 23 Mar 2015 15:48:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 Ov6E6BOSd7yw; Mon, 23 Mar 2015 15:48:49 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 738BC1A0022; Mon, 23 Mar 2015 15:48:49 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id C7D13200A1; Mon, 23 Mar 2015 18:58:36 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 388BA63B76; Mon, 23 Mar 2015 18:48:48 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 1F2C3636A2; Mon, 23 Mar 2015 18:48:48 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "6lo@ietf.org" <6lo@ietf.org>, "roll@ietf.org WG" <roll@ietf.org>
In-Reply-To: <CADrU+d+vPHN-Z0ZzYB0L98b5L1Yy3Vy02a1vTt0=vBvA3q6uuw@mail.gmail.com>
References: <BN1PR03MB0729E0B05811AA6C648B2DD950F0@BN1PR03MB072.namprd03.prod.outlook.com> <22866.1427143218@sandelman.ca> <CADrU+d+vPHN-Z0ZzYB0L98b5L1Yy3Vy02a1vTt0=vBvA3q6uuw@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Mon, 23 Mar 2015 18:48:48 -0400
Message-ID: <17230.1427150928@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/U08vALPsDr07Kpclf3rWrRGzMDg>
Subject: Re: [Roll] [6lo] RPL artifact compression discussion
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2015 22:48:51 -0000

Robert Cragie <robert.cragie@gridmerge.com> wrote:
    > <RCC>There is - it's IPHC. You can use IPHC twice as we discussed in
    > the recent call.</RCC> 

Thank you for your reply, and reminding me that I didn't followup with you on
this question.   So, I'm not really sure how you signal this.

This is what I see at this time:

15.4 header stuff.
Dispatch    = LOWPAN_IPHC (0b1110 111N).      (rfc6282. section 4/5)
            here we want to put another compress header, so N=1.
            base format, with "NH=1"
                 NHC_1=0b1110 EID NH      EID=5,NH=1
            = here we would have RPI
                 NHC_2=???

Now if NHC_2 = 7, then an IPIP header follows.
If the NHC_1's NH=0, then an entire byte follows for something that
doesn't fit into the EID (e.g. IPsec ESP).

I don't know I signal that what follows the RPI isn't an IPv6 header
(uncompressed), but rather another LOWPAN_IPHC.

Maybe you have a better way of presenting this detail.

-- 
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-