Re: Comments on draft-katz-yeung-traffic-08.txt
Sina Mirtorabi <sina@CISCO.COM> Mon, 21 October 2002 18:24 UTC
Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09344 for <ospf-archive@LISTS.IETF.ORG>; Mon, 21 Oct 2002 14:24:31 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <18.00784F95@cherry.ease.lsoft.com>; Mon, 21 Oct 2002 14:26:45 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 322325 for OSPF@DISCUSS.MICROSOFT.COM; Mon, 21 Oct 2002 14:26:45 -0400
Received: from 171.68.227.73 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Mon, 21 Oct 2002 14:26:45 -0400
Received: from SMIRTORAW2K (par-ilm-dhcp1-vl133-19.cisco.com [144.254.54.214]) by fire.cisco.com (8.11.6+Sun/8.8.8) with SMTP id g9LIQh017607 for <OSPF@DISCUSS.MICROSOFT.COM>; Mon, 21 Oct 2002 11:26:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
Message-ID: <ECEBIKJEBCOMCBDBKDNBMEPECEAA.sina@cisco.com>
Date: Mon, 21 Oct 2002 11:26:43 -0700
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: Sina Mirtorabi <sina@CISCO.COM>
Subject: Re: Comments on draft-katz-yeung-traffic-08.txt
To: OSPF@DISCUSS.MICROSOFT.COM
In-Reply-To: <200210191802.OAA18430@bigbird.xebeo.com>
Precedence: list
Content-Transfer-Encoding: 7bit
Rohit, > -----Original Message----- > From: Mailing List [mailto:OSPF@DISCUSS.MICROSOFT.COM]On Behalf Of Rohit > Dube > Sent: Saturday, October 19, 2002 11:02 AM > To: OSPF@DISCUSS.MICROSOFT.COM > Subject: Re: Comments on draft-katz-yeung-traffic-08.txt > > > Hello Naiming, > > Thanks for your thoughtful comments. There are two ways one can > look at TE over multi-access links - > > a) Only 2 devices are allowed. This was my interpretation based > on section 1.2. My take is that if the condition is violated > (ie there are more than 2 devices) one needs to spell out > how to react to this. this is not how I would interpret. section 1.2 of the draft states: "The extensions specified in this document capture the reservation state of point-to-point links. The reservation state of multiaccess links is not accurately _reflected_, except in the special case that there are only two devices in the multiaccess subnetwork." > b) More than 2 devices are allowed which can work given the > limitations you list below. If this is allowed, we need > to explicitly say so and indicate any additional procedures > in the draft. > yes this is how I would read the draft... as far as for additional procedure, what else is needed to define a TE over multi-acess link having more than two attached routers? ( given the limitation for reservation state ) since 'Maximum Reservable Bandwidth' is configurable it is up to the operator to set a value that reflect a bit better the number of routers attached to the multi-acess network for example if there are N routers attached and we do not want to oversubscribe one could set Maximum Reservable Bandwidth <= Maximum Bandwidth / ( N-1 ) where N is the number of routers attached to multi-acess link Sina > Either way, I think the item needs to be clarified. > > Best, > --rohit. > > On Fri, 18 Oct 2002 23:07:55 -0700 Naiming Shen writes: > =>there is no need to withdraw TE LSAs while more than two routers > =>start to exist on the multi-access network. the TE draft says > =>clearly there will be limitations(verses the p2p link), but this > =>does not at all mean you can not run TE on that multi-access link > =>with multiple-routers. it's perfectly "fine" to setup TE tunnels > =>with multiple routers over the same multi-access link. > => > =>will this cause problem in terms of congestion? yes, it can. but > => > => - even over p2p TE links, we only reserve the bandwidth for > => the TE links, we can still "overbook" the bandwidth and congest > => the p2p TE links. > => > => - TE is usually used to route traffic for the purpose of saving > => cost in the long-haul p2p links. those multi-router/multi-access > => link usually is close to the edge of the network. even there is > => congestion going on, there probably is not much you can do to > => route around them. If there is congestion, simple add more > => bandwith there and the cost should be low. > => > =>since there will be a need to do TE with multiple routers on a LAN, > =>i think specifying the remote ip of 0.0.0.0 is OK, the draft probably > =>should say "or this TLV can be omitted". specifying a real IP address > =>even in the case of only two routers on the LAN does not sound right. > =>for p2p link, you have to specify the neighbor IP address, since > =>otherwise, in the case of parallel p2p links, there will be no > =>other indication to flag the match at both ends. for LAN, you have > =>the DR interface address to tie them ends together. > => > =>thanks.
- Comments on draft-katz-yeung-traffic-08.txt Acee Lindem
- Re: Comments on draft-katz-yeung-traffic-08.txt Kireeti Kompella
- Re: Comments on draft-katz-yeung-traffic-08.txt Rohit Dube
- Re: Comments on draft-katz-yeung-traffic-08.txt Acee Lindem
- Re: Comments on draft-katz-yeung-traffic-08.txt Don Goodspeed
- Re: Comments on draft-katz-yeung-traffic-08.txt Don Goodspeed
- Re: Comments on draft-katz-yeung-traffic-08.txt Tony Przygienda
- Re: Comments on draft-katz-yeung-traffic-08.txt Rohit Dube
- Re: Comments on draft-katz-yeung-traffic-08.txt Naidu, Venkata
- Re: Comments on draft-katz-yeung-traffic-08.txt Naiming Shen
- Re: Comments on draft-katz-yeung-traffic-08.txt Rohit Dube
- Re: Comments on draft-katz-yeung-traffic-08.txt Sina Mirtorabi
- Re: Comments on draft-katz-yeung-traffic-08.txt Rohit Dube
- Re: Comments on draft-katz-yeung-traffic-08.txt Sina Mirtorabi
- Re: Comments on draft-katz-yeung-traffic-08.txt Rohit Dube
- Re: Comments on draft-katz-yeung-traffic-08.txt Li, Ke Qin (Peter)
- Re: Comments on draft-katz-yeung-traffic-08.txt Sina Mirtorabi
- Re: Comments on draft-katz-yeung-traffic-08.txt Rohit Dube
- Re: Comments on draft-katz-yeung-traffic-08.txt Naidu, Venkata
- Re: Comments on draft-katz-yeung-traffic-08.txt Acee Lindem
- Re: Comments on draft-katz-yeung-traffic-08.txt Kireeti Kompella
- Re: Comments on draft-katz-yeung-traffic-08.txt Acee Lindem
- Re: Comments on draft-katz-yeung-traffic-08.txt Kireeti Kompella
- Re: Comments on draft-katz-yeung-traffic-08.txt Acee Lindem
- Re: Comments on draft-katz-yeung-traffic-08.txt Don Goodspeed
- Re: Comments on draft-katz-yeung-traffic-08.txt Tom Petch
- Re: Comments on draft-katz-yeung-traffic-08.txt Acee Lindem
- Re: Comments on draft-katz-yeung-traffic-08.txt Tom Petch
- Re: Comments on draft-katz-yeung-traffic-08.txt Acee Lindem
- Re: OSPFv3 Applications Support Rohit Dube
- Re: OSPFv3 Applications Support Quaizar Vohra
- Re: OSPFv3 Applications Support Acee Lindem
- Re: OSPFv3 Applications Support Erblichs
- Re: OSPFv3 Applications Support Kunihiro Ishiguro
- Re: OSPFv3 Applications Support Kireeti Kompella
- Re: OSPFv3 Applications Support Acee Lindem
- Re: I-D ACTION:draft-katz-yeung-ospf-traffic-10.t… Rohit Dube