IETF Logo Mail Archive

Re: [6tsch] work item 2: centralized route and track computation with PCE

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Tue, 23 July 2013 17:04 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: 6tsch@ietfa.amsl.com
Delivered-To: 6tsch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8082921E809F for <6tsch@ietfa.amsl.com>; Tue, 23 Jul 2013 10:04:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zIluG2bfupEw for <6tsch@ietfa.amsl.com>; Tue, 23 Jul 2013 10:04:36 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 857E111E82E7 for <6tsch@ietf.org>; Tue, 23 Jul 2013 10:04:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1564; q=dns/txt; s=iport; t=1374599074; x=1375808674; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=yFsJWSkxlDLvpXt0VSCtgMjBqBK9pM41E1EKpqYwkI8=; b=P89DknH7IHB9K9EN2Cpn3ncSwsR61jDmAgjJo+8ruU3aqQVYga+v7PJd bz1d0Sm7OuRpPhs7UqqzNllnH299GRuw5p/once6r5dV0ylZH1uulLuT7 lM9w8SbSwB4i4yTjcAsYlk49vnU1hqoS1KrN8ZwDVdYKgm5RHZoNTGwtI Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFAJm27lGtJXG9/2dsb2JhbABagwaBBcBJgRMWdIIkAQEBAwE6PwwEAgEIEQEDAQELFAkHMhQDBggCBA4FCIgCBrh0j0wxBwaDDG4DqSyDFIIq
X-IronPort-AV: E=Sophos;i="4.89,729,1367971200"; d="scan'208";a="238396188"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-3.cisco.com with ESMTP; 23 Jul 2013 17:04:23 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r6NH4NvN009718 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 23 Jul 2013 17:04:23 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.94]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.02.0318.004; Tue, 23 Jul 2013 12:04:22 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Thread-Topic: [6tsch] work item 2: centralized route and track computation with PCE
Thread-Index: AQHOh78y7OEYhHbYS+ueX7YfovBAQplyfQ4g
Date: Tue, 23 Jul 2013 17:04:21 +0000
Deferred-Delivery: Tue, 23 Jul 2013 17:04:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD84139FC69@xmb-rcd-x01.cisco.com>
References: <E045AECD98228444A58C61C200AE1BD841391C8B@xmb-rcd-x01.cisco.com> <CALEMV4YhEJuWDZx-js7ATQdfi+OUMc2LajV_pqmbk4EzDi_SOA@mail.gmail.com> <17244.1374587886@sandelman.ca> <E045AECD98228444A58C61C200AE1BD841393388@xmb-rcd-x01.cisco.com> <5067.1374595849@sandelman.ca>
In-Reply-To: <5067.1374595849@sandelman.ca>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.73.204]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Thomas Watteyne <watteyne@eecs.berkeley.edu>, "6tsch@ietf.org" <6tsch@ietf.org>
Subject: Re: [6tsch] work item 2: centralized route and track computation with PCE
X-BeenThere: 6tsch@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tsch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tsch>, <mailto:6tsch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6tsch>
List-Post: <mailto:6tsch@ietf.org>
List-Help: <mailto:6tsch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tsch>, <mailto:6tsch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jul 2013 17:04:42 -0000

Actually Michael,

That was the original idea. But there is so much more to do than incremental PCEP that we fell back to requirements and architecture.
Also the PCEP changes may better be done within PCE WG if we have a clean req + archi to explain what we need.

What do you think?

Pascal


-----Original Message-----
From: mcr@sandelman.ca [mailto:mcr@sandelman.ca] On Behalf Of Michael Richardson
Sent: mardi 23 juillet 2013 18:11
To: Pascal Thubert (pthubert)
Cc: 6tsch@ietf.org; Thomas Watteyne
Subject: Re: [6tsch] work item 2: centralized route and track computation with PCE


Pascal Thubert (pthubert) <pthubert@cisco.com> wrote:

    > We might simplify by omitting:

    > "
    > In detail, the WG will consider operations:
    > (1) from  the device routing layer to the PCE for
    > (i) sending topological information and routing metrics, and
    > (ii) getting on-demand routing information; and
    > (2) from the device 6top sublayer to the PCE for
    > (a) exporting neighboring and link quality statistics and
    > (b) requesting to (re)compute and install a track that meets explicit flow requirements.
    > "
    > From the charter though we all know that this work has to be done.

I suggest that the charter says,

"Based upon intended operations between the device routing layer, and the PCE, extensions to PCEP will be considered"

That's the only important thing: this WG is allowed to extend PCEP.

--
Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works

v2.8.7 | Report a Bug | By Email