[spring] Re： IPR poll - draft-hu-spring-segment-routing-proxy-forwarding
Yisong Liu <liuyisong@chinamobile.com> Fri, 14 January 2022 11:14 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 80CB63A2203; Fri, 14 Jan 2022 03:14:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.398
X-Spam-Level:
X-Spam-Status: No, score=-4.398 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_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 VWvqEB_cs_oq; Fri, 14 Jan 2022 03:14:22 -0800 (PST)
Received: from cmccmta1.chinamobile.com (cmccmta1.chinamobile.com [221.176.66.79]) by ietfa.amsl.com (Postfix) with ESMTP id F35753A2202; Fri, 14 Jan 2022 03:14:19 -0800 (PST)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.11]) by rmmx-syy-dmz-app03-12003 (RichMail) with SMTP id 2ee361e15b070b8-cc5b3; Fri, 14 Jan 2022 19:14:16 +0800 (CST)
X-RM-TRANSID: 2ee361e15b070b8-cc5b3
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from CMCC-PC (unknown[222.129.55.191]) by rmsmtp-syy-appsvr06-12006 (RichMail) with SMTP id 2ee661e15b06b43-2333c; Fri, 14 Jan 2022 19:14:16 +0800 (CST)
X-RM-TRANSID: 2ee661e15b06b43-2333c
MIME-Version: 1.0
x-PcFlag: c7b798dc-4d83-4adb-b821-b1ab0f1ec95b_5_51529
X-Mailer: PC_RICHMAIL 2.9.14
Date: Fri, 14 Jan 2022 19:14:14 +0800
From: Yisong Liu <liuyisong@chinamobile.com>
To: "bruno.decraene" <bruno.decraene@orange.com>, SPRING WG <spring@ietf.org>, draft-hu-spring-segment-routing-proxy-forwarding <draft-hu-spring-segment-routing-proxy-forwarding@ietf.org>
Message-ID: <202201141914141591155526@chinamobile.com>
Content-Type: multipart/Alternative; boundary="----=_001_NextPart1591155526_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/bpPCKzysEoNnellRm0Mkkktc9DU>
Subject: [spring] Re： IPR poll - 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:14:26 -0000
Hi WG，
I'm not aware of any undisclosed IPR related to this draft.
Best Regards
Yisong
发件人: bruno.decraene
时间: 2022/01/13(星期四)18:17
收件人: SPRING WG;draft-hu-spring-segment-routing-proxy-forwarding;
主题: IPR poll - draft-hu-spring-segment-routing-proxy-forwarding
Hi authors, contributors, WG
In preparation of the WG adoption call on draft-hu-spring-segment-routing-proxy-forwarding [1], this email starts a poll for IPR.
If you are an author or contributor to the subject document, please respond to this email. In your response, please indicate if all relevant IPR has been disclosed. If you know of relevant IPR that has not been disclosed, please state that and describe how this gap is being addressed.
Even if you are not a contributor or author, if you know of relevant IPR, please ensure that it has been dislosed as discussed in BCP 79.
If you know of someone else IPR that you believe is relevant and not disclosed, please file a third party IPR disclosure.
Thanks,
Regards,
Bruno, Jim, Joel
[1] https://datatracker.ietf.org/doc/draft-hu-spring-segment-routing-proxy-forwarding/
_________________________________________________________________________________________________________________________ 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.