IETF Logo Mail Archive

Re: [Roll] Querying PDAO

"Li Zhao (liz3)" <liz3@cisco.com> Thu, 25 July 2019 13:02 UTC

Return-Path: <liz3@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 05BC712021F for <roll@ietfa.amsl.com>; Thu, 25 Jul 2019 06:02:59 -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=Yu8c+mw5; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=S/qZQHAi
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 0QAY3PwObM9M for <roll@ietfa.amsl.com>; Thu, 25 Jul 2019 06:02:56 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EECB1200B5 for <roll@ietf.org>; Thu, 25 Jul 2019 06:02:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20867; q=dns/txt; s=iport; t=1564059776; x=1565269376; h=from:to:subject:date:message-id:mime-version; bh=t8jZAC0/ML8zIBbYBzj9MbQQF0Cj7bW8d41xFVyrMxM=; b=Yu8c+mw5DtxJBAPGouYynnNRCwLgZ1gI3ZP2sxqhIWUU9iNxq+yLaBG8 AVU4XLPfWuB0KTop/Aa61LOjPvQTJMKZp5ixh1kkjwa+6uyMplrxc7oZW iItingkqQNg/MP9ZSJX5gLhjjwIYLa3nuxoyuqQZFl6YeGPfPZobIGZmc Y=;
IronPort-PHdr: 9a23:gwpKZRV8yMJOMPveNLlzcZkMS+nV8LGuZFwc94YnhrRSc6+q45XlOgnF6O5wiEPSANiJ8OpK3uzRta2oGXcN55qMqjgjSNRNTFdEwd4TgxRmBceEDUPhK/u/ay0oR+xJVURu+DewNk0GUMs=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AHCABipzld/40NJK1cCh0BAQUBBwUBgWeBFS8kLANtVSAECyqEHYNHA4x9TIFqJX6RfYRXgUKBEANUCQEBAQwBAS0CAQGEQAIXgkcjOBMBAwEBBAEBAgEGbYUeDIVKAQECAxIRHQEBOBEBCBEDAQEBKwIEMB0KBBMigwABgR1NAx0BAqJRAoE4iGBxgTKCegEBBYJHgkMYghMJgTSLYIIWgREnDBOCFzU+hAwNBAszCYJrMoImgTIBiySCJoR/iG2NH20GAwKCGo1WhjobmAylDwIEAgQFAg4BAQWBZyGBWHBQKgFzgU6CQoNxilNygSmKYIJSAQE
X-IronPort-AV: E=Sophos;i="5.64,306,1559520000"; d="scan'208,217";a="384202103"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 25 Jul 2019 13:02:55 +0000
Received: from XCH-ALN-011.cisco.com (xch-aln-011.cisco.com [173.36.7.21]) by alln-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x6PD2tUG007626 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <roll@ietf.org>; Thu, 25 Jul 2019 13:02:55 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-011.cisco.com (173.36.7.21) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 25 Jul 2019 08:02:55 -0500
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 25 Jul 2019 09:02:54 -0400
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 25 Jul 2019 09:02:54 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=V1UZs8VrraOi93J0/4T/D5YekzxyXJMfCWFovl/25PsfvPE0NFwIfuePc82K4Amgei1PZzvVVJ7KN82SBTI9EWot8J95riF1vOUD5OXRAoYEmYJ/7ILjnrj57gnW2E4MGnddK99EThw/gN7g7tjAC6pyQDnJxBqGf5Zrx5GKgoJQOj3qASTCv71P7JBVZnZ74Wsn7vA3elzzu59Edd6PTEFfxoDarZYZ/lk1oF68BlovYMrB/nfrJ7fS334EXROPfGYBZy3lcFcMcw6ufX37G3+2G9FnOgDAhuF0wl2cj6U0UXfoq74ArF0EZFQZvmaoWcaWQmrruqsqlcZey8ZthA==
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=t8jZAC0/ML8zIBbYBzj9MbQQF0Cj7bW8d41xFVyrMxM=; b=INog10+lar51EnklwAhb4KwVSB3c7vUyMZKsYaJyBjCZ34YaywfHNogW6jMIAxFHNADmPHy4seKl4jPYV5xWUWs3QNOCa4Fmdmniqeqm46dQZAv/cEGomM7o0zk4J38JLpzqkYo/TEDTT0vXGrKbrdd3mJfNocMMehAWgrVWm52Jb+TVM62uv3olUUqkVtp55Wg2VKOwOssbc5I6PggKCGsdVLg0pQdW8uNy8aDjmJMf9xBdQuG8O7QFsQFIZWKu1DF6D/sjC/XEroGu+dDOLDDWTM+ImbMvVz08tSDZStJh8TxHpl0ndfX6TdC9c+uublPl1xgp0oEGH0uog1KXVg==
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=t8jZAC0/ML8zIBbYBzj9MbQQF0Cj7bW8d41xFVyrMxM=; b=S/qZQHAiyIwWA93NwKRdBx+e3a5bPseXCf4yRPWvje/mhqYevdLbVYVHew143+b0jGhbCZJbdRG3+PrL6T8JZ1g/zmJj2/5ovgyOSPIzkncVVXKRofPRe5rnbHZaoOfHKcrnQAOqyRRNsPCTLwaKyaS+sEtQo14fh2genHA+8ME=
Received: from MN2PR11MB3680.namprd11.prod.outlook.com (20.178.252.96) by MN2PR11MB4159.namprd11.prod.outlook.com (20.179.150.225) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2094.16; Thu, 25 Jul 2019 13:02:52 +0000
Received: from MN2PR11MB3680.namprd11.prod.outlook.com ([fe80::4815:c3d4:9fce:2d52]) by MN2PR11MB3680.namprd11.prod.outlook.com ([fe80::4815:c3d4:9fce:2d52%4]) with mapi id 15.20.2094.017; Thu, 25 Jul 2019 13:02:52 +0000
From: "Li Zhao (liz3)" <liz3@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] Querying PDAO
Thread-Index: AQHVQulDP49OaeTlkkaZr4JZQ61kVQ==
Date: Thu, 25 Jul 2019 13:02:52 +0000
Message-ID: <CEE1F9DD-4186-41CC-BC80-AFC616AC6187@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=liz3@cisco.com;
x-originating-ip: [2001:420:c0c8:1004::24]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: bd756850-4253-4b8f-6380-08d711006737
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB4159;
x-ms-traffictypediagnostic: MN2PR11MB4159:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MN2PR11MB4159B87D350701F6516896598CC10@MN2PR11MB4159.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0109D382B0
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(376002)(366004)(396003)(39860400002)(346002)(199004)(189003)(316002)(53936002)(8676002)(5660300002)(25786009)(54896002)(36756003)(76116006)(66556008)(7736002)(6116002)(66446008)(256004)(6512007)(86362001)(66946007)(66476007)(229853002)(6306002)(66574012)(91956017)(68736007)(6506007)(486006)(81156014)(81166006)(33656002)(2906002)(2616005)(8936002)(6916009)(46003)(476003)(478600001)(64756008)(102836004)(186003)(71200400001)(71190400001)(6486002)(53546011)(6436002)(14454004)(6246003)(99286004)(88722002)(24704002); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4159; H:MN2PR11MB3680.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-message-info: 3shD9vTO1oZoEHXvNqyq5oMm39MTAcoSydrEE0/Gq85/z8hcYIxI1fY9SmIBkoH/UP55mjoBe3rmzND3oVPa3P+K7oEbrrjVcI+aNILiByeg824DfDHw2bPY8aL5+wq0L/ygozZj618upaLKyFw56bwWni8/8quMbjsTm6XIkYGd9F9qj4PWTGjFMCIKRhn1A2OzUua17jlaq3A+jXtFF+WGWBSx02vW6LWvZsySS98rakNjg8cPcao3hcAtltfQ2TIGIrWlKkNZdmy5nbVlLFhGxbL9npTtJl+B3NXd9FBPQOojGE6b93lvWHITSB/HOAW3RLRr6XGjWXGHlFs3zooptOYWEJ9hD//gzhwUhl+sZFYQfCx2QHrwuQTo/5HzgfqmxfaBvMVRtj7LhcN33HeE/1iFEjERZcmm9fRtWhs=
Content-Type: multipart/alternative; boundary="_000_CEE1F9DD418641CCBC80AFC616AC6187ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: bd756850-4253-4b8f-6380-08d711006737
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Jul 2019 13:02:52.3820 (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: liz3@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4159
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.21, xch-aln-011.cisco.com
X-Outbound-Node: alln-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/t62rC0RYGJmZft8Z58lky9JS_jk>
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 13:03:03 -0000

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> on behalf of "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
Date: Thursday, July 25, 2019 at 7:53 AM
To: Routing Over Low power and Lossy networks <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> On Behalf Of Li Zhao (liz3)
Sent: mercredi 24 juillet 2019 16:42
To: Routing Over Low power and Lossy networks <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.28.0 | Report a Bug | By Email | System Status