IETF Logo Mail Archive

Re: [Roll] Querying PDAO

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Thu, 25 July 2019 16:58 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 900041200CE for <roll@ietfa.amsl.com>; Thu, 25 Jul 2019 09:58:03 -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=ffxlj3x2; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=TXbskth4
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 9VVba01P95vy for <roll@ietfa.amsl.com>; Thu, 25 Jul 2019 09:58:00 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17302120105 for <roll@ietf.org>; Thu, 25 Jul 2019 09:57:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=24354; q=dns/txt; s=iport; t=1564073873; x=1565283473; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=gFlHTTVHhh6qAesU75LxbRVObRA2w+J57AA3JpcRq2Y=; b=ffxlj3x23MS9UnRIOlLV/OOd50dvY+O4xT6Mn19/JrF/U7oij7/+SKis H2MxqXoWs1DIKJJq6OXF5wTJe9aWPoURlte5YoqmjDs4x8y5WrKg8ru4H /HoAJXBdVN9o8n0ccJgIc5fhwravMVmhFr6pLFRmj+GIa47zjEk2gAWjR 8=;
IronPort-PHdr: 9a23:P7mbKRZ6d9FeufMpcSm0RAb/LSx94ef9IxIV55w7irlHbqWk+dH4MVfC4el20gabRp3VvvRDjeee87vtX2AN+96giDgDa9QNMn1NksAKh0olCc+BB1f8KavycywnFslYSHdu/mqwNg5eH8OtL1A=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C+AAB/3jld/5FdJa1cChwBAQEEAQEHBAEBgVUFAQELAYEULyQsA21VIAQLKoQdg0cDjH5Mgg9+llSBLhSBEANUCQEBAQwBAS0CAQGEQAIXgkcjNgcOAQMBAQQBAQIBBm2FHgyFSgEBAQEDEhEKEwEBOA8CAQgRAwEBASgDAgICMBQJCAIEEwgagwGBHU0DHQECoksCgTiIYHGBMoJ6AQEFhQsYghMJgTQBi14XgUA/gRFGghc1PoQMDQQLHhUJFoJVMoImjFeCJoR/iG2NH20JAoIajVaGVZgMpQ8CBAIEBQIOAQEFgVcJKIFYcBU7gmyCQoNxilNygSmKWYJSAQE
X-IronPort-AV: E=Sophos;i="5.64,307,1559520000"; d="scan'208,217";a="591992231"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 25 Jul 2019 16:57:52 +0000
Received: from XCH-RCD-018.cisco.com (xch-rcd-018.cisco.com [173.37.102.28]) by rcdn-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id x6PGvpUZ010592 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <roll@ietf.org>; Thu, 25 Jul 2019 16:57:52 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-RCD-018.cisco.com (173.37.102.28) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 25 Jul 2019 11:57:51 -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; Thu, 25 Jul 2019 11:57:50 -0500
Received: from NAM01-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; Thu, 25 Jul 2019 11:57:50 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=lAgQnbr/SHGHzSIKVnRTC7WsBFebTklsPg7pgqtoJlIxgxp2+ESaDlM8UHGnjlT6o+kS8Ads3TS9fiSGHL4jlsXItY11IwqiG1eiCZuiectBIsrTZTDYqgQhvzeiL/VRSSOodFvCKsaILU+jLbFOUU1odFBhUPGxiKAgDDzzGMD35aKZFVxwPvwoLsM1tbekgwhr74v5ghJ2U5j41YbjC7efsWUfyGXaeBgYZi7FaCXzcEvGtVPpqmDw9twrr/1w2srmstyNsJ7yxRVI5FNWSEodu883+fdc1vZDqz/VAHeutyOfvA8BJly4ihJuprlrtN1nUqCMuPVgCqfX82aKaA==
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=gFlHTTVHhh6qAesU75LxbRVObRA2w+J57AA3JpcRq2Y=; b=MEJo0pS5ojQxDKn2+7CsracV8UsK06/VLL0A24nmBZ/MSpHHtPEId6/boXNhSl1xAHWkmonOHPccwzrlOS8YJ8xIY4fRe839qLzejPejXxXR8gZXKhzC9EBwf+5EwhQ29CQ7TPpBpv464UaceD+ku5YaZHFv0s5IA4+FzLZl8s/wLnTJoVA6dnKsgnKfI8jeR8h6Sgbmu5fhKnh6kDKKn+fqIGMJuSJ0uh2Y5W1o0VVCfj/UdWTbAYSgrHDs56T/7jRrRsszKYmRKDhiAihZASWMss9zyO4Y8FLXEZ4YxY+sogbIgazk7shBezivJKJ5XWs4Cd6xbzTMVKOJn55Zyg==
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=gFlHTTVHhh6qAesU75LxbRVObRA2w+J57AA3JpcRq2Y=; b=TXbskth4nLs1BaNz84LNVHoOG1+LFMDrSAlu/5OzPMuOvA/CvTfbRo7wBPEbcNaWrUc1v7NKdAzGi+q0Tg5G6uTWgC3z7fwO+Nl9m06K6LskFHU/GAyYz4UP3gGQjgd7BBOlg06unciQ+SmtfVkK683ywKHGrveD02UWlMVYGSU=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB3597.namprd11.prod.outlook.com (20.178.251.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2115.10; Thu, 25 Jul 2019 16:57:49 +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 16:57:49 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] Querying PDAO
Thread-Index: AQHVQulDP49OaeTlkkaZr4JZQ61kVabbjW+A
Date: Thu, 25 Jul 2019 16:57:34 +0000
Deferred-Delivery: Thu, 25 Jul 2019 16:57:30 +0000
Message-ID: <MN2PR11MB35656240F3D6B6F3B5E17B85D8C10@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <CEE1F9DD-4186-41CC-BC80-AFC616AC6187@cisco.com>
In-Reply-To: <CEE1F9DD-4186-41CC-BC80-AFC616AC6187@cisco.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:c0c0:1008::235]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3ab3b558-b1d0-4e4a-13e4-08d7112139c1
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB3597;
x-ms-traffictypediagnostic: MN2PR11MB3597:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MN2PR11MB35970B816F4A71BDE0392A71D8C10@MN2PR11MB3597.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0109D382B0
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(136003)(39860400002)(396003)(376002)(346002)(189003)(199004)(74316002)(66574012)(11346002)(486006)(71190400001)(71200400001)(478600001)(68736007)(52536014)(476003)(25786009)(5660300002)(446003)(46003)(229853002)(6666004)(55016002)(14454004)(2906002)(33656002)(8676002)(186003)(6306002)(54896002)(8936002)(6246003)(76176011)(316002)(9686003)(102836004)(6916009)(236005)(76116006)(99286004)(790700001)(6116002)(66946007)(81156014)(81166006)(66446008)(256004)(64756008)(66476007)(6436002)(86362001)(53546011)(53936002)(6506007)(7696005)(7736002)(66556008)(24704002); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3597; 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: xeusZWYuZfU2pUqiTctwN4ODhLKQFePm8jfF4m37j4xc81qI0O1qV5vjPxDiLvvIfEIpmnDd4HA+t3GvgWJEKtx363KGwhCwOa6tK7qWEyrrTuKpHou0IlNLnTheN4uAfRFi3tS6XxeuZ7aC+8BdXkdBwc+D5QOWpDafV0lEgFnkE6N6WW00TGwFBdi/k0TvZU93mvD6o0KcMAhbkHl8OUJIjM+W03XsZZOuFfGnocJ21VRILfYk+mXyHberpdFw9orYtfulL1VKMHUwHDV+tSniR77OdDI/uhh2lJQ2qcTYLzoUFASzJ8ocPQ/MHtVb5HHj7dRZEIxgJ+5OaK3uAosvxAqLR3HZEixv7Tax0vJ91zOMtCThPyIrEhGAsoPjnX0zgT/uieAT6zNNzXb0ybsyOM7/p7dhtl1jmXVzQgk=
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB35656240F3D6B6F3B5E17B85D8C10MN2PR11MB3565namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 3ab3b558-b1d0-4e4a-13e4-08d7112139c1
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Jul 2019 16:57:49.4943 (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: MN2PR11MB3597
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.28, xch-rcd-018.cisco.com
X-Outbound-Node: rcdn-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/H8qrJy2oBOQgJSw9kQvn-I4MlB8>
Subject: Re: [Roll] Querying PDAO
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 16:58:04 -0000

I see, Li. Let’s see if others object or wish to add stuff?

All the best,

Pascal

From: Roll <roll-bounces@ietf.org> On Behalf Of Li Zhao (liz3)
Sent: jeudi 25 juillet 2019 09:03
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Subject: Re: [Roll] Querying PDAO

Yes. Use target as a prefix is to reserve the capability of creating a path to a subnet. Maybe we can use another way to keep the capability.

Suboption for route parameter is a good idea. We can define some TLV to identify these parameters.


Best regards,
Li


From: Roll <roll-bounces@ietf.org<mailto:roll-bounces@ietf.org>> on behalf of "Pascal Thubert (pthubert)" <pthubert@cisco.com<mailto:pthubert@cisco.com>>
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org<mailto:roll@ietf.org>>
Date: Thursday, July 25, 2019 at 7:53 AM
To: Routing Over Low power and Lossy networks <roll@ietf.org<mailto:roll@ietf.org>>
Subject: Re: [Roll] Querying PDAO

Looks good Li.

I’m confused that you see the target as a prefix; would you like to create a path to the nearest router that serves a subnet?
I guess that the route parameters should be a place for suboptions.
Suboptions I can fathom would be a max sum of steps of Rank, a max latency, and a reliability level. Should be extensible though.
Which means that the sibling and transit information in the DAO should provide enough metrics to build this.

Assessing the list here, do we have a consensus to add a PDAO query DIS to the PDAO draft?

All the best,

Pascal

From: Roll <roll-bounces@ietf.org<mailto:roll-bounces@ietf.org>> On Behalf Of Li Zhao (liz3)
Sent: mercredi 24 juillet 2019 16:42
To: Routing Over Low power and Lossy networks <roll@ietf.org<mailto:roll@ietf.org>>
Subject: [Roll] Querying PDAO

Dear all,

Following up on querying PDAO from root at the meeting today:

It makes sense to provide a querying mechanism for node which can get PDAO from root. Then node can query special PDAO route entry according to its special requirement. For example, route hop, latency, route algorithm, remaining lifetime.

We can enhance DIS to query PDAO if adding a flag in DIO Base Object to identify it is a PDAO query DIS.
And this DIS need to carry a new Control Message Options because existing Control Message can’t identify the requirement.
A possible Control message is as following:


        0                   1                   2                   3

        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

       |   Type = TBD | Option Length | Prefix Length | alg    | Resvd |

       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

       |                                                               |

       .                   Target Prefix (Variable Length)             .

       .                                                               .

       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

       |                        route parameter                        |

       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+



alg: route algorithm such as latency/hop limited/common ancestor.
hops/latency/remaining lifetime are some route parameter.

Is it possible to add some text about it?


Best regards,
Li

v2.23.0 | Report a Bug | By Email