Re: [6tsch] work item 2: centralized route and track computation with PCE
Michael Richardson <mcr+ietf@sandelman.ca> Tue, 23 July 2013 18:14 UTC
Return-Path: <mcr@sandelman.ca>
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 5A0B911E834C for <6tsch@ietfa.amsl.com>;
Tue, 23 Jul 2013 11:14:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
tests=[BAYES_00=-2.599]
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 zhdPF0Ie4DuR for
<6tsch@ietfa.amsl.com>; Tue, 23 Jul 2013 11:14:13 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184])
by ietfa.amsl.com (Postfix) with ESMTP id D64A311E8350 for <6tsch@ietf.org>;
Tue, 23 Jul 2013 11:14:10 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by
tuna.sandelman.ca (Postfix) with ESMTP id 87FC720181;
Tue, 23 Jul 2013 15:19:40 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 435A263A88;
Tue, 23 Jul 2013 14:12:41 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix)
with ESMTP id 2224B63A7C; Tue, 23 Jul 2013 14:12:41 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>
In-Reply-To: <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>
<E045AECD98228444A58C61C200AE1BD84139FC69@xmb-rcd-x01.cisco.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;
<'$9xN5Ub#
z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1;
protocol="application/pgp-signature"
Date: Tue, 23 Jul 2013 14:12:40 -0400
Message-ID: <23644.1374603160@sandelman.ca>
Sender: mcr@sandelman.ca
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 18:14:18 -0000
Pascal Thubert (pthubert) <pthubert@cisco.com> wrote: > That was the original idea. But there is so much more to do than > incremental PCEP that we fell back to requirements and architecture. What's important is that the charter explain that PCEP is in context, and that extensions to it are. If there are more things that need to be done that do not overlap any other WG, then the need to do them will become obvious from the requirements. > Also the PCEP changes may better be done within PCE WG if we have a > clean req + archi to explain what we need. Don't preclude the decision by the IESG. There is no doubt that the PCE WG will be asked to review, but if they are about to be closed, or are busy doing other things, or have little common people with IoT, then it makes no sense. The IESG might find an PCE expert to review, or even to co-chair. -- Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
- [6tsch] work item 2: centralized route and track … Pascal Thubert (pthubert)
- Re: [6tsch] work item 2: centralized route and tr… Xavier Vilajosana Guillen
- Re: [6tsch] work item 2: centralized route and tr… Pascal Thubert (pthubert)
- Re: [6tsch] work item 2: centralized route and tr… Maria Rita PALATTELLA
- Re: [6tsch] work item 2: centralized route and tr… Qin Wang
- Re: [6tsch] work item 2: centralized route and tr… Pascal Thubert (pthubert)
- [6tsch] work item 2: centralized route and track … Pascal Thubert (pthubert)
- Re: [6tsch] work item 2: centralized route and tr… Maria Rita PALATTELLA
- Re: [6tsch] work item 2: centralized route and tr… Michael Richardson
- Re: [6tsch] work item 2: centralized route and tr… Pascal Thubert (pthubert)
- Re: [6tsch] work item 2: centralized route and tr… Raghuram Sudhaakar (rsudhaak)
- Re: [6tsch] work item 2: centralized route and tr… Pascal Thubert (pthubert)
- Re: [6tsch] work item 2: centralized route and tr… Thomas Watteyne
- Re: [6tsch] work item 2: centralized route and tr… Michael Richardson
- Re: [6tsch] work item 2: centralized route and tr… Pascal Thubert (pthubert)
- Re: [6tsch] work item 2: centralized route and tr… Pascal Thubert (pthubert)
- Re: [6tsch] work item 2: centralized route and tr… Thomas Watteyne
- Re: [6tsch] work item 2: centralized route and tr… Pascal Thubert (pthubert)
- Re: [6tsch] work item 2: centralized route and tr… Michael Richardson
- Re: [6tsch] work item 2: centralized route and tr… Pascal Thubert (pthubert)
- Re: [6tsch] work item 2: centralized route and tr… Michael Richardson
- Re: [6tsch] work item 2: centralized route and tr… Thomas Watteyne