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

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Thu, 27 November 2014 14:03 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 848F81A0119; Thu, 27 Nov 2014 06:03:16 -0800 (PST)
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 pk112fBUnS39; Thu, 27 Nov 2014 06:03:14 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 743901A008B; Thu, 27 Nov 2014 06:03:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3666; q=dns/txt; s=iport; t=1417096994; x=1418306594; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=2/o5u2xaeuacrGK0pb1ZaF56ZaTY2Zq8D1oiFDrr58Y=; b=V+O5eV4OXTtg0YL9LFPAubB8lComfcMZqdZRfRbmuoOJV2qkvQPAbIty 0kF59kxbAMWNo/oNQHr1j/hkDr4aakxoK9L3Z8ENI3/33Xac89rphUym7 OVrS5nTvl5I8U/ylJsJKhB/anEKNNu2PaAnnkBiH9QUfeEyq9NdWkv4SK s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.07,469,1413244800"; d="scan'208";a="100674078"
Received: from alln-core-3.cisco.com ([]) by alln-iport-4.cisco.com with ESMTP; 27 Nov 2014 14:03:13 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com []) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id sARE3DnL019583 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 27 Nov 2014 14:03:13 GMT
Received: from xmb-rcd-x01.cisco.com ([]) by xhc-aln-x04.cisco.com ([]) with mapi id 14.03.0195.001; Thu, 27 Nov 2014 08:03:13 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "6lo@ietf.org" <6lo@ietf.org>
Thread-Topic: New Version Notification for draft-thubert-6lo-routing-dispatch-00.txt
Thread-Index: AQHQCkcKV0+2qTicPkyTS/yZFWZX4Jx0ey0w
Date: Thu, 27 Nov 2014 14:03:12 +0000
Deferred-Delivery: Thu, 27 Nov 2014 14:03:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD848A7DE36@xmb-rcd-x01.cisco.com>
References: <20141127133537.6084.69209.idtracker@ietfa.amsl.com>
In-Reply-To: <20141127133537.6084.69209.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/qt1VKDUXNWimwN02nX_06o3kh_8
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>
Subject: [Roll] FW: New Version Notification for draft-thubert-6lo-routing-dispatch-00.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: <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: Thu, 27 Nov 2014 14:03:16 -0000

Dear all:

This is a response to the question about the compression of RFC 6553 on top of RFC 6554.
It seems exaggerated to consume a dispatch type for the RPL option only. 
But here, we introduce a routing header which is the equivalent of the mesh header in RFC 4944; we propose a compressed TLV format that can encode RH3, RPL option, IP-in-IP, and is further extensible, for instance for upcoming  BIER.
As it goes, the mesh header consumes 1/3 of all the 6LoWPAN addressable space for application only in Mesh-under. 
This draft reuses that space in Route-over with the assumption that Route-over will not co-exist in a sma enetwork with Mesh-under encoded in the RFC 4944 fashion.
If there is effectively a need for co-existence, devices have to implement the new Mesh-under format that is also proposed in the draft.

Comments welcome,

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: jeudi 27 novembre 2014 14:36
To: Pascal Thubert (pthubert); Pascal Thubert (pthubert); Laurent Toutain; Carsten Bormann; Laurent Toutain; Dr. Carsten Bormann
Subject: New Version Notification for draft-thubert-6lo-routing-dispatch-00.txt

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

Name:		draft-thubert-6lo-routing-dispatch
Revision:	00
Title:		A Routing Header Dispatch for 6LoWPAN
Document date:	2014-11-25
Group:		Individual Submission
Pages:		19
URL:            http://www.ietf.org/internet-drafts/draft-thubert-6lo-routing-dispatch-00.txt
Status:         https://datatracker.ietf.org/doc/draft-thubert-6lo-routing-dispatch/
Htmlized:       http://tools.ietf.org/html/draft-thubert-6lo-routing-dispatch-00

   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