The MPLS-OPS Archive

[Terry Lee <terrylee@huawei.com>]

 

                          |
            Sends         |       Reserves             Receives
                          |
                          |       ________
     SE( S1{?B} ) <- (a)  |  (c) |(S1,S2) |   (c) <- SE( (S1,S2){2B} )
                          |      |  {2B}  |
                          |      |________|
     ---------------------|---------------------------------------------
                          |    
   SE( (S2){2B} ) <- (b)  |
                          |          
                          |   

 

            Figure 1: Shared-Explicit (SE) Reservation Example

 

      Figure 1 shows an example of Shared-Explicit (SE) style
      reservations.  There are two upstream senders; packets from sender S1
      arrive through previous hop (a), packets from sender S2 arrive through
      previous hop (b).
      There are only  one downstream receiver R1; packets bound for R1 are
      routed via outgoing interface (c) . 
      Sender S1 request SENDER_TSPEC {1B}, and Sender S2 request SENDER_TSPEC {2B}.
      When SE-style reservations are merged,  the  flowspec forwarded upstream
      to  S1 should be {1B} or {2B}?