[spring] Re： WG adoption call - draft-hu-spring-segment-routing-proxy-forwarding
Yisong Liu <liuyisong@chinamobile.com> Fri, 14 January 2022 11:30 UTC
Return-Path: <liuyisong@chinamobile.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DB113A2243 for <spring@ietfa.amsl.com>; Fri, 14 Jan 2022 03:30:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.098
X-Spam-Level:
X-Spam-Status: No, score=-0.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.001, HDRS_MISSP=2.499, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 mRLhZTF99MZg for <spring@ietfa.amsl.com>; Fri, 14 Jan 2022 03:30:02 -0800 (PST)
Received: from cmccmta3.chinamobile.com (cmccmta3.chinamobile.com [221.176.66.81]) by ietfa.amsl.com (Postfix) with ESMTP id B2D773A2241 for <spring@ietf.org>; Fri, 14 Jan 2022 03:30:00 -0800 (PST)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.5]) by rmmx-syy-dmz-app09-12009 (RichMail) with SMTP id 2ee961e15eb33c3-cd1bf; Fri, 14 Jan 2022 19:29:59 +0800 (CST)
X-RM-TRANSID: 2ee961e15eb33c3-cd1bf
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from CMCC-PC (unknown[222.129.55.191]) by rmsmtp-syy-appsvr03-12003 (RichMail) with SMTP id 2ee361e15eb57af-fcc0f; Fri, 14 Jan 2022 19:29:59 +0800 (CST)
X-RM-TRANSID: 2ee361e15eb57af-fcc0f
MIME-Version: 1.0
x-PcFlag: 8c1128aa-645d-4b9a-963a-f5790262a733_5_51531
X-Mailer: PC_RICHMAIL 2.9.14
Date: Fri, 14 Jan 2022 19:29:57 +0800
From: Yisong Liu <liuyisong@chinamobile.com>
To: "bruno.decraene" <bruno.decraene@orange.com>, SPRING WG <spring@ietf.org>
Message-ID: <202201141929571592099306@chinamobile.com>
Content-Type: multipart/Alternative; boundary="----=_001_NextPart1592099306_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/7HVqVZ17E2vBwGX3hO3r7N4QKa4>
Subject: [spring] Re： WG adoption call - draft-hu-spring-segment-routing-proxy-forwarding
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jan 2022 11:30:05 -0000
Hi WG,
I support the adoption of this draft as co-author. It provides a midpoint protection mechanism and improves the SR local protection solution.
Best Regards
Yisong
发件人: bruno.decraene
时间: 2022/01/13(星期四)18:19
收件人: SPRING WG;
主题: [spring] WG adoption call - draft-hu-spring-segment-routing-proxy-forwarding
Dear WG,
This message starts a 2 week WG adoption call, ending 27/01/2022, for draft-hu-spring-segment-routing-proxy-forwarding
https://datatracker.ietf.org/doc/draft-hu-spring-segment-routing-proxy-forwarding/
After review of the document please indicate support (or not) for WG adoption of the document to the mailing list.
Please also provide comments/reasons for your support (or lack thereof) as this is a stronger way to indicate your (non) support as this is not a vote.
If you are willing to work on or review the document, please state this explicitly. This gives the chairs an indication of the energy level of people in the working group willing to work on the document.
Thanks!
Bruno, Jim, Joel
_________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.