IETF Logo Mail Archive

Re: [Roll] Querying PDAO

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 25 July 2019 00:22 UTC

Return-Path: <mcr@sandelman.ca>
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 301461202B9 for <roll@ietfa.amsl.com>; Wed, 24 Jul 2019 17:22:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 mIfEdthg5dQe for <roll@ietfa.amsl.com>; Wed, 24 Jul 2019 17:22:18 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 239CC12025D for <roll@ietf.org>; Wed, 24 Jul 2019 17:22:18 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:67c:370:128:6e88:14ff:fe34:93bc]) by relay.sandelman.ca (Postfix) with ESMTPS id E94961F44B for <roll@ietf.org>; Thu, 25 Jul 2019 00:22:16 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 5D2381B00; Wed, 24 Jul 2019 20:22:39 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
In-reply-to: <77E0C031-82C2-422A-9333-6F7B02C4B3C4@cisco.com>
References: <77E0C031-82C2-422A-9333-6F7B02C4B3C4@cisco.com>
Comments: In-reply-to "Li Zhao (liz3)" <liz3@cisco.com> message dated "Wed, 24 Jul 2019 23:41:49 -0000."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Wed, 24 Jul 2019 20:22:39 -0400
Message-ID: <10416.1564014159@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/cLefTrQTCrp1ixoxthhe8WYYe44>
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 00:22:20 -0000

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