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 84CDA12015F for <roll@ietfa.amsl.com>; Thu, 25 Jul 2019 06:02:55 -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, 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=IWO4w7WS; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=OvzXf/gD
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 0es13_PQHs_a for <roll@ietfa.amsl.com>; Thu, 25 Jul 2019 06:02:53 -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 3AE101200B5 for <roll@ietf.org>; Thu, 25 Jul 2019 06:02:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1816; q=dns/txt; s=iport; t=1564059773; x=1565269373; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=lX95R2jvSOBAK42hnZxZ1MMtzqKSlmorpiBX1lRSG5E=; b=IWO4w7WSwCzmgyxb9zgvBs5CgBw4a2LRzZaCz9Sev1vgKY8WY925WHqZ 9b2Y2aQQWeAl5MrCobIS5EAdV2N/t1uP13EDTVeILapvAKp8YBjiYwZ/0 Z+Scxi6EJxwnXIqrv6tunhxF3kupR3JKicAvcgF1trBVBvigu632WyHNp k=;
IronPort-PHdr: 9a23:V74h6xVjRbBB3X2YKheReIhFjFLV8LGuZFwc94YnhrRSc6+q45XlOgnF6O5wiEPSANiJ8OpK3uzRta2oGXcN55qMqjgjSNRNTFdEwd4TgxRmBceEDUPhK/u/ay0oR+xJVURu+DewNk0GUMs=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AUAQBipzld/4QNJK1mHQEBBQEHBQGBVAcBCwGBQ1ADbVUgBAsqhB2DRwOMfUyCD5dSgS6BJANUCQEBAQwBAR8OAgEBgUuCdQIXgkcjNQgOAQMBAQQBAQIBBm2FHgyFSgEBAQECARIREQwBATgPAgEIGAICJgICAjAVEAIEEyKDAAGBagMODwEColECgTiIYHGBMoJ6AQEFgkeCQxiCEwmBDCgBi1+CFoERJx+CTD6EW4J0MoImgTIBiySCJpsLbQYDAoIalBAbmAylDwIEAgQFAg4BAQWBUQE2gVhwegFzgU4JgjmDHVSKU3KBKY0yAQE
X-IronPort-AV: E=Sophos;i="5.64,306,1559520000"; d="scan'208";a="384202001"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 25 Jul 2019 13:02:50 +0000
Received: from XCH-RCD-012.cisco.com (xch-rcd-012.cisco.com [173.37.102.22]) by alln-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id x6PD2ofO019504 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <roll@ietf.org>; Thu, 25 Jul 2019 13:02:50 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-RCD-012.cisco.com (173.37.102.22) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 25 Jul 2019 08:02:50 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 25 Jul 2019 08:02:49 -0500
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 25 Jul 2019 09:02:49 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZJZ3MvvYsQMk52LcGJw26JRcPpcqX0qDjnFcm83Pej69Y1TeyJHVZYEU+4xMMO/3TZ6CIN2XkFiQXcHbX1iCMXkrPejC8CpXeMrGDOe3JlHXaL7yh29Y3xRmvgeEToNdlz+kkFSEXTYjosTn7+lN+ChiM7YDCJF+0yVQ9BzJOLUrMZlDjvRRqqsAug85vd7NFZI5JN+3oC8EET18jqrCMqxwy0dd3TReLdVedoiWoG67BZIzWkDM8zGW2xxprMLa5vHfqhNlvOAWZ19RILzFb92nxDMD/egEaG31o42OqiyuMzRBQehoJ6/C7ffP716D/Q6AXmG+4HGW2xMeWN5Oog==
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=lX95R2jvSOBAK42hnZxZ1MMtzqKSlmorpiBX1lRSG5E=; b=G4vqgz4UWZ4GyTrghU4qDsXixL/WKB75U8VwxMRGeoOey16mrfW62YY8lrNKooPZWiVot0R1Nti1lpxbV9uDvmzoTb4irTdESGKKq2zFlMhguS6+k0g1ldozLceL3lzMFcKNmE/uurfOM7IMdoFnTQCoJgm5e5Bil1q1ZTq/PpWUGSzHwsb2zGxIun/vX5+HKojR+AVvBBqaQaFRcXZv8AUXlHv5/6NtBtzJ1NIkYi6+Lf0hxdWZtmvKcH3sz0T4JICBi8RAYA67cyo63mm06szzqP3JFRObLQkvdjwscDWYKnq7DAH+IVcI7KYdZFdjYRSwmR1+9iHVE4je8MYJjQ==
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=lX95R2jvSOBAK42hnZxZ1MMtzqKSlmorpiBX1lRSG5E=; b=OvzXf/gDHLxeENQK2thCUah/TQ4JHZWWFXrfT+6EmCONCI6ofiEYsBZal4eEp//BCsUGoh27A9S0CUYpYiswH6YtLRgWcgCt3oTfp/vZNmV7nVJlZGNnU0cAr1c5Opr6D6wJNy3CkMQFIzhWxrLU8P7Bn4OOmWhG4S1nYY08nTk=
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:47 +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:47 +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: AQHVQnldZPEd7kPI0E21cQA8lnfMNqbaeS+AgAFae4A=
Date: Thu, 25 Jul 2019 13:02:46 +0000
Message-ID: <B7E354EC-2B84-4AC0-AD15-F915B581EFA3@cisco.com>
References: <77E0C031-82C2-422A-9333-6F7B02C4B3C4@cisco.com> <10416.1564014159@dooku.sandelman.ca>
In-Reply-To: <10416.1564014159@dooku.sandelman.ca>
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: fa14f8b6-ce05-4bed-8191-08d7110063ee
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: 1
x-microsoft-antispam-prvs: <MN2PR11MB4159CE8EAE8431250CF863ED8CC10@MN2PR11MB4159.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7219;
x-forefront-prvs: 0109D382B0
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(376002)(366004)(396003)(39860400002)(346002)(199004)(189003)(966005)(316002)(53936002)(8676002)(5660300002)(25786009)(36756003)(76116006)(66556008)(7736002)(6116002)(66446008)(256004)(6512007)(305945005)(86362001)(66946007)(66476007)(229853002)(6306002)(91956017)(68736007)(6506007)(486006)(81156014)(81166006)(33656002)(2906002)(2616005)(8936002)(76176011)(6916009)(46003)(476003)(478600001)(64756008)(102836004)(186003)(71200400001)(71190400001)(6486002)(6436002)(446003)(14454004)(6246003)(99286004)(11346002)(88722002); 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: hsmmo7qk5r9z9jXSJx+d/oFTLZS+4bfp0E4x39OuoeIryJUfifhTnuXAepOE0kKw/RkBqCyECuu6/YkoX2Mzx8d4MptrJB8ugheFr3L7x9rzqIfysrGbB3Ejmy+vXnJgRczNCQz7RIoFd69c2J3bS3bGDTqLn8IKW9vTvmh5+aZ7ImB7uL3nOpO1Xn0Xqr23wKb2wh6iVV2FF8jCIUpW7xIWjupPjEzyi04hM2G1js0eadiEr9UXtu3hQfs4xl9FSYN5yfdT/kmRgKg85/RnBTzw3dM/4bnaMbsho8x6y2mP9XrPl6vGcsD/p2FqT0bSF8dUTfbs8gFbuO77s3roG5WW72+yETwwv/xQhABv3Dzy8H2dhA1G6h1CkCsz3U3o3TFVLv4Ta5/yDDhVc68xNKUYp1XJiSQtBprJjhHs8Rs=
Content-Type: text/plain; charset="utf-8"
Content-ID: <E63D0FFFA4A5B243B61EA6A27B257C95@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: fa14f8b6-ce05-4bed-8191-08d7110063ee
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Jul 2019 13:02:46.8193 (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.37.102.22, xch-rcd-012.cisco.com
X-Outbound-Node: alln-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/Nuie1_REYL0F6jKBzb1Z9rCdJOc>
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:02:56 -0000

Correct. If the application on node X wants to ask a nearest path to node Y, PDAO draft doesn't provide any mechanism.
I think PDAO draft need to cover this case. Maybe how and when to use PDAO is out of scope of this draft.
But at least we need to reserve the asking capability and define the protocol.


Best regards,
Li
 


On 2019/7/25, 8:22 AM, "Roll on behalf of Michael Richardson" <roll-bounces@ietf.org on behalf of mcr+ietf@sandelman.ca> wrote:

    
    Li Zhao (liz3) <liz3@cisco.com> wrote:
        > 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.
    
    So, if I understand, you are asking that a given node X, having traffic to
    node Y, should be able to ask the root to project a DAO towards Y?
    
    -- 
    ]               Never tell me the odds!                 | ipv6 mesh networks [ 
    ]   Michael Richardson, Sandelman Software Works        | network architect  [ 
    ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.28.0 | Report a Bug | By Email | System Status