IETF Logo Mail Archive

Re: [Roll] stitching PDAO segments

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 28 October 2019 15:34 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 0742012010F for <roll@ietfa.amsl.com>; Mon, 28 Oct 2019 08:34:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, 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 header.b=blXvhLdG; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=tEXApupJ
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 PMvnJEZc75s5 for <roll@ietfa.amsl.com>; Mon, 28 Oct 2019 08:34:43 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE530120098 for <roll@ietf.org>; Mon, 28 Oct 2019 08:34:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11067; q=dns/txt; s=iport; t=1572276882; x=1573486482; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=0ctC+97N1zQkjQ0itQB0nfqqRj7u22LUvpaJc0yxauo=; b=blXvhLdGe1r3uZa+sGAH+pGk4vLEqd3tAUbu7LZDtCZBK1I4UkOINuzh rnAYz5i5lnl4WMcy+nSLIAcOd7UPYmqgnwVu9FZCz/lf4mnHAQvrOH8Ut m8I4HiZNWVolMlwwNl9kDO4cwSVS6B1YGoIHQ+BTCNuz+lW/jbK5SEibl Y=;
IronPort-PHdr: 9a23:GZZhXh3QX10EzaCrsmDT+zVfbzU7u7jyIg8e44YmjLQLaKm44pD+JxKGt+51ggrPWoPWo7JfhuzavrqoeFRI4I3J8RVgOIdJSwdDjMwXmwI6B8vQEVH7MfTndTASF8VZX1gj9Ha+YgBY
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AmAADUCbdd/5FdJa1lGgEBAQEBAQEBAQMBAQEBEQEBAQICAQEBAYFnBQEBAQELAYEbL1AFbFggBAsqh24DhFqGFE6CEJAAgwcDgmCCAYEuFIEQA1QJAQEBDAEBJQgCAQGEQAKDSiQ0CQ4CAwkBAQQBAQECAQUEbYU3DIVRAQEBAQMSGxMBASUTDwIBCBEBAwEBKAcyFAMGCAEBBBMIGoMBgXlNAy4BAgylUAKBOIhggieCfgEBBYUQGIIXAwaBNgGFFYZ5GIFAP4ERRoJMPoJiAQECAYEmHB4rCYMMgiyNQodzmDcKgiSHEIc4hwGZWpZpkR4CBAIEBQIOAQEFgVI5gVhwFYMnUBAUgwaDc4UUhT90AQGBJo8sAQE
X-IronPort-AV: E=Sophos;i="5.68,240,1569283200"; d="scan'208,217";a="657634935"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 28 Oct 2019 15:34:41 +0000
Received: from XCH-RCD-012.cisco.com (xch-rcd-012.cisco.com [173.37.102.22]) by rcdn-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id x9SFYff1031058 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <roll@ietf.org>; Mon, 28 Oct 2019 15:34:41 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-RCD-012.cisco.com (173.37.102.22) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 28 Oct 2019 10:34:41 -0500
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 28 Oct 2019 10:34:40 -0500
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 28 Oct 2019 10:34:40 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=eYtnnubqRYMHF7GaYvv0M6uSNNR2JC1WwhN92o0kP/goiSBp0Pmq1519TdzyMmw2Og7N+i27DM+HfVMda4Iugb14verCkyLek0Xw0ShhoVzJBcxdFnMu0DILVw1X4ws/Bw/TMCWN1gxTKp+/AhFw1rYfNq70TTaOOvFQkrQeHY1wo1LgkEN9n8yMh9HpNs7dlEDP7T4zI3xw2vNMLVNIg8+zysWRpCHwRtKCc6wyFJOT0kjlHgM430BRSKQ9QVLsbwQZEwHKzdRxjYf1pZUhROjrRfLuRmNhJmaFYEtXBHBW+NY7z3KsLtJms/TE5jAamfdImg/VR3vFbcpac20K1w==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=oIjT0dqw/XoGfQ3k63d48jSxyWiK42+KJQks5UzH7ms=; b=NL9o+ozh2vPlGC5I1UC/zdBlERcQDJtkoLdbbb8Ii7yxlRURpvxzJgOSYOZzh+k/iq1EMAM7VTvZPFLiRdxTk9+tM/n+HTQrFal3SmEopKw50YsgEWsOL779lbSE/nE9/nLwfFdqwjFmtMcvFv/81Xgps+W+KZe4avZer3ZTE/3OYT1LyxJ1HrXludj9TJJJ9FBCOgURfls1evrbGpsihAbImU4LIxWMPBr2cFeJUohhnbfdDkG1+6Rc2sh09WAZTXyEOCeG7cOCS6i7WmkKdI3/XW+t6YELcAOqh6E7beaw/TyLz5RagCdCyI9cilR9tLk5TKWi7sxHid32ZY9iow==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=oIjT0dqw/XoGfQ3k63d48jSxyWiK42+KJQks5UzH7ms=; b=tEXApupJuPfElzgr9cIkI9jlOTbUvPMumnCBLwr0QfNMq/j30pS1ryEHaVVv+zER/VEdPBtShOAkGTsk1nSjM1JQYsokp3tW9U8L7GssBN4VlR1h6iWabOADOjp0Y7KrDwkqF+joAlGaDDEHT1BCdSPV4Ilm87w2Moa37g24rZc=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB4366.namprd11.prod.outlook.com (52.135.38.209) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2387.24; Mon, 28 Oct 2019 15:34:39 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::31c9:3a31:3c07:a920]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::31c9:3a31:3c07:a920%6]) with mapi id 15.20.2387.023; Mon, 28 Oct 2019 15:34:39 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: stitching PDAO segments
Thread-Index: AdVCavf1/y2OVF18Rs6j63tFfNF4zQAIinQAEsXh4yA=
Date: Mon, 28 Oct 2019 15:34:21 +0000
Deferred-Delivery: Mon, 28 Oct 2019 15:33:23 +0000
Message-ID: <MN2PR11MB3565EE67426469E4B7460949D8660@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <MN2PR11MB35654E17AC76C7BB7DDD9096D8C60@MN2PR11MB3565.namprd11.prod.outlook.com> <OSAPR01MB2372DD841FEFA8B1F4884287E5C10@OSAPR01MB2372.jpnprd01.prod.outlook.com>
In-Reply-To: <OSAPR01MB2372DD841FEFA8B1F4884287E5C10@OSAPR01MB2372.jpnprd01.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pthubert@cisco.com;
x-originating-ip: [2001:420:44f3:1300:fc9e:730:2c16:4060]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0999b32d-8490-4b61-0cd0-08d75bbc58b6
x-ms-traffictypediagnostic: MN2PR11MB4366:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MN2PR11MB43660FE43490B3F1C2C011ACD8660@MN2PR11MB4366.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7219;
x-forefront-prvs: 0204F0BDE2
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(39860400002)(396003)(136003)(366004)(376002)(199004)(189003)(74316002)(486006)(236005)(229853002)(71190400001)(606006)(186003)(99286004)(6246003)(71200400001)(6916009)(8936002)(66946007)(66476007)(2906002)(66556008)(64756008)(66446008)(8676002)(55016002)(81166006)(81156014)(52536014)(9686003)(446003)(76116006)(476003)(6306002)(25786009)(14454004)(7736002)(6436002)(54896002)(11346002)(46003)(86362001)(7696005)(316002)(966005)(33656002)(53546011)(6506007)(5660300002)(76176011)(102836004)(790700001)(6116002)(6666004)(7116003)(256004)(3480700005)(478600001); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4366; H:MN2PR11MB3565.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: orNF5dAJMmcfnIH2TdKRnzD8sfK0ihuVq4/zFHJ9kdEUzBZhZMslGKtLkm7fZF3QorpzWR0NYQIqadwfymtg4sovJ44afFBp97EtvmQzUotCUDMn8aKPsv6wpaNeD+RkCQUlQl0gS4Ld2nKQIleUV+b7miRxPtxehjyFa9hD7LahxsIr/OUVtX891uvVy5CaZGkSaF4o+iKDlBtjAaICGg0R2Wk2fM0sxhggpmppwosmfVQiysxugImUIfVXR56IspB3bqLlCquyx/gBplYloMgV+1feWyDlxbQ1G/XfrUh3DUgve3qb7ra90mscqigatxQbrIaHfkwylB7wzUaRBxewxCQIjFvSX306FoFTk1mxR9LwMfOM+QQhTOjPXhzsIDRJv5g0pgR2Ny9bWhHPqDvDCrT6I8MmV9I0hpaGVjomS5lA4wSENkZxxi2lcrn2V1mQ8V8zALExccaGJhv4zraCizZJ1KJYzVD6no49dMQ=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB3565EE67426469E4B7460949D8660MN2PR11MB3565namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 0999b32d-8490-4b61-0cd0-08d75bbc58b6
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Oct 2019 15:34:39.5700 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 4giKRP0ezWz5jnoreACLmEMauNFUIaqhONbROHNtfexKfIGALeHhhwc56gyppZDaWeaKFXClkwtjwPRaG1XAwg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4366
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.22, xch-rcd-012.cisco.com
X-Outbound-Node: rcdn-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/ihdBkWa-fxk3dkZR4_sHT_59JHQ>
Subject: Re: [Roll] stitching PDAO segments
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Mon, 28 Oct 2019 15:34:45 -0000

Hello Toshio

You're correct: RPL carries the commands, but there's still a PCE.
My conclusion from this thread is that there's indeed a need to explain how PDAo segments are assembled into a Track as opposed to letting the reader guess...


All the best;

Pascal

From: Roll <roll-bounces@ietf.org> On Behalf Of toshio9.ito@toshiba.co.jp
Sent: jeudi 25 juillet 2019 04:09
To: roll@ietf.org
Subject: Re: [Roll] stitching PDAO segments

Hi Pascal,

I thought 6TiSCH Track forwarding is a completely different forwarding scheme
from RPL/IPv6 forwarding, as implied in https://tools.ietf.org/html/draft-ietf-6tisch-architecture-24#section-3.6

In that case, we don't have to relate DAO projection and Track, I think.
Or, maybe DAO projection is one implementation of Track forwarding, with RPL root playing
the role of PCE?


From: Roll <roll-bounces@ietf.org<mailto:roll-bounces@ietf.org>> On Behalf Of Pascal Thubert (pthubert)
Sent: Thursday, July 25, 2019 7:10 AM
To: Routing Over Low power and Lossy networks <roll@ietf.org<mailto:roll@ietf.org>>
Subject: [Roll] stitching PDAO segments

Dear all

Following up on stitching PDAO paths at the meeting today:

As you know, a 6TiSCH Track can be a lot more complex than a sequence of nodes (see https://tools.ietf.org/html/draft-ietf-6tisch-architecture-24#section-4.5.3)
It results that deploying a Track requires stitching segments into a DODAG from source to destination.
What makes the most sense for a 6TISCH Track is probably that each track is defined as a DODAG local instance for the source. All the PDAO segments would be stitched together into that DODAG to form a Track.
The current draft allows for this but a section that explains it all would certainly be useful.

Are we all OK that I propose some text about that?

All the best

Pascal

v2.23.0 | Report a Bug | By Email