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

Gabriel Montenegro <Gabriel.Montenegro@microsoft.com> Tue, 30 June 2015 19:09 UTC

Return-Path: <Gabriel.Montenegro@microsoft.com>
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 C753A1A872F; Tue, 30 Jun 2015 12:09:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 eOrBMFWHJ2b8; Tue, 30 Jun 2015 12:09:35 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0724.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:724]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E136A1A871F; Tue, 30 Jun 2015 12:09:34 -0700 (PDT)
Received: from BN1PR03MB072.namprd03.prod.outlook.com (10.255.225.156) by BN1PR03MB072.namprd03.prod.outlook.com (10.255.225.156) with Microsoft SMTP Server (TLS) id 15.1.195.15; Tue, 30 Jun 2015 19:09:26 +0000
Received: from BN1PR03MB072.namprd03.prod.outlook.com ([169.254.9.150]) by BN1PR03MB072.namprd03.prod.outlook.com ([169.254.9.150]) with mapi id 15.01.0195.005; Tue, 30 Jun 2015 19:09:26 +0000
From: Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, "Routing Over Low power and Lossy networks" <roll@ietf.org>, "6lo@ietf.org" <6lo@ietf.org>
Thread-Topic: New Version Notification for draft-thubert-6lo-routing-dispatch-04.txt
Thread-Index: AQHQs1XApl1qaVb6L0KeY9/7tpYI8J3FRnPAgAAha2A=
Date: Tue, 30 Jun 2015 19:09:25 +0000
Message-ID: <BN1PR03MB072B51CFC978786AE1B75FC95A90@BN1PR03MB072.namprd03.prod.outlook.com>
References: <20150630165644.26795.43642.idtracker@ietfa.amsl.com> <E045AECD98228444A58C61C200AE1BD849EF3FBB@xmb-rcd-x01.cisco.com>
In-Reply-To: <E045AECD98228444A58C61C200AE1BD849EF3FBB@xmb-rcd-x01.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;
x-originating-ip: [2001:4898:80e0:ee43::2]
x-microsoft-exchange-diagnostics: 1; BN1PR03MB072; 5:JPeBO3Wh7AGIfTO44dlU9tP2YbFQawjnpfr7A/EEa42qCMiK3ke1E5zcHEQ4GPk962QQaNijrsTXucJwC/K2CZzvSZuM8a998itWgyIkaN9RYzT6uq2aUt5KCA54KUGo7CffF27bkRKxa4oUH3jbaw==; 24:9U1iXjFpZFGcLOfI8zgAFnG426TQvCmuz4NRNtX+13kuU1IXHu0t+5VOxeGLmiXAg3IxItoR9E4srJ/8zRtap/a+mDkCALpW9isV5zhHRio=; 20:siaH7E24o+3x8x4po39ihF953ibB6RNNmT83OaLEZCLmxcq2/IRXqEwhrJyoYn7J0FaoZn1MHpPR5wduzCHH3Q==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BN1PR03MB072;
x-microsoft-antispam-prvs: <BN1PR03MB072299DF988A3BC668471E195A90@BN1PR03MB072.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401001)(5005006)(3002001); SRVR:BN1PR03MB072; BCL:0; PCL:0; RULEID:; SRVR:BN1PR03MB072;
x-forefront-prvs: 06237E4555
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(13464003)(51704005)(164054003)(377424004)(5003600100002)(86362001)(87936001)(19580395003)(99286002)(19580405001)(230783001)(106116001)(2656002)(50986999)(92566002)(62966003)(77156002)(54356999)(76176999)(122556002)(33656002)(74316001)(5001960100002)(107886002)(46102003)(76576001)(5002640100001)(2501003)(15975445007)(102836002)(2950100001)(2900100001)(5001770100001)(189998001)(3826002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN1PR03MB072; H:BN1PR03MB072.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Jun 2015 19:09:25.7551 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN1PR03MB072
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/Zp_Kan7qE_p5xP6tglEmlanLXsk>
Subject: Re: [Roll] 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, 30 Jun 2015 19:09:38 -0000

Thanks, Pascal.

I see that options 1 and 2 reuse the mesh header. And option 3 reuses NALP. All three of these reuse previously assigned values. 

I was under the impression that one of the options was going to use a new type out of the ESC+<type> space. Sure, as you mention in the new draft revision, that is not defined clearly yet (though there is something being prepared), but neither is any of the stuff in the draft. 

The point is that it would be good to have at least one option that does not reuse anything previously assigned (other than ESC, which is there for that purpose and is in our control to further define).  

Oh, and request noted. It would definitely be good to discuss this in Prague.

Thanks,

Gabriel

> -----Original Message-----
> From: 6lo [mailto:6lo-bounces@ietf.org] On Behalf Of Pascal Thubert
> (pthubert)
> Sent: Tuesday, June 30, 2015 10:05
> To: Routing Over Low power and Lossy networks; 6lo@ietf.org
> Subject: [6lo] FW: New Version Notification for draft-thubert-6lo-routing-
> dispatch-04.txt
> 
> Dear all:
> 
> This new version proposes in section 3 some alternates to the reuse of the
> mesh header. Comments welcome.
> 
> Cheers,
> 
> Pascal
> 
> -----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
> 
> Abstract:
>    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
> 
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
> https://www.ietf.org/mailman/listinfo/6lo