I don’t understand the practical use of this draft. If a node is going to pull SID information from the IGP as advertised by the SRMN, that node needs to understand whatever extensions you add to the IGP, and needs to be able to parse things to figure out what its own local label range is. That’s pretty much exactly the work that the node would need to do with the current IGP extensions, where it advertises its own range+offset.
I’m having trouble coming up with a scenario where your approach is easier, more scalable, or otherwise beneficial in some way not covered by existing technology. Can you clarify this for me? I don’t mean “tell me how it’s *different* from what’s already defined”, I mean “tell me why it’s *better* than what’s already defined” eric From: Isis-wg [mailto:isis-wg-boun...@ietf.org] On Behalf Of liao.t...@zte.com.cn Sent: Friday, October 24, 2014 1:57 AM To: Hannes Gredler Cc: ospf@ietf.org; spr...@ietf.org; isis...@ietf.org Subject: [Isis-wg] 答复: Re: [spring] FW: New Version Notification for draft-lw-spring-sid-allocation-00.txt Hi, Hannes Thanks for your review and the good comments. In this draft, SID can be automatically generated by a control node (the Segment Routing Management Nodes (SRMNs)), and the SRMNs generate the SID mapping to each node in the SR domain, then the IGP extension flooding out to every node, each node will know the sid allocated to each other. While if we use Netconf/YANG, all the nodes in the SR domain should be supported the open interface to Netconf/YANG, which is not easy, for many ASGs, CSGs only support SNMP protocol in the IP RAN scenarios. So this solution could simpify the conguration of ASG,CSG(actually it is zero-configuratin for them), which is very important for the operation. Best Regards. Ting Hannes Gredler <han...@juniper.net<mailto:han...@juniper.net>> 2014-10-23 23:46 收件人 <liao.t...@zte.com.cn<mailto:liao.t...@zte.com.cn>> 抄送 "spr...@ietf.org<mailto:spr...@ietf.org>" <spr...@ietf.org<mailto:spr...@ietf.org>>, "isis...@ietf.org<mailto:isis...@ietf.org>" <isis...@ietf.org<mailto:isis...@ietf.org>>, "ospf@ietf.org<mailto:ospf@ietf.org>" <ospf@ietf.org<mailto:ospf@ietf.org>> 主题 Re: [spring] FW: New Version Notification for draft-lw-spring-sid-allocation-00.txt liao, my read of your draft is that you're utilizing IGP extensions to flood configuration informatioun through the network. have you considered using netconf/YANG for doing so ? and if so what is wrong (what are the shortcomings) of netconf/YANG to configure RAN routers ? IOW why are exisiting configuration mencahnism not good enough ? /hannes On Wed, Oct 22, 2014 at 05:35:48PM +0800, liao.t...@zte.com.cn<mailto:liao.t...@zte.com.cn> wrote: | In some situation where users expect to simply plug in a SR node and have | it automatically use Segment Routing. | This draft attempts to solve this need. | Expecting your review and comments. Thank you. | | Best Regards. | Ting, Bo, Fangwei, and Bhumip | | ----- ת???Ë ?Î?Ã038768/user/zte_ltd ʱ?? 2014-10-22 16:11 ----- | | internet-dra...@ietf.org<mailto:internet-dra...@ietf.org> ?Õ???Ë Bhumip Khasnabish | <bhumip.khasnab...@ztetx.com<mailto:bhumip.khasnab...@ztetx.com>>, "Bhumip | 2014-10-22 16:02 Khasnabish" <bhumip.khasnab...@ztetx.com<mailto:bhumip.khasnab...@ztetx.com>>, | "fangwei hu" <hu.fang...@zte.com.cn<mailto:hu.fang...@zte.com.cn>>, | Fangwei Hu <hu.fang...@zte.com.cn<mailto:hu.fang...@zte.com.cn>>, "Wu | Bo" <bo...@zte.com.cn<mailto:bo...@zte.com.cn>>, "Ting Liao" | <liao.t...@zte.com.cn<mailto:liao.t...@zte.com.cn>>, Ting Liao | <liao.t...@zte.com.cn<mailto:liao.t...@zte.com.cn>>, Bo Wu | <bo...@zte.com.cn<mailto:bo...@zte.com.cn>> | ???Í | ?÷?â New Version Notification for | draft-lw-spring-sid-allocation-00.txt | | | A new version of I-D, draft-lw-spring-sid-allocation-00.txt | has been successfully submitted by Fangwei Hu and posted to the | IETF repository. | | Name: draft-lw-spring-sid-allocation | Revision: 00 | Title: SPRING SID Allocation | Document date: 2014-10-22 | Group: Individual Submission | Pages: 12 | URL: | http://www.ietf.org/internet-drafts/draft-lw-spring-sid-allocation-00.txt | Status: | https://datatracker.ietf.org/doc/draft-lw-spring-sid-allocation/ | Htmlized: | http://tools.ietf.org/html/draft-lw-spring-sid-allocation-00 | | Abstract: | Segment Routing (SR) allows for a flexible definition of end-to-end | paths within IGP topologies by encoding paths as sequences of | topological sub-paths, called "segments". These segments are | advertised by the link-state routing protocols (IS-IS and OSPF). And | a segment is identified by a Segment Routing ID(SID). This document | proposes a method that the only selected SR nodes responsible for | allocating SIDs for a SR domain to reduce SID configuration required | on all SR nodes. | | | | | Please note that it may take a couple of minutes from the time of | submission | until the htmlized version and diff are available at tools.ietf.org. | | The IETF Secretariat | _______________________________________________ | spring mailing list | spr...@ietf.org<mailto:spr...@ietf.org> | https://www.ietf.org/mailman/listinfo/spring
_______________________________________________ OSPF mailing list OSPF@ietf.org https://www.ietf.org/mailman/listinfo/ospf