Re: [Roll] Sibling information
"Pascal Thubert (pthubert)" <pthubert@cisco.com> Thu, 25 July 2019 02:40 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 068991200DB for <roll@ietfa.amsl.com>; Wed, 24 Jul 2019 19:40:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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, URIBL_BLOCKED=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=N6Id6Ldg; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=QrLtscGx
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 jSmgSSrcSags for <roll@ietfa.amsl.com>; Wed, 24 Jul 2019 19:40:11 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA7F7120090 for <roll@ietf.org>; Wed, 24 Jul 2019 19:40:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9669; q=dns/txt; s=iport; t=1564022410; x=1565232010; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=Bw6zWu7LsgDVN8cIZnWZ2mzgDWkyMK2KtIsvA0LlrOU=; b=N6Id6Ldgi0CI5hjmajPRhEKm0hjuuUbKLLB0q7efRfYveS6ODQpDneOt eZefnalfz/0hbVJGpBxVsDBsNJAVDyLb4O4iMTV9Tta24pBtQoEe+7ufl 9Wj4SFjrKy7L5VFfA8Btr/n73b/K3UmYLkSfSz/zWo7LZ7ma/FvWBEQEl 8=;
IronPort-PHdr: 9a23:0qbK1RLe40VfafdBTtmcpTVXNCE6p7X5OBIU4ZM7irVIN76u5InmIFeBvKd2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUgMdz8AfngguGsmAXFXnLOPgYjYmNM9DT1RiuXq8NBsdFQ==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AYAABGFjld/5RdJa1mGwEBAQEDAQEBBwMBAQGBUwYBAQELAYEULyQsA21VIAQLKgqEE4NHA4RSiCpMgg+Se4RVgS4UgRADVAkBAQEMAQEYAQoKAgEBhEACF4JCIzQJDgEDAQEEAQECAQZthR4MhUoBAQEBAwEBEBEKEwEBLAwPAgEIEQQBASgDAgICJQsUCQgBAQQTIoMAAYEdTQMdAQIMoUkCgTiIYHGBMoJ5AQEFgkeCRBiCEwMGgTQBhHKGbReBQD+BECgfUYF7PoJhAQGBKRxCBwmCVTKCJoxXgiWEf5Z0CQKCGYgbhTuGOhuCLZVdpQsCBAIEBQIOAQEFgVA4gVhwFTsqAYJBgkKDcYUUhT9ygSmLLAGBIAEB
X-IronPort-AV: E=Sophos;i="5.64,305,1559520000"; d="scan'208,217";a="598885791"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 25 Jul 2019 02:40:01 +0000
Received: from XCH-ALN-016.cisco.com (xch-aln-016.cisco.com [173.36.7.26]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id x6P2e1Bu026644 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <roll@ietf.org>; Thu, 25 Jul 2019 02:40:01 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-ALN-016.cisco.com (173.36.7.26) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 24 Jul 2019 21:40:00 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 24 Jul 2019 21:39:59 -0500
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 24 Jul 2019 21:39:59 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Jz+I1fJ8cC5mMOSY67w1Q7G+r9dTT73F2slz1g7IZuIRBowekiza1oAysQMgziTY09KHtyfCPDl6Gbx5giiCVezHdeTccvrVvRn9816AjLHrlIyuUgXXhb8Nj0LTK3bdY5ChEvQ+7J0LFFy9upk3zrjYZwl1XNuNIrm+kYJcR3bmHgpcQBAyw+JV+EdzRkf7UYOhPgJZu1T5yiyg3jOMys7fGyNmskxnAwAdTm7r/1hGArVU9lXuZbtyDO4QYv2Op/uMA1mrXWIu4WxTPSevFPOh1+c6BawTPZnk5YNB8Ox+Wu933m8SphVDWGy6n93vsAklc7akKD0FcZGjHJNtuQ==
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=Bw6zWu7LsgDVN8cIZnWZ2mzgDWkyMK2KtIsvA0LlrOU=; b=dBn1hIF2fnDfOExSzWYFUEiKqhpRewNpUwBqPvnM656WAg+ocCNJBqK0B2kXqYaY65DYhY8xKdhRM4wZynwXVustNbqsdmnTJdY2+vhz0f36/pntQseJcuQRbLt+cufgSsgMGch2MJxDnmdwjOhRdYsLnN+S6l8ilwxSm4ztVaqQQXCmqEHtTs3cKamZh8HwC8Kt6Ut3U9h7QSAWN4gWC0h3mdxjY0EGQasRbjPk3UkP8Y/x5aPzEU3s1jjCgiLgXxb/nl+MfaDeINR2aC8SnIcyeQnoxShwpmUk5loPLK0YXWHML6VLwJCeuQVZYPN/QeK29H1N9nx7s2gOmAcnww==
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=Bw6zWu7LsgDVN8cIZnWZ2mzgDWkyMK2KtIsvA0LlrOU=; b=QrLtscGxqM9lKf5vnVM9Nr+FoOe7l4LjCVmyBOKqWWbSBGq/6uzTdcNSptxPsK/KJTL00tY1Wrxnb1Q/kej+pH5SxgsjquAx+WZjVgZXGQJdAkQ7ir1A8ROGX2oq1whRC61mxPgkQkUssfzyilzeBFUjhR0f07kn3+GO2OnsSE4=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB3696.namprd11.prod.outlook.com (20.178.253.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2115.13; Thu, 25 Jul 2019 02:39:58 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::1ce9:1582:146c:c50a]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::1ce9:1582:146c:c50a%6]) with mapi id 15.20.2094.013; Thu, 25 Jul 2019 02:39:58 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] Sibling information
Thread-Index: AdVCbFxjQmGr9n08QiSNVldJ8OXwSAAEwVbwAAS3lUY=
Date: Thu, 25 Jul 2019 02:39:58 +0000
Message-ID: <4A2E16A7-D161-421E-B930-98D0F2D04990@cisco.com>
References: <MN2PR11MB35651875289F99DDB70BEB93D8C60@MN2PR11MB3565.namprd11.prod.outlook.com>, <982B626E107E334DBE601D979F31785C5DF5BC96@BLREML503-MBX.china.huawei.com>
In-Reply-To: <982B626E107E334DBE601D979F31785C5DF5BC96@BLREML503-MBX.china.huawei.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pthubert@cisco.com;
x-originating-ip: [207.115.96.130]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7a701a1e-aeaa-4d44-de6d-08d710a962a9
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB3696;
x-ms-traffictypediagnostic: MN2PR11MB3696:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <MN2PR11MB3696C485EF0858E2F3A8571AD8C10@MN2PR11MB3696.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0109D382B0
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(396003)(346002)(136003)(366004)(39860400002)(189003)(199004)(33656002)(2906002)(5660300002)(6916009)(229853002)(66066001)(36756003)(26005)(236005)(102836004)(6512007)(99286004)(68736007)(54896002)(6306002)(86362001)(256004)(76176011)(53936002)(478600001)(8936002)(6506007)(11346002)(25786009)(8676002)(966005)(53546011)(6486002)(446003)(2616005)(66946007)(81156014)(81166006)(66446008)(76116006)(91956017)(486006)(6436002)(7736002)(64756008)(66476007)(316002)(186003)(71200400001)(71190400001)(66556008)(476003)(6246003)(6116002)(790700001)(606006)(3846002)(14454004)(244885003); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3696; H:MN2PR11MB3565.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 7ptgz8m5Q9h0NEm+npSzgNN9cqi2L6zNY97UiL+r7l7NFu2qov5u0gXH2IXBFZukMOOrkotk6WVfvvrkNPUwHTvlgfZ3tSXTuumNiNY/H733NBDgGK7LCETaNZA8AJS4WokuipFO98HApSyZue/VQffU6D8o4OSHtHVEq/teQAmLprZXukfOYImz/pJY62cPVIREqdb9pCFLvdUin6lyiql/Gf0BdFVazOcYj2RzJNA5FB0wlDrjdhV0wvuNGem9mPKR/4qDRrkvIXXDX/2ERdubnotlljVXp7SVyh07NrcxkWCtx9pAyu9BNLY85+98AXaVh5Rnyxdzn9B+buo99R/dS8Yz8BsTTj4uLTvFOlNZWg2zfX00xt4DfqKLo/6iUQisqDChujKb0UOcE1lNp3odiVHT1SJAfrLUTlfJCE8=
Content-Type: multipart/alternative; boundary="_000_4A2E16A7D161421EB93098D0F2D04990ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 7a701a1e-aeaa-4d44-de6d-08d710a962a9
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Jul 2019 02:39:58.4942 (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: pthubert@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3696
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.26, xch-aln-016.cisco.com
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/2E6vHCcIlIYyvhbQyTqDcBU1xiA>
Subject: Re: [Roll] Sibling information
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: Thu, 25 Jul 2019 02:40:13 -0000
Hello Rahul Siblings are peers at a Rank similar to this node. RPL will not tell the root about them. We want to give similar information about parents and siblings but we do not want the root to use siblings for source routing. So a sibling information option would be just like a transit but not for use as a parent in normal RPL and then the metrics could be added for both kinds. Regards, Pascal Le 24 juil. 2019 à 20:34, Rahul Arvind Jadhav <rahul.jadhav@huawei.com<mailto:rahul.jadhav@huawei.com>> a écrit : Hi Pascal, Isn’t it already possible to send multiple Transit Information Option in DAO in non-storing MOP for a node to inform root of node’s multiple parents? I understand you mentioned sibling information but I am wondering how root makes use of sibling information to optimize P-DAO. I can clearly relate how root can use multiple parent’s info to optimize P-DAO but not sure how sibling info will help. Regards, Rahul From: Roll [mailto:roll-bounces@ietf.org] On Behalf Of Pascal Thubert (pthubert) Sent: 25 July 2019 06:12 To: Routing Over Low power and Lossy networks <roll@ietf.org<mailto:roll@ietf.org>> Subject: [Roll] Sibling information Dear all Following up on the WG meeting today: It makes sense to make the draft complete by adding a sibling information in the Non storing mode DAO to the root. This was the root can compute more optimized P DAO. Are we OK that I include some text and a proposed format about that in the next revision? All the best Pascal _______________________________________________ Roll mailing list Roll@ietf.org<mailto:Roll@ietf.org> https://www.ietf.org/mailman/listinfo/roll
- [Roll] Sibling information Pascal Thubert (pthubert)
- Re: [Roll] Sibling information Rahul Arvind Jadhav
- Re: [Roll] Sibling information toshio9.ito
- Re: [Roll] Sibling information Pascal Thubert (pthubert)