[Bier] Questions on draft-zhang-bier-te-yang

[benjamin r <[e-mail]>]

Hi,

Authors, please clarify the below questions.

      module: ietf-bier-te
        augment /rt:routing:
          +--rw bier-te
             +--rw subdomain* [subdomain-id]
                +--rw subdomain-id    uint16
                +--rw te-adj-id
                |  +--rw si* [si]
                |     +--rw si     uint16
                |     +--rw adj* [adj-id]
                |        +--rw adj-id     uint16
                |        +--rw adj-if     if:interface-ref
                |        +--rw bp-type?   Enumeration // BEN1
BEN1//
Bp-type is the property of interface and I think the bp-type will not change (or) need to be configured for each SD.
Example: bp-type of an interface is p2p no matter the SD ?
Considering this, can we remove this config under SD and instead define this bp-type configuration under bier-te/adj-if
This means, a hierarchy like "bier-te/adj-if/bp-type".

                +--rw bsl* [fwd-bsl]
                |  +--rw fwd-bsl    uint16
                |  +--rw si* [si]
                |     +--rw si            uint16
                |     +--rw te-bift-id
                |     |  +--rw type?    enumeration
                |     |  +--rw value    rt-types:mpls-label
                |     +--rw fwd-items* [te-bp]
                |        +--rw te-bp       uint16
                |        +--rw bp-type?    enumeration // BEN2
BEN2//
Fwd-items need not have bp-type. I think there is no use of this field in forwarding. Can this be removed ?
                |        +--rw (fwd-type)
                |        |  +--:(connected)
                |        |  +--:(routed)
                |        |  +--:(local-decap)
                |        |  +--:(other)
                |        +--rw dnr-flag?   boolean
                |        +--rw out-info //BEN3
BEN3//

"Section 3.6. Requirements"  of draft-ietf-bier-te-arch-01:
"BIER-TE forwarding MAY support more than one adjacency on a bit and
ECMP adjacencies."

It is advantageous to have a single bit position mapped to more than one adjacency.
So the fields like out-info, fwd-type, dnr-flag etc need to be grouped to a container, and there can be a list of this container under te-bp.

                |        |  +--rw fwd-intf          if:interface-ref
                |        |  +--rw te-out-bift-id
                |        |     +--rw type?    enumeration
                |        |     +--rw value    rt-types:mpls-label
                |        +--rw te-frr {bier-te-frr}?
                |        |  +--rw frr-index?      uint16
                |        |  +--rw resetbitmask* [bitmask]
                |        |     +--rw bitmask    bit-string
                |        +--rw te-ecmp* [out-if] {bier-te-ecmp}?
                |           +--rw out-if            if:interface-ref
                |           +--rw te-out-bift-id
                |              +--rw type?    enumeration
                |              +--rw value    rt-types:mpls-label




Thanks
Benjamin R
VRP PDU, Network Business Line
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka
Tel: + 91-80-49160700 Ext II Mob: [phone] Email: [e-mail]<mailto:[e-mail]>
[Company_logo]


________________________________

This e-mail and its attachments contain confidential information from HUAWEI, which
is intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!