@techreport{bowers-spring-adv-per-algorithm-label-blocks-02,
    number =    {draft-bowers-spring-adv-per-algorithm-label-blocks-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-bowers-spring-adv-per-algorithm-label-blocks/02/},
    author =    {Chris Bowers and Hannes Gredler and Uma Chunduri},
    title =     {{Advertising Per-Topology and Per-Algorithm Label Blocks}},
    pagetotal = 14,
    year =      2015,
    month =     oct,
    day =       5,
    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).},
}