IETF Logo Mail Archive

[Pce] 答复: Adoption of draft-li-pce-sr-bidir-path-06?

Zhenghaomian <zhenghaomian@huawei.com> Sun, 26 January 2020 14:17 UTC

Return-Path: <zhenghaomian@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C5B9120058 for <pce@ietfa.amsl.com>; Sun, 26 Jan 2020 06:17:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 Mm2E0pMRvAky for <pce@ietfa.amsl.com>; Sun, 26 Jan 2020 06:17:20 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 2A82F120043 for <pce@ietf.org>; Sun, 26 Jan 2020 06:17:20 -0800 (PST)
Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 94FA14E3F5F944E9B8CB for <pce@ietf.org>; Sun, 26 Jan 2020 14:17:14 +0000 (GMT)
Received: from lhreml743-chm.china.huawei.com (10.201.108.193) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sun, 26 Jan 2020 14:17:12 +0000
Received: from lhreml743-chm.china.huawei.com (10.201.108.193) by lhreml743-chm.china.huawei.com (10.201.108.193) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Sun, 26 Jan 2020 14:17:14 +0000
Received: from DGGEML406-HUB.china.huawei.com (10.3.17.50) by lhreml743-chm.china.huawei.com (10.201.108.193) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Sun, 26 Jan 2020 14:17:14 +0000
Received: from DGGEML511-MBX.china.huawei.com ([169.254.1.115]) by dggeml406-hub.china.huawei.com ([10.3.17.50]) with mapi id 14.03.0439.000; Sun, 26 Jan 2020 22:17:11 +0800
From: Zhenghaomian <zhenghaomian@huawei.com>
To: "julien.meuric@orange.com" <julien.meuric@orange.com>, "pce@ietf.org" <pce@ietf.org>
Thread-Topic: [Pce] Adoption of draft-li-pce-sr-bidir-path-06?
Thread-Index: AQHVzR65KH9CMZLatk6xE66AAy5MSKf9DEwA
Date: Sun, 26 Jan 2020 14:17:09 +0000
Message-ID: <E0C26CAA2504C84093A49B2CAC3261A43B96E79B@dggeml511-mbx.china.huawei.com>
References: <e69cdba1-69c2-583c-3eaf-f14265a45d74@orange.com>
In-Reply-To: <e69cdba1-69c2-583c-3eaf-f14265a45d74@orange.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.97.231]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/LG_7g9y7EzZyfsIytYPNhpuG8RM>
Subject: [Pce] 答复: Adoption of draft-li-pce-sr-bidir-path-06?
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jan 2020 14:17:22 -0000

Yes/Support. 

Best wishes,
Haomian

-----邮件原件-----
发件人: Pce [mailto:pce-bounces@ietf.org] 代表 julien.meuric@orange.com
发送时间: 2020年1月17日 18:13
收件人: pce@ietf.org
主题: [Pce] Adoption of draft-li-pce-sr-bidir-path-06?

Hi all,

It is time to share your thoughts about draft-li-pce-sr-bidir-path-06.
Do you believe the I-D is a right foundation for a PCE WG item? Please use the PCE mailing list to express your comments, support or disagreement, including applicable rationale, especially for the latter.

Thanks,

Dhruv & Julien

v2.23.0 | Report a Bug | By Email