Re: [spring] Fwd: I-D Action:draft-cheng-spring-srv6-resource-programming-00.txt
姜文颖 <jiangwenying@chinamobile.com> Thu, 10 November 2022 15:20 UTC
Return-Path: <jiangwenying@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 47B02C1522AD for <spring@ietfa.amsl.com>; Thu, 10 Nov 2022 07:20:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.606
X-Spam-Level:
X-Spam-Status: No, score=-2.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 uG1-hWl3eyoz for <spring@ietfa.amsl.com>; Thu, 10 Nov 2022 07:20:24 -0800 (PST)
Received: from cmccmta1.chinamobile.com (cmccmta1.chinamobile.com [221.176.66.79]) by ietfa.amsl.com (Postfix) with ESMTP id D4DD7C14F743 for <spring@ietf.org>; Thu, 10 Nov 2022 07:20:22 -0800 (PST)
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[172.16.121.95]) by rmmx-syy-dmz-app03-12003 (RichMail) with SMTP id 2ee3636d16b5079-5ef54; Thu, 10 Nov 2022 23:20:21 +0800 (CST)
X-RM-TRANSID: 2ee3636d16b5079-5ef54
X-RM-SPAM-FLAG: 00000000
Received: from jiangwenying@chinamobile.com ( [172.16.114.1] ) by ajax-webmail-syy-appsvrnew08-11018 (Richmail) with HTTP; Thu, 10 Nov 2022 23:20:20 +0800 (CST)
Date: Thu, 10 Nov 2022 23:20:20 +0800
From: 姜文颖 <jiangwenying@chinamobile.com>
To: Robert Raszuk <robert@raszuk.net>, SPRING WG <spring@ietf.org>
Cc: 程伟强 <chengweiqiang@chinamobile.com>, "chen.ran" <chen.ran@zte.com.cn>, linchangwang <linchangwang.04414@h3c.com>, "zhao.detao" <zhao.detao@zte.com.cn>
Message-ID: <2b0a636d0f62275-00027.Richmail.00006070664026585547@chinamobile.com>
References: <165753377735.4976.3539236774327005092@ietfa.amsl.com>, <CAOj+MMG2rK22Wq7FrRhVsV+RXgOU4H8kNJZ+-e9UbYbLx1Vmtw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_273431_92018248.1668093620648"
X-Priority: 3
X-RM-TRANSID: 2b0a636d0f62275-00027
Encrypt-Channel: web
X-RM-OA-ENC-TYPE: 0
X-RM-FontColor: 0
X-CLIENT-INFO: X-TIMING=0&X-MASSSENT=0&X-SENSITIVE=0
X-Mailer: Richmail_Webapp(V2.4.15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/aHQ71QkUmGc7z-Lvo8QBt6euKZs>
Subject: Re: [spring] Fwd: I-D Action:draft-cheng-spring-srv6-resource-programming-00.txt
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 10 Nov 2022 15:20:27 -0000
Hi R, Thanks for your comments. 1. The solution in this draft is compliant with the SR architecture and design principles. The SR path selection is still in the ingress node. The End.NRP SID can be used to build SR path at the ingress node similar to the End.X SID. 2. The End.X cannot provide the capability of forwarding resource guarantee which is often required by some important customers. According to the description in Section 4.2 of RFC 8986, End.X forwards to an endpoint with cross-connect to a 39layer-3 adjacency39. While, the End.NRP can be associated with the both adjacency and forwarding resources. B.R. Wenying ----邮件原文----发件人:Robert Raszuk <robert@raszuk.net>收件人:SPRING WG <spring@ietf.org>抄 送: (无)发送时间:2022-11-08 19:23:35主题:[spring] Fwd: I-D Action:draft-cheng-spring-srv6-resource-programming-00.txtDear WG,This draft is one more attempt to shift SR path selection from ingress node to segment endpoints. Is such direction really something Spring wg endorses ? Functionally all of this type of proposals can be done on ingress nodes making transit nodes lean and carrying less state just using End.X to direct to segments. Just a general observation .... Thx R. ---------- Forwarded message ---------From: <internet-drafts@ietf.org>Date: Mon, Jul 11, 2022, 11:03Subject: I-D Action: draft-cheng-spring-srv6-resource-programming-00.txtTo: <i-d-announce@ietf.org> A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Network Resource Programming with SRv6 Authors : Weiqiang Cheng Wenying Jiang Ran Chen Detao Zhao Changwang Lin Filename : draft-cheng-spring-srv6-resource-programming-00.txt Pages : 8 Date : 2022-07-11 Abstract: This document defines a new SRv6 network function which can be used for SRv6 Network Resource Programming. A new SRv6 Endpoint behavior is used to associate with a set of network resource partition, called End.NRP. By using the End.NRP SID , the SRv6 policy can provide the capability of network resources programming. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-cheng-spring-srv6-resource-programming/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-cheng-spring-srv6-resource-programming-00 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt