[bess] Fw: New Version Notification for draft-lz-bess-srv6-service-capability-06.txt
liu.yao71@zte.com.cn Wed, 09 October 2024 02:06 UTC
Return-Path: <liu.yao71@zte.com.cn>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61FE9C1CAE79 for <bess@ietfa.amsl.com>; Tue, 8 Oct 2024 19:06:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dXffjf71UXqX for <bess@ietfa.amsl.com>; Tue, 8 Oct 2024 19:06:46 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41B93C1840C1 for <bess@ietf.org>; Tue, 8 Oct 2024 19:06:45 -0700 (PDT)
Received: from mse-fl1.zte.com.cn (unknown [10.5.228.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4XNbq63J8zz8RTZL for <bess@ietf.org>; Wed, 9 Oct 2024 10:06:42 +0800 (CST)
Received: from njy2app08.zte.com.cn ([10.40.13.206]) by mse-fl1.zte.com.cn with SMTP id 49926OcY020927 for <bess@ietf.org>; Wed, 9 Oct 2024 10:06:24 +0800 (+08) (envelope-from liu.yao71@zte.com.cn)
Received: from mapi (njy2app08[null]) by mapi (Zmail) with MAPI id mid203; Wed, 9 Oct 2024 10:06:25 +0800 (CST)
Date: Wed, 09 Oct 2024 10:06:25 +0800
X-Zmail-TransId: 2b006705e521ffffffff8a5-e18b4
X-Mailer: Zmail v1.0
Message-ID: <20241009100625838zbPqTF4_vSU9ET4fkwfqQ@zte.com.cn>
References: 172843710545.278.8621468568021872146@dt-datatracker-78dc5ccf94-w8wgc
Mime-Version: 1.0
From: liu.yao71@zte.com.cn
To: bess@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 49926OcY020927
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 6705E532.002/4XNbq63J8zz8RTZL
Message-ID-Hash: RFIEH4DI62A6JZDJ6725KKF5OSRJPUZK
X-Message-ID-Hash: RFIEH4DI62A6JZDJ6725KKF5OSRJPUZK
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
X-Mailman-Version: 3.3.9rc5
Precedence: list
Subject: [bess] Fw: New Version Notification for draft-lz-bess-srv6-service-capability-06.txt
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/36sUvQxB4BxJ2uwoqWSXYhqNYKw>
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, A new version of draft-lz-bess-srv6-service-capability has just been uploaded. Based on the specification in RFC9252 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 proposes an automatic advertisement controlling method for SRv6-based service routes by defining a new Capability Code for SRv6-based BGP service capability. In this version, the main changes are: a) The whole draft is reorganized for ease of reading. b) Another current practice to control the advertisement of the SRv6-based service routes is included and analyzed. The authors are looking forward to your review and comments. Thanks, Yao Original From: internet-drafts@ietf.org <internet-drafts@ietf.org> Date: 2024年10月09日 09:25 Subject: New Version Notification for draft-lz-bess-srv6-service-capability-06.txt A new version of Internet-Draft draft-lz-bess-srv6-service-capability-06.txt has been successfully submitted by Yao Liu and posted to the IETF repository. Name: draft-lz-bess-srv6-service-capability Revision: 06 Title: SRv6-based BGP Service Capability Date: 2024-10-08 Group: Individual Submission Pages: 9 URL: https://www.ietf.org/archive/id/draft-lz-bess-srv6-service-capability-06.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-06.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-06 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