>[Nitin]:: Unicast multiple next hops are covered in Section 7.2.3.
><snip>
>[Nitin] LOAD_BALANCE_WEIGHT is the flag on the next-hop that is used to
>indicate ECMP/load-balancing
>> and multicast replication next hops.
>[Nintin] Section 7.3 talks about multicast replication (and refers to
>Section 7.2.2).
>
>[Sue]: You are stating that:
>
><nexthop-list> ::= (<nexthop> <LOAD_BALANCE_WEIGHT>) [(<nexthop>
><LOAD_BALANCE_WEIGHT>)... ]
>Is the flag for NH ECMP
>
><nexthop-list> ::= (<nexthop> <PROTECTION_PREFERENCE>)
> [(<nexthop> <PROTECTION_PREFERENCE>)... ]
>
>Sets primary/backup, and mixed with LOAD_BALANCE_WEIGHT - you groupings of
>next-hops that are used for multicast (as default).
>
> <nexthop-list> ::= <nexthop> [ <nexthop> ... ]
>
>This makes it specific, but requires you specify the LOAD_BALANCE_WEIGHT
>with each next hoip.
>Were you intended your LOAD_BALANCE_WEIGHT to be a integer, and the
>LOAD_PROTECTION_PREFERENCE to be a number.
>From the draft:
o PROTECTION_PREFERENCE: This provides a primary/backup like
preference. The preference is an integer value that should be set
to 1 (primary) or 2 (backup). Only when all the primary nexthops
fail is the traffic re-routed through the backup nexthops. This
attribute must be specified for all the members of a list or none
of them.
o LOAD_BALANCE_WEIGHT: This is used for load-balancing. Each list
member MUST be assigned a weight between 1 and 99. The weight
determines the proportion of traffic to be sent over a nexthop
used for forwarding as a ratio of the weight of this nexthop
divided by the weights of all the nexthops of this route that are
used for forwarding. To perform equal load-balancing, one MAY
specify a weight of "0" for all the member nexthops. The value
"0" is reserved for equal load-balancing and if applied, MUST be
applied to all member next hops.
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
