Return-Path: 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 B4EE71202B8 for ; Thu, 25 Jul 2019 23:41:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 27aS3jdAEKQi for ; Thu, 25 Jul 2019 23:41:33 -0700 (PDT) Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 054B21202AA for ; Thu, 25 Jul 2019 23:41:33 -0700 (PDT) Received: by mail-ed1-x52d.google.com with SMTP id p15so52268461eds.8 for ; Thu, 25 Jul 2019 23:41:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=685buZJv73Wq7vHhIC3E+rUKKDLjRriWCOz7PvYTH50=; b=ey2+2QgvS2LDZQSjRsXu3lxMLZkBz7c6NYFBJHfJT9V3vB0UXDObjS1Fkr5wiCfpz6 0hlVOJTKYS+NhrnjCU1eyjsrEqIanS2K8yO+zl0ppDBwdGddlBAaZlDXi3U7Z1LzSs5n 01ROAdWOyWhqWi9A6i8jvo63G1eXkBEgCUzQ4kTWrAyGP246I26AUjj45nbNUKjCrZtS TF7eyC5riDQc61ZwDOmGJbt5V4GrMCjF1uIpjwxWYB3GuCoCOslcqXFVKtwEJRXDNi6N IA/UGLIlpMHkz2wf5lMM+O8W2J7pJkEFMRbXtE9O2mgLlILExs3jyTd461lAXRTWIWZR iOgQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=685buZJv73Wq7vHhIC3E+rUKKDLjRriWCOz7PvYTH50=; b=TxInq2M3DHCE+BBcTaMIj3GK1Thg6KXuEeEbYYPOSwCtPpZEOYu/0jd7TG3WEx71XZ twjBmeYlJF5+EudGUPYZqYtPknveI1OnMavH13oBv05iaMs0+whnJwjJZ0yZ7j1qnxDf LzGZgzNwNi+oKn4cgJBgQoNEsCFHJvtK2I5XGCcITvWlwVcd9yNW8YwZxq7RCNB3u96z PNUP4nV7UZqrjd3P+XwLt4RjxJMLNuTrngb/Bheincpv8/N2R0qGDuZt60t0+zqWmp1E KmOeuoQi0FA988JJOWznLCQRlvuge6rr7cJg2scR5xjlC+2xv2BWdJnShzh8BIeWAiGA XxTQ== X-Gm-Message-State: APjAAAVuA3BfznkulxtJOEx6zwYu0RAYady3vBuUnXEK+jFpNcKXlTJU ZIkeH+sZMHzDL5ue/jJKhbUMFG1Uya6eh0pphbUZf5Mq X-Google-Smtp-Source: APXvYqxjvf2HBu7MdMzYnbnXjGLiV0GijkIPGg06AnBkjISI3tz9H0pSaU0OSwu2BNfJ65Bb4R+Q18hx9caYqcwoH9w= X-Received: by 2002:a50:c28a:: with SMTP id o10mr79181397edf.182.1564123291436; Thu, 25 Jul 2019 23:41:31 -0700 (PDT) MIME-Version: 1.0 References: <7318D717-50F7-4C5E-9F49-B185B0186CC1@cisco.com> In-Reply-To: <7318D717-50F7-4C5E-9F49-B185B0186CC1@cisco.com> From: Michael Baddeley Date: Fri, 26 Jul 2019 07:41:20 +0100 Message-ID: To: Routing Over Low power and Lossy networks Content-Type: multipart/alternative; boundary="0000000000002bcd29058e8fd595" Archived-At: Subject: Re: [Roll] stitching PDAO segments X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jul 2019 06:41:35 -0000 --0000000000002bcd29058e8fd595 Content-Type: text/plain; charset="UTF-8" > > > A 6TiSCH tract is computed by a pce but with RPL the nodes do not care > where that logical function is located and simply talk to the root. Either > the root hosts a pce or it talks to a pce to get the computation done. > > > > Pascal, Just to be clear for my own understanding: is a 6TiSCH track defined as centrally computed by a PCE? I thought tracks could also be allocated with soft cells in a distributed hop-by-hop manner? (for example, along the RPL route). Regards, Michael --0000000000002bcd29058e8fd595 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


A 6TiSCH tract is computed by a= pce but with RPL the nodes do not care where that logical function is loca= ted and simply talk to the root. Either the root hosts a pce or it talks to= a pce to get the computation done.

=C2=A0

<= /div>
Pascal,=C2=A0

Just to be clear for my own understanding: is a 6Ti= SCH track defined as centrally computed by a PCE? I thought tracks could al= so be allocated with soft cells in a distributed hop-by-hop manner? (for ex= ample, along the RPL route).

Regards,

Michael
--0000000000002bcd29058e8fd595--