Scribd Logo
Upload

Welcome to Scribd!

  • Slides 91 Bier 0 PDF

    Uploaded by

    Pravin Bhandarkar
    42 views9 pages
    This document summarizes a presentation on a draft proposing an encapsulation for Bit Index Explicit Replication (BIER) that integrates BIER with MPLS. The encapsulation assigns an MPLS label to represent the BIER parameters, including the set of egress routers, set identifier, and bitstring length. This allows each router to map the label to the proper forwarding table for BIER. The encapsulation provides flexibility, leverages MPLS procedures, and integrates well with MPLS transport and applications. Some concerns were discussed, such as whether the label is really needed or if non-MPLS encapsulations could also work, but the MPLS approach was defended as providing advantages in many environments.

    Original Description:

    Original Title

    slides-91-bier-0.pdf

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This document summarizes a presentation on a draft proposing an encapsulation for Bit Index Explicit Replication (BIER) that integrates BIER with MPLS. The encapsulation assigns an MPLS label to represent the BIER parameters, including the set of egress routers, set identifier, and bitstring length. This allows each router to map the label to the proper forwarding table for BIER. The encapsulation provides flexibility, leverages MPLS procedures, and integrates well with MPLS transport and applications. Some concerns were discussed, such as whether the label is really needed or if non-MPLS encapsulations could also work, but the MPLS approach was defended as providing advantages in many environments.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    42 views9 pages

    Slides 91 Bier 0 PDF

    Uploaded by

    Pravin Bhandarkar
    This document summarizes a presentation on a draft proposing an encapsulation for Bit Index Explicit Replication (BIER) that integrates BIER with MPLS. The encapsulation assigns an MPLS label to represent the BIER parameters, including the set of egress routers, set identifier, and bitstring length. This allows each router to map the label to the proper forwarding table for BIER. The encapsulation provides flexibility, leverages MPLS procedures, and integrates well with MPLS transport and applications. Some concerns were discussed, such as whether the label is really needed or if non-MPLS encapsulations could also work, but the MPLS approach was defended as providing advantages in many environments.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 9

    BIER BOF

    IETF 91 Honolulu, Hawaii

    draft-wijnands-mpls-encapsulation-01
    Presenter:
    Jeffrey Zhang

    Juniper

    IJsbrand Wijnands (editor)

    Cisco

    Eric Rosen (editor)

    Juniper

    Andrew Dolganow

    Alcatel-Lucent

    Jeff Tantsura

    Ericsson

    Sam Aldrin

    Huawei

    Authors:

    Parameters for BIER Forwarding


    of Data Packets
    Set of Egress BFRs (BFERs)
    o Encoded as set of 1s in a BitString
    o To interpret BitString, must know:
    Length of BitString
    SetId: which BFR-id is represented by low-order bit

    Which underlay is being used


    o

    To find next hops for each packet

    Entropy
    o

    For ECMP

    These parameters must be inferable from data packet

    header
    IETF 91 - Honolulu, Hawaii, November 9-14, 2014

    Encaps

    dispatch payload (part of packet beneath BIER header)


    o Allow payload to be MPLS packet

    IETF 91 - Honolulu, Hawaii, November 9-14, 2014

    Strategy Behind Design of Encaps


    Since BIER already has IGP-based control plane, needed to
    advertise

    Since BIER
    BFR-Ids,
    already
    etc.:has IGP-based control plane, needed to

    advertise
    BFR-Ids,
    o Piggyback
    on this etc.:
    to allow each BFR to assign an MPLS label to the triple:

    <
    SetId,
    , BitString
    underlay>
    oSetId
    Piggyback
    onLength,
    this to allow
    each BFR to assign an MPLS label to the triple:
    Length,
    underlay>
    (Detail: OSPF draft actually assigns label range to sequence of SetIds
    SetIds, instead of

    assigning single label to single SetId


    SetId)
    )
    o No additional MPLS control protocols
    are needed

    , instead of

    o No additional MPLS control protocols are needed


    MPLS label serves as a (locally significant) lookup key for this triple
    Label
    MPLSprecedes
    label serves
    BIER
    as header:
    a (locally significant) lookup key for this triple
    o Appears as bottom label of label stack
    Label precedes BIER header:
    o Serves
    Appearsasaslookup
    bottomkey
    label
    for of
    proper
    label Bit
    stack
    Index Forwarding Table
    o Serves as lookup key for proper Bit Index Forwarding Table
    Additional labels (as needed for app) may follow BIER header, as

    part of payload
    partofAdditional
    payload labels (as needed for app) may follow BIER header, as
    Integrates BIER well with MPLS transport and with MPLS-based
    applications
    Integrates BIER well with MPLS transport and with MPLS-based
    IETF 91 - Honolulu, Hawaii, November 9-14, 2014

    MPLS BIER Header


    Top Label

    Bottom Label

    BIER header

    Payload

    Between MPLS and Payload

    MPLS Label stack from top to bottom

    IPv4/IPv6/MPLS

    Top Label

    (Note: Bottom Label will usually be the only label in this stack)

    Bottom Label

    Represents SetId, underlay, and BitString length; also indicates that BIER header
    is following.

    BIER header

    The BIER header encoded between MPLS and payload

    Payload

    Payload (type is indicated in the BIER header)

    I: BFIR-id present
    IETF 91 - Honolulu, Hawaii, November 9-14, 2014

    Advantages of Integration with MPLS


    Flexibility to add additional forwarding parameters without changing

    the encapsulation format

    o Example: maybe the best way to identify an underlay is with a TLV; one
    could bind a label to a TLV, but one wouldnt want the TLV in the data
    packet encapsulation header.
    Leverages MPLS forwarding procedures
    o Label maps to Bit Index Forwarding Table
    o Reduces need to string together lookup key out of multiple header fields
    o Very simple integration with MPLS protection schemes
    No need for additional layer 2 codepoints
    When MPLS based FRR is used, no need for special label to indicate

    payload is BIER

    IETF 91 - Honolulu, Hawaii, November 9-14, 2014

    CControversies re MPLS Integration


    I like BIER, but I hate MPLS
    o Rename the MPLS Label to be the BIER Lookup Key

    Having to maintain and distribute locally significant lookup

    keys requires too much state and protocol.


    o Compared to the amount of state and protocol required to maintain/
    distribute the BFR-ids???

    My hardware cant swap header fields


    o Hard to do BIER (or even IP) if you cant modify the header fields!

    But isnt it better if one size fits all?


    o No.

    A longer, non-MPLS, encapsulation could easily be developed


    o may be a viable option in some environments,
    o but that doesnt eliminate the advantages of using the MPLS encapsulation.
    IETF 91 - Honolulu, Hawaii, November 9-14, 2014

    IETF 91 - Honolulu, Hawaii, November 9-14, 2014

    Thank you.

    You might also like