Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt
"Sastry, Ravi" <rsastry@SONUSNET.COM> Mon, 10 November 2003 21:12 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 QAA13796 for <ospf-archive@LISTS.IETF.ORG>; Mon, 10 Nov 2003 16:12:00 -0500 (EST)
Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <13.00C3F819@cherry.ease.lsoft.com>; Mon, 10 Nov 2003 16:12:11 -0500
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 60066629 for OSPF@PEACH.EASE.LSOFT.COM; Mon, 10 Nov 2003 16:12:10 -0500
Received: from 208.45.178.33 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Mon, 10 Nov 2003 16:12:10 -0400
Received: from sonusms1.sonusnet.com (sonusms1 [10.128.32.93]) by revere.sonusnet.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hAALC9lf002033 for <OSPF@peach.ease.lsoft.com>; Mon, 10 Nov 2003 16:12:09 -0500 (EST)
Received: from sonusdc3.sonusnet.com (unverified) by sonusms1.sonusnet.com (Content Technologies SMTPRS 4.3.10) with ESMTP id <T65d2d2b9fd0a80205d5b8@sonusms1.sonusnet.com> for <OSPF@peach.ease.lsoft.com>; Mon, 10 Nov 2003 16:12:02 -0500
Received: by sonusdc3.sonusnet.com with Internet Mail Service (5.5.2653.19) id <WDVTWG2S>; Mon, 10 Nov 2003 16:12:02 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID: <8A2FD2AE4BFC974481522E9D7943DCCB3246D5@sonusdc3.sonusnet.com>
Date: Mon, 10 Nov 2003 16:12:01 -0500
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: "Sastry, Ravi" <rsastry@SONUSNET.COM>
Subject: Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Any MTU issues especially when there are large number of tunnels? Just wondering.. ravi/ > -----Original Message----- > From: Sandy Eng [mailto:swkeng@CISCO.COM] > Sent: Monday, November 10, 2003 3:58 PM > To: OSPF@PEACH.EASE.LSOFT.COM > Subject: Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt > > > Rahul, > > Rahul Aggarwal wrote: > > Following up on this thread, I have the following concerns with this > > document: > > > > 1. Tunnels are used both intra and inter domains. Thus tunnel > > capabilities have to be propagated across domains as well. > Hence IGP is > > imho not appropriate for this application. > > > > 2. Tunnel capabilities are not used by core routeres. > > As we are announcing specific router capabilities, it therefore infers > that only certain routers in the network are capable of some specific > capabilities. If all routers in a network have the same capability, > there is then no need for specific announcement. > > Thanks, > Sandy > > > > > > > 3. There are existing documents that specify the use of BGP > for this: > > draft-raggarwa-ppvpn-tunnel-encap-sig-01.txt > > draft-nalawade-kapoor-tunnel-safi-01.txt > > > > Hence imho OSPF WG should not take on this work. > > > > Thanks, > > rahul > > > > On Tue, 28 Oct 2003, Robert Raszuk wrote: > > > > > >>Acee, > >> > >> > >>> My biggest fear would be that if this draft is accepted it > >>> would only be the first of a torrent of auto-configuration > >>> drafts. > >> > >>Second one not first ;). Notice this one submitted a while back: > >>draft-raszuk-ospf-bgp-peer-discovery-00.txt > >> > >> > 1. Should OSPF be used for tunnel auto-configuration? > >> > >>I think in general this requires a study on a case by case > basis. Most > >>important factors which should be taken into consideration are: > >> > >>*A* How frequently the information advertised changed - is it static > >>configuration or dynamic in nature which triggers reflooding ? > >> > >>*B* Is the application which the uses delivered information > limited to > >>IGP domain or crosses domains ? > >> > >>*C* What is the amount of information to be flooded (keeping in mind > >>that majority of P routers - those in the core - will never use it. > >> > >>*D* What are the alternatives available & _deployed_ today > to deliver > >>the same information to it's users > >> > >>*E* How often area wide flooding will be sufficient versus > domain wide. > >> > >>Coming back to draft-eng-nalawade-ospf-tunnel-cap-00.txt I see the > >>following: > >> > >>Reg A: Info is essentially static except the L2TPv3 cookie rollover > >>intervals which if implementation permits could be changing > periodically > >> > >>Reg B: I think that in any application of tunnels we can't limit the > >>scope of use to one IGP domain. There can be a lot of > customers who may > >>never need to go over a domain (which this draft is > targeting though). > >> > >>Reg C: Minimal (comparing to TE at least :):). > >> > >>Reg D: It is worth noting that there is a few drafts in IDR > describing > >>the ideas for the same information distribution > >> > >>Reg E: Looking at the most common OSPF topologies I would > say that most > >>tunnels will be build between edge PEs and those in a lot > of cases are > >>located in it's own POP areas. Not to say that there are no > customers > >>who keep most of their PEs on the edges of area 0. > >> > >>Rgs, > >>R. > >> > > >
- draft-eng-nalawade-ospf-tunnel-cap-00.txt Acee Lindem
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Sandy Eng
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Gargi Nalawade
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Robert Raszuk
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Rahul Aggarwal
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Gargi Nalawade
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Sandy Eng
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Sastry, Ravi
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Sandy Eng
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Rahul Aggarwal
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Rahul Aggarwal
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Gargi Nalawade
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Sandy Eng
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Robert Raszuk
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Rahul Aggarwal
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Gargi Nalawade
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Gargi Nalawade
- draft-eng-nalawade-ospf-tunnel-cap-00.txt Yakov Rekhter
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Yakov Rekhter
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Robert Raszuk
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Yakov Rekhter
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Robert Raszuk
- Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt Yakov Rekhter