SPRING WG, There was quite a lot of discussion in person after we presented draft-bowers-spring-adv-per-algorithm-label-blocks-01 in Prague, and there was also much discussion on this list about the issue raised by this draft. We have made two main additions to this revision of the draft to further this discussion.
1) We have included discussion of multiple topologies in addition to multiple algorithms, and we have modified the proposed ISIS extension to handle both multiple topologies and multiple algorithms. 2) We have tried to accurately describe a proposal, which was outlined on this list, for managing the assignment of per-topology/per-algorithm node index values, which we refer to as the "configured offset mapping method". We welcome feedback from the working group on this draft. Thanks, Chris -----Original Message----- From: internet-dra...@ietf.org [mailto:internet-dra...@ietf.org] Sent: Monday, October 05, 2015 2:05 PM To: Uma Chunduri <uma.chund...@ericsson.com>; Hannes Gredler <han...@juniper.net>; Pushpasis Sarkar <psar...@juniper.net>; Chris Bowers <cbow...@juniper.net>; Chris Bowers <cbow...@juniper.net>; Uma Chunduri <uma.chund...@ericsson.com>; Pushpasis Sarkar <psar...@juniper.net>; Hannes Gredler <han...@juniper.net> Subject: New Version Notification for draft-bowers-spring-adv-per-algorithm-label-blocks-02.txt A new version of I-D, draft-bowers-spring-adv-per-algorithm-label-blocks-02.txt has been successfully submitted by Chris Bowers and posted to the IETF repository. Name: draft-bowers-spring-adv-per-algorithm-label-blocks Revision: 02 Title: Advertising Per-Topology and Per-Algorithm Label Blocks Document date: 2015-10-05 Group: Individual Submission Pages: 14 URL: https://www.ietf.org/internet-drafts/draft-bowers-spring-adv-per-algorithm-label-blocks-02.txt Status: https://datatracker.ietf.org/doc/draft-bowers-spring-adv-per-algorithm-label-blocks/ Htmlized: https://tools.ietf.org/html/draft-bowers-spring-adv-per-algorithm-label-blocks-02 Diff: https://www.ietf.org/rfcdiff?url2=draft-bowers-spring-adv-per-algorithm-label-blocks-02 Abstract: When segment routing is used in a network that is controlled by a link state IGP (such as ISIS or OSPF), each node in the network can be assigned one or more index numbers, known as "node-SIDs". The node-SIDs are unique within the network, and are known to all the nodes in the network. If an ingress node has a data packet to be sent to an egress node, the ingress node may select a node-SID corresponding to the egress node, and "translate" that node-SID to an MPLS label. The MPLS label represents a particular path to the egress node; the path is determined by applying a routing algorithm to a particular view of the network topology and a particular set of metric assignments to the links of that topology. The packet can then be forwarded by pushing the label on the packet's label stack and transmitting the packet to the next hop on the corresponding path to the egress node. This document compares two different procedures for translating a node-SID to the MPLS label that represents a path chosen by a particular algorithm operating on a particular topology. It also specifies the ISIS extensions needed to support one of the procedures (known as the "per-topology/per-algorithm label block" procedure). 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 spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
