The MPLS-OPS Archive

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



[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: Wed, 30 Oct 2002 15:33:36 +0800
  • Cc: mpls-ops@mplsrc.com, lixia@CS.UCLA.EDU
  • Resent-Date: Wed, 30 Oct 2002 03:43:28 -0500
  • To: "M. ELK" <elkou141061@hotmail.com>

BUT accordong to RFC2205, "A service-specific calculation of Path_Te, the SUM of all
Tspecs that were supplied in Path messages from different  previous hops". NOT THE LUB.
 
It means in Router1 Ic will reserve min(path_te,Resv_Te),while path_Te=4M and Resv_Te=3M?
 
It's funny. what's wrong
                ______________                ____________
S1(REQ 2M)----Ia|             |               |           |
                |     Router1 |Ic___________Id| Router2   |Ie____|
S2(REQ 2M)----Ib| 
            |               |           |      |
                |_____________|               |___________|      |
                                                         |
                                                         |ROUTER3
                                                         |
                ______________                                   |      
                |             |                                  |
S3(REQ 3M)----If|     Router1 |Ig________________________________|
                | 
            |                                  |
                |_____________|               
> >                         |
> >           Sends         |       Reserves             Receives
> >                         |
> >                         |       ________
> >    SE( S1{?B} ) <- (a)  |  (c) |(S1,S2) |   (c) <- SE( (S1,S2){2B} )
> >     
 
>Let us call the above node "R" ,
> Let us call the node upstream through interface "a"  R1 .
 
> R forward {2B} to R1 but do not make any reservation over interface  "a" .
> R1 recieving a request for {2B} over interface "a" .
> R1 calculate the Path_TE ( the sum of all Tspecs that were supplied in path
>msg's from different previous hob . pls refer to rfc 2205 sec 2.2 page 21) ,
>Since their is only one path msg which is from S1 forwarded to "a" so
>PATh_Te is equal to Tspec of S1 path msg ie: equal to {1B} .
 
>RSVP process on R1 will issue a "make reservation " call to "Traffic control" process (pls >refer to rfc 2205 sec 3.11.2 page 69) .
>the parametrs of such call :
>Interface which is equal to "a".
>TC_flowspec which is equal to {2B}
>TC_TSPEC which is Path_Te ie: {1B}
 
>For the traffic control at node R1, will make a reservation over interface "a" which is the >min (TC_flowspec,TC_TSpec ) ie: the reservation over interface "a" will be just {1B} .
 
> Let us call the above node "R" ,
>Let us call the node upstream through interface "a"  R1 .
 
> R forward {2B} to R1 but do not make any reservation over interface  "a" .
> R1 recieving a request for {2B} over interface "a" .
> R1 calculate the Path_TE ( the sum of all Tspecs that were supplied in path
>msg's from different previous hob . pls refer to rfc 2205 sec 2.2 page 21) ,
>Since their is only one path msg which is from S1 forwarded to "a" so
>PATh_Te is equal to Tspec of S1 path msg ie: equal to {1B} .
 
>RSVP process on R1 will issue a "make reservation " call to "Traffic control" process (pls >refer to rfc 2205 sec 3.11.2 page 69) .
>the parametrs of such call :
>Interface which is equal to "a".
>TC_flowspec which is equal to {2B}
>TC_TSPEC which is Path_Te ie: {1B}
 
>For the traffic control at node R1, will make a reservation over interface "a" which is the >min (TC_flowspec,TC_TSpec ) ie: the reservation over interface "a" will be just {1B} .