[bess] Fw: New Version Notification for draft-lz-bess-srv6-service-capability-07.txt
liu.yao71@zte.com.cn Wed, 10 December 2025 01:38 UTC
Return-Path: <liu.yao71@zte.com.cn>
X-Original-To: bess@mail2.ietf.org
Delivered-To: bess@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id A40EC984CC40; Tue, 9 Dec 2025 17:38:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3H7oH8_WAhoq; Tue, 9 Dec 2025 17:38:13 -0800 (PST)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [160.30.148.34]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 1ABBE984CC38; Tue, 9 Dec 2025 17:38:12 -0800 (PST)
Received: from mse-fl2.zte.com.cn (unknown [10.5.228.133]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4dQyz61cfyz4xPB8; Wed, 10 Dec 2025 09:38:10 +0800 (CST)
Received: from njb2app05.zte.com.cn ([10.55.22.121]) by mse-fl2.zte.com.cn with SMTP id 5BA1bvhB086479; Wed, 10 Dec 2025 09:37:57 +0800 (+08) (envelope-from liu.yao71@zte.com.cn)
Received: from mapi (njy2app02[null]) by mapi (Zmail) with MAPI id mid203; Wed, 10 Dec 2025 09:37:58 +0800 (CST)
Date: Wed, 10 Dec 2025 09:37:58 +0800
X-Zmail-TransId: 2afa6938cef6617-fc25a
X-Mailer: Zmail v1.0
Message-ID: <20251210093758167jBQRUbe70O8nM9pFK-ER0@zte.com.cn>
References: 176527453617.1080797.3137884677666005894@dt-datatracker-5bd94c585b-wk4l4
Mime-Version: 1.0
From: liu.yao71@zte.com.cn
To: bess@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 5BA1bvhB086479
X-TLS: YES
X-SPF-DOMAIN: zte.com.cn
X-ENVELOPE-SENDER: liu.yao71@zte.com.cn
X-SPF: None
X-SOURCE-IP: 10.5.228.133 unknown Wed, 10 Dec 2025 09:38:10 +0800
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 6938CF02.000/4dQyz61cfyz4xPB8
Message-ID-Hash: TB5BAZ6VNFJURH3B6VCO5H4JCOGCINKX
X-Message-ID-Hash: TB5BAZ6VNFJURH3B6VCO5H4JCOGCINKX
X-MailFrom: liu.yao71@zte.com.cn
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-bess.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-lz-bess-srv6-service-capability@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [bess] Fw: New Version Notification for draft-lz-bess-srv6-service-capability-07.txt
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/GIFlh-eJwer9yIJivsbAG3Jrjg4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Owner: <mailto:bess-owner@ietf.org>
List-Post: <mailto:bess@ietf.org>
List-Subscribe: <mailto:bess-join@ietf.org>
List-Unsubscribe: <mailto:bess-leave@ietf.org>
Hi All, We've uploaded a new version of draft-lz-bess-srv6-service-capability which introduces a new BGP capability to indicate the support of SRv6-based BGP services. In this version, this draft has been changed from "Standards Track" to "Experimental", considering that there're already many implementations of SRv6-based BGP services based on the method of configuration, and a section has been added on how to upgrade the devices on the network to support the new capability in order to avoid interoperability problems. Any feedback or comments are more than welcome. Regards, Yao Original From: internet-drafts@ietf.org <internet-drafts@ietf.org> Date: 2025年12月09日 18:02 Subject: New Version Notification for draft-lz-bess-srv6-service-capability-07.txt A new version of Internet-Draft draft-lz-bess-srv6-service-capability-07.txt has been successfully submitted by Yao Liu and posted to the IETF repository. Name: draft-lz-bess-srv6-service-capability Revision: 07 Title: SRv6-based BGP Service Capability Date: 2025-12-09 Group: Individual Submission Pages: 9 URL: https://www.ietf.org/archive/id/draft-lz-bess-srv6-service-capability-07.txt Status: https://datatracker.ietf.org/doc/draft-lz-bess-srv6-service-capability/ HTML: https://www.ietf.org/archive/id/draft-lz-bess-srv6-service-capability-07.html HTMLized: https://datatracker.ietf.org/doc/html/draft-lz-bess-srv6-service-capability Diff: https://author-tools.ietf.org/iddiff?url2=draft-lz-bess-srv6-service-capability-07 Abstract: RFC9252 specifies that implementations MUST provide a mechanism to control advertisement of SRv6-based BGP service routes on a per neighbor and per service basis. This document provides analysis on the problems that may be encountered if the SRv6-based service routes are received by the MPLS-only PEs. Some currently used SRv6-based service routes advertisement controlling methods by configuration or network planning are also described. And this document proposes an automatic advertisement controlling method for SRv6-based service routes by defining a new Capability Code for SRv6-based BGP service capability. The IETF Secretariat