IETF Logo Mail Archive

Re: [Roll] Querying PDAO

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 25 July 2019 15:37 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 8816312026E for <roll@ietfa.amsl.com>; Thu, 25 Jul 2019 08:37:14 -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 noUS4YTQBPB2 for <roll@ietfa.amsl.com>; Thu, 25 Jul 2019 08:37:11 -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 C2EE51201DA for <roll@ietf.org>; Thu, 25 Jul 2019 08:37:11 -0700 (PDT)
Received: from dooku.sandelman.ca (dhcp-9d9a.meeting.ietf.org [31.133.157.154]) by relay.sandelman.ca (Postfix) with ESMTPS id 361A31F44B for <roll@ietf.org>; Thu, 25 Jul 2019 15:37:10 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id B61291D76; Thu, 25 Jul 2019 11:37:32 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
In-reply-to: <B7E354EC-2B84-4AC0-AD15-F915B581EFA3@cisco.com>
References: <77E0C031-82C2-422A-9333-6F7B02C4B3C4@cisco.com> <10416.1564014159@dooku.sandelman.ca> <B7E354EC-2B84-4AC0-AD15-F915B581EFA3@cisco.com>
Comments: In-reply-to "Li Zhao (liz3)" <liz3@cisco.com> message dated "Thu, 25 Jul 2019 13:02:46 -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: Thu, 25 Jul 2019 11:37:32 -0400
Message-ID: <18422.1564069052@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/Pu7RmPuxzqq7TabLq8fCv7YQUvk>
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 15:37:15 -0000

Li Zhao (liz3) <liz3@cisco.com> wrote:
    > Correct. If the application on node X wants to ask a nearest path to
    > node Y, PDAO draft doesn't provide any mechanism.

P2PRPL tries to do this, but you are suggesting that instead of learing it,
the root should just know it.  This goes to some of the PCE cases, I think.

Is there PCE technology we can use?

DAO-projection does not create a route that is remembered, rather it prefixes
it to a particular packet.  So you'd want node X to be able to ask the root
for such a source route?

    > 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.
-- 
]               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.23.0 | Report a Bug | By Email