Re: [Roll] routing-dispatch (6lorh) change in ownership from 6LO to ROLL

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Fri, 18 March 2016 10:47 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63A4812D7D3; Fri, 18 Mar 2016 03:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 Jj9IzXy8fy0k; Fri, 18 Mar 2016 03:47:02 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23E1A12D539; Fri, 18 Mar 2016 03:47:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15967; q=dns/txt; s=iport; t=1458298022; x=1459507622; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=c1cA6996k096zLpwLFB3kpldH1YMD5yXIVzLR+u+s+4=; b=mBC4XVKvu1vzIxrC4d7bafa6IWnrJxVx6I1Ni+k57a+vvGNIBOP04exU 8fXS7lIACKe4mZMBedUpEP1xSUcS0CEIJy1QvQQ2/0Hrl4pVD30pw9nNw ZgVhN8URjGHuz28W615NwGmEjuSIEUi45R3wt/ouJ+tFdhSpQ39s6w6XM c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D3AQDx2+tW/4oNJK1egnlMU28GrkaJP?= =?us-ascii?q?oIPAQ2BbyGFbAKBLzgUAQEBAQEBAWQnhEEBAQEELUwQAgEIEQQBASgHIREUCQg?= =?us-ascii?q?BAQQBDQUIiAoDEg68SA2EVQEBAQEBAQEBAQEBAQEBAQEBAQEBAREEhh6DRX+CP?= =?us-ascii?q?oFiSQmFIAWXJTEBhXCGHoFujw6HMYdTAR4BAUKDZWqJZX4BAQE?=
X-IronPort-AV: E=Sophos; i="5.24,354,1454976000"; d="scan'208,217"; a="87902178"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 18 Mar 2016 10:47:00 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u2IAl0NR018238 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 18 Mar 2016 10:47:00 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 18 Mar 2016 05:47:00 -0500
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1104.009; Fri, 18 Mar 2016 05:46:59 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>, "draft-ietf-6lo-paging-dispatch@tools.ietf.org" <draft-ietf-6lo-paging-dispatch@tools.ietf.org>, "draft-ietf-6lo-routing-dispatch@tools.ietf.org" <draft-ietf-6lo-routing-dispatch@tools.ietf.org>, "6lo@ietf.org" <6lo@ietf.org>, Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: routing-dispatch (6lorh) change in ownership from 6LO to ROLL
Thread-Index: AdGAmop9h2qYFLg/TgebhfKJtHrSXwAZ6IKw
Date: Fri, 18 Mar 2016 10:46:42 +0000
Deferred-Delivery: Fri, 18 Mar 2016 10:46:18 +0000
Message-ID: <0a3e093af6aa4648abc0ed798d92ae5c@XCH-RCD-001.cisco.com>
References: <BN1PR03MB0725DAF0801633B06EB4018958B0@BN1PR03MB072.namprd03.prod.outlook.com>
In-Reply-To: <BN1PR03MB0725DAF0801633B06EB4018958B0@BN1PR03MB072.namprd03.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.22.5]
Content-Type: multipart/alternative; boundary="_000_0a3e093af6aa4648abc0ed798d92ae5cXCHRCD001ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/r5Ypt6J36392zmwzMUl-5ebYKI4>
X-Mailman-Approved-At: Fri, 18 Mar 2016 14:07:35 -0700
Cc: "6lo-chairs@tools.ietf.org" <6lo-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, Michael Richardson <mcr+ietf@sandelman.ca>, Suresh Krishnan <suresh.krishnan@ericsson.com>, "James Woodyatt \(jhw@nestlabs.com\)" <jhw@nestlabs.com>, "roll-chairs@tools.ietf.org" <roll-chairs@tools.ietf.org>
Subject: Re: [Roll] routing-dispatch (6lorh) change in ownership from 6LO to ROLL
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 18 Mar 2016 10:47:04 -0000

Hello Gabriel:

That is perfectly fine with me, and I have 2 procedural questions:

1)      Can I submit as draft-roll or do we need an adoption call there?

2)      Draft -6lorh is stable, ready to last call IMHO.  The critical decisions involving formats and header orders are probably already taken. What may be still subject to discussion and that is of specific value to ROLL is bit mapping to protocols or things like that. Since we are transitioning areas, it would be good that 6lo expresses a blessing of the current shape and form so that unless there is a major change, we do not need to recirculate the document again through areas to go to IESG. Based on the fact that 6lo adopted it in the first place, will 6lo be happy that the ROLL WG completes the editorial work on RPL relayed semantics and ships from routing area without handing back the result?

Cheers,

Pascal

From: Gabriel Montenegro [mailto:Gabriel.Montenegro@microsoft.com]
Sent: jeudi 17 mars 2016 23:16
To: draft-ietf-6lo-paging-dispatch@tools.ietf.org; draft-ietf-6lo-routing-dispatch@tools.ietf.org; 6lo@ietf.org; Routing Over Low power and Lossy networks <roll@ietf.org>
Cc: 6lo-chairs@tools.ietf.org; roll-chairs@tools.ietf.org; Michael Richardson <mcr+ietf@sandelman.ca>ca>; Alvaro Retana (aretana) <aretana@cisco.com>om>; Suresh Krishnan <suresh.krishnan@ericsson.com>om>; James Woodyatt (jhw@nestlabs.com) <jhw@nestlabs.com>om>; Ralph Droms <rdroms.ietf@gmail.com>om>; Brian Haberman <brian@innovationslab.net>
Subject: routing-dispatch (6lorh) change in ownership from 6LO to ROLL

Hi folks,

We've had some discussions among the 6lo and ROLL chairs and personnel as well as the responsible AD's (Brian, Alvaro and Suresh) to the effect that the following draft (aka 6lorh) is better suited for ROLL than 6lo:


*        https://tools.ietf.org/wg/6lo/draft-ietf-6lo-routing-dispatch/

This draft uses the framework established in the paging-dispatch draft, which is clearly in 6lo's scope:


*        https://tools.ietf.org/wg/6lo/draft-ietf-6lo-paging-dispatch/



We're moving 6lorh (routing-dispatch) to ROLL. Sure, 6lorh uses something out of 6lo (the paging-dispatch draft), but it is so specific to ROLL that the document belongs there.



This is analogous to how DHC has operated over many years: base DHCP format changes happen in DHC, but applications of DHC mechanisms specific to any given technology are best developed by the relevant WG (of course, with review by DHC to double-check the use of DHC facilities).



Similarly, 6lo will be in the loop to review routing-dispatch, to make sure it uses paging-dispatch properly. But routing-dispatch is so specific to ROLL that further development, WG LC, IESG processing, etc., will happen under ROLL.



Thanks,



Gabriel (on behalf of ROLL and 6LO chairs)