Re: [Lsr] "IGP Extensions for Segment Routing Service Segment" -draft-lz-lsr-igp-sr-service-segments-02

liu.yao71@zte.com.cn Wed, 29 July 2020 01:57 UTC

Return-Path: <liu.yao71@zte.com.cn>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D37593A0E98 for <lsr@ietfa.amsl.com>; Tue, 28 Jul 2020 18:57:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level:
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 wIZe1QMfDxwd for <lsr@ietfa.amsl.com>; Tue, 28 Jul 2020 18:57:56 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FF583A0E8F for <lsr@ietf.org>; Tue, 28 Jul 2020 18:57:55 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.164.217]) by Forcepoint Email with ESMTPS id D9012D7A23A5259AEAC6 for <lsr@ietf.org>; Wed, 29 Jul 2020 09:57:53 +0800 (CST)
Received: from mse-fl1.zte.com.cn (unknown [10.30.14.238]) by Forcepoint Email with ESMTPS id B537D31DD3EDA5C9ABAF; Wed, 29 Jul 2020 09:57:53 +0800 (CST)
Received: from njxapp01.zte.com.cn ([10.41.132.200]) by mse-fl1.zte.com.cn with SMTP id 06T1vl1c016239; Wed, 29 Jul 2020 09:57:47 +0800 (GMT-8) (envelope-from liu.yao71@zte.com.cn)
Received: from mapi (njxapp01[null]) by mapi (Zmail) with MAPI id mid203; Wed, 29 Jul 2020 09:57:47 +0800 (CST)
Date: Wed, 29 Jul 2020 09:57:47 +0800
X-Zmail-TransId: 2af95f20d79b59d3e898
X-Mailer: Zmail v1.0
Message-ID: <202007290957472639201@zte.com.cn>
In-Reply-To: <E58BB9C0-2E74-4924-8117-4D35E534245A@cisco.com>
References: E58BB9C0-2E74-4924-8117-4D35E534245A@cisco.com
Mime-Version: 1.0
From: liu.yao71@zte.com.cn
To: acee@cisco.com
Cc: zzhang_ietf@hotmail.com, lsr@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 06T1vl1c016239
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/6sEQzcDLBfwXVhzDkr2AgqBeKNw>
Subject: Re: [Lsr] "IGP Extensions for Segment Routing Service Segment" -draft-lz-lsr-igp-sr-service-segments-02
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jul 2020 01:57:59 -0000

Hi Acee,

Thanks for reading the draft.

Yes, the main purpose of this draft is to carry the segment segment information via IGP so only one node per AS need to be connected with the controller through BGP-LS.

With the existing BGP-LS extension draft, it is certainly one solution to configure BGP sessions between all the service function nodes and controller, and each node sends the SF information to the controller individually.

And if I get you right, we can also select one node to have a BGP session with the controller and configure BGP sessions between the selected node and SF nodes.

But how the selected node get the SF information from SF nodes via BGP needs to be solved, since BGP-LS is typically used for exchanging information between the south and north rather than nodes of the same level, and there's no other existing BGP extension for distribute SIDs information between nodes .

This draft aims to provide an alternate way if the operators prefer running IGP on SF nodes.

So we would like to collect comments on the WG session to see how others think about it.






Regards,


Yao















原始邮件



发件人:AceeLindem(acee) <acee@cisco.com>
收件人:刘尧00165286;zzhang_ietf@hotmail.com <zzhang_ietf@hotmail.com>;
抄送人:lsr@ietf.org <lsr@ietf.org>;
日 期 :2020年07月29日 01:53
主 题 :"IGP Extensions for Segment Routing Service Segment" -draft-lz-lsr-igp-sr-service-segments-02




Speaking as WG member:


 


It seems the sole purpose of this draft is to get service segment information from nodes in the IGP domain to the IGP node that has a BGP session with the controller. You don’t need to put this information
 into the IGP in order to do this. Simply configure BGP sessions for the BGP-LS AF between the nodes with service functions and the node selected to have a BGP session with the controller.


 


Speaking as WG Chair – please let me know if we can omit this draft from the agenda.


 


Thanks,


Acee