The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2002-Oct> msg00087



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

Re: a question about SE sytle reservation

  • From: Terry Lee <terrylee@huawei.com>
  • Date: Thu, 17 Oct 2002 13:36:15 +0800
  • Cc: mpls-ops@mplsrc.com
  • Resent-Date: Thu, 17 Oct 2002 02:39:03 -0400
  • To: Lixia Zhang <lixia@CS.UCLA.EDU>

     For this question, we have concern about why  the  flowspec forwarded upstream 
      to  S1 should be  {2B} ? The  flowspec forwarded upstream to  S1  be  {1B} 
      can  also satisfy the request of Sender S1 . 

     Another question. after mergeing , the reservation in S1 should be {2B},
      when delete the path created by sender S2, the reservations in S1 also should 
      be {2B}. At that time, S2 doesn't share reservations  with S1, S1 only need {1B},
      allocate S1 {2B} may be waste. What do you think about this  instance ?  

----- Original Message ----- 
From: "Lixia Zhang" <lixia@CS.UCLA.EDU>
To: "Terry Lee" <terrylee@huawei.com>; <Braden@isi.edu>; <mpls-ops@mplssrc.com>
Sent: Thursday, October 17, 2002 11:02 AM
Subject: Re: a question about SE sytle reservation


> On 10/16/02 19:54, "Terry Lee" <terrylee@huawei.com> wrote:
> 
> > 
> >                         |
> >           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}?
> 
> 2B (Because it is a shared reservation, one must use the bigger one to fit
> both)
> 

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml