[Roll] FW: New Version Notification for draft-thubert-6lo-routing-dispatch-04.txt

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Tue, 07 July 2015 09:52 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id B3E961A877D; Tue, 7 Jul 2015 02:52:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id qIaggXPJMexg; Tue, 7 Jul 2015 02:52:46 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4D391A8776; Tue, 7 Jul 2015 02:52:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4742; q=dns/txt; s=iport; t=1436262765; x=1437472365; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=edbwWr70gN7O1bt+5Ptf2H8NfOnetzs304MjytdVsVU=; b=Vk/rLQrXkTnUS/KYUQPhkNPf7LvqUkOoTdE52FHLrb+GI20MfyiLuUTe VqWu8I1Ed2ImlX4f4BXEbCKc3KEaMwlBVj8mPtRbeBLU3gOUWAeAWGUVC xkyuXKsQqbqe70djMTfRdosS5XZe5KErTfROsp9/FS0DAa/Xo+NX3I+t0 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.15,422,1432598400"; d="scan'208";a="9501272"
Received: from rcdn-core-8.cisco.com ([]) by rcdn-iport-5.cisco.com with ESMTP; 07 Jul 2015 09:52:44 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com []) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t679qjAS025932 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 7 Jul 2015 09:52:45 GMT
Received: from xmb-rcd-x01.cisco.com ([]) by xhc-rcd-x14.cisco.com ([]) with mapi id 14.03.0195.001; Tue, 7 Jul 2015 04:52:44 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>
Thread-Topic: New Version Notification for draft-thubert-6lo-routing-dispatch-04.txt
Thread-Index: AQHQs1XApl1qaVb6L0KeY9/7tpYI8J3PzNEg
Date: Tue, 7 Jul 2015 09:52:44 +0000
Deferred-Delivery: Tue, 7 Jul 2015 09:51:48 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD849F044E4@xmb-rcd-x01.cisco.com>
References: <20150630165644.26795.43642.idtracker@ietfa.amsl.com>
In-Reply-To: <20150630165644.26795.43642.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/rGbDfQLJJj6A0y13B2Kk9TgwvQ4>
Subject: [Roll] FW: New Version Notification for draft-thubert-6lo-routing-dispatch-04.txt
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 07 Jul 2015 09:52:47 -0000

Dear all:

We are still not there yet for the compression of RPL artifacts! But good progress was made.
We have most of the compression done, what's left is the dispatch game.

This version of eth draft proposes 3 ways to adapt 6LoWPAN while maintaining backward compatibility with RFC4944, and our hope is that we select one in Prague so we can ship the draft. Option 1 is what we proposed at the last IETF, with an alt twist in it. Option 2 and 3 are new. 

Please consider those options, and come discuss them at 6Lo:

      Option 1 considers that a network where this specification applies
      is physically separate from a network where the Mesh Header
      defined in [RFC4944] is used.  With that assumption, the Mesh
      Header dispatch space can be reused.  A variation is proposed
      whereby the NALP pattern 00xxxxxx is reused instead of the Mesh
      Header pattern.

      Option 2 defines a new Separator Dispatch value that indicates
      that no Mesh Header is present in the remainder of the packet.  If
      the 10xxxxxx pattern is found in the packet after this new
      Separator Dispatch, then this specification applies.  It is
      suggested that the new Separator Dispatch would also enable to
      reuse patterns 00xxxxxx and 11xxxxxx in the future.

      Option 3 uses values in pattern 11xxxxxx that are free to this
      date, avoiding patterns 11000xxx and 11100xxx that are used for
      the Fragmentation Header as defined in [RFC4944].



-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: mardi 30 juin 2015 18:57
To: Robert Cragie; Pascal Thubert (pthubert); Pascal Thubert (pthubert); Laurent Toutain; Carsten Bormann; Laurent Toutain; Dr. Carsten Bormann; Robert Cragie
Subject: New Version Notification for draft-thubert-6lo-routing-dispatch-04.txt

A new version of I-D, draft-thubert-6lo-routing-dispatch-04.txt
has been successfully submitted by Pascal Thubert and posted to the IETF repository.

Name:		draft-thubert-6lo-routing-dispatch
Revision:	04
Title:		A Routing Header Dispatch for 6LoWPAN
Document date:	2015-06-30
Group:		Individual Submission
Pages:		23
URL:            https://www.ietf.org/internet-drafts/draft-thubert-6lo-routing-dispatch-04.txt
Status:         https://datatracker.ietf.org/doc/draft-thubert-6lo-routing-dispatch/
Htmlized:       https://tools.ietf.org/html/draft-thubert-6lo-routing-dispatch-04
Diff:           https://www.ietf.org/rfcdiff?url2=draft-thubert-6lo-routing-dispatch-04

   This specification provides a new 6LoWPAN dispatch type for use in
   Route-over and mixed Mesh-under and Route-over topologies, that
   reuses the encoding of the mesh type defined in RFC 4944 for pure
   Mesh-under topologies.  This specification also defines a method to
   compress RPL Option (RFC6553) information and Routing Header type 3
   (RFC6554), an efficient IP-in-IP technique and opens the way for
   further routing techniques.  This extends 6LoWPAN Transmission of
   IPv6 Packets (RFC4944), and is applicable to new link-layer types
   where 6LoWPAN is being defined.


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat