Re: [Teas] WG adoption poll draft-zhao-teas-pce-control-function

"Scharf, Michael (Nokia - DE)" <michael.scharf@nokia.com> Fri, 30 September 2016 13:03 UTC

Return-Path: <michael.scharf@nokia.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B60D412B3A0 for <teas@ietfa.amsl.com>; Fri, 30 Sep 2016 06:03:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level:
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 jF0lCwbRT0IW for <teas@ietfa.amsl.com>; Fri, 30 Sep 2016 06:03:05 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6777112B39C for <teas@ietf.org>; Fri, 30 Sep 2016 06:03:01 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id 048B3D729DC5D; Fri, 30 Sep 2016 13:02:56 +0000 (GMT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u8UD2wN5009502 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 30 Sep 2016 13:02:58 GMT
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u8UD2vE9000493 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 30 Sep 2016 15:02:57 +0200
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.135]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0301.000; Fri, 30 Sep 2016 15:02:57 +0200
From: "Scharf, Michael (Nokia - DE)" <michael.scharf@nokia.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'Igor Bryskin' <Igor.Bryskin@huawei.com>
Thread-Topic: [Teas] WG adoption poll draft-zhao-teas-pce-control-function
Thread-Index: AQHR+MsdeahL2I+PW0CEZwKoDr4uMgK1IXSeAVdjs3KhAtyYUP9vAdQw
Date: Fri, 30 Sep 2016 13:02:56 +0000
Message-ID: <655C07320163294895BBADA28372AF5D48AC9527@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <b2134da4-a438-0462-b7b2-ccb5a6d7a858@labn.net> <000efdef-b3b1-56d5-80db-1193a3026105@labn.net> <0C72C38E7EBC34499E8A9E7DD007863908EFCBC3@dfweml501-mbx> <09ea01d21b18$1149f3f0$33dddbd0$@olddog.co.uk>
In-Reply-To: <09ea01d21b18$1149f3f0$33dddbd0$@olddog.co.uk>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/p9aGhuOAi49weEwOvQU81TvX6-s>
Cc: 'TEAS WG' <teas@ietf.org>
Subject: Re: [Teas] WG adoption poll draft-zhao-teas-pce-control-function
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Sep 2016 13:03:06 -0000

> I suppose we have to choose. At the time of writing, no-one had seriously
> proposed using PCEP on that interface. I suppose we would only consider that
> if there is enthusiasm to implement. Do you want to?
> 
> But look at Figure 6.

I am not aware of any enthusiasm to implement PCEP on some interfaces shown in Figure 6.

Thanks

Michael