From exim@www1.ietf.org Fri Dec 5 00:59:19 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07590 for ; Fri, 5 Dec 2003 00:59:19 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AS8zZ-0002u3-A4 for l3vpn-archive@odin.ietf.org; Fri, 05 Dec 2003 00:59:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hB55x5NO011153 for l3vpn-archive@odin.ietf.org; Fri, 5 Dec 2003 00:59:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AS8zZ-0002to-4I for l3vpn-web-archive@optimus.ietf.org; Fri, 05 Dec 2003 00:59:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07587 for ; Fri, 5 Dec 2003 00:58:48 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AS8zW-0002IL-00 for l3vpn-web-archive@ietf.org; Fri, 05 Dec 2003 00:59:02 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AS8zW-0002IH-00 for l3vpn-web-archive@ietf.org; Fri, 05 Dec 2003 00:59:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AS8zV-0002sw-6S; Fri, 05 Dec 2003 00:59:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AS8yX-0002rn-Ja for l3vpn@optimus.ietf.org; Fri, 05 Dec 2003 00:58:01 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07555 for ; Fri, 5 Dec 2003 00:57:44 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AS8yU-0002HT-00 for l3vpn@ietf.org; Fri, 05 Dec 2003 00:57:58 -0500 Received: from www3.mail.lycos.com ([209.202.220.160] helo=lycos.com) by ietf-mx with smtp (Exim 4.12) id 1AS8yU-0002HF-00 for l3vpn@ietf.org; Fri, 05 Dec 2003 00:57:58 -0500 Received: from Unknown/Local ([?.?.?.?]) by mailcity.com; Fri, 05 Dec 2003 05:57:20 -0000 To: l3vpn@ietf.org Date: Fri, 05 Dec 2003 11:27:20 +0530 From: "prem chand" Message-ID: Mime-Version: 1.0 X-Sent-Mail: off Reply-To: premac@lycos.com X-Mailer: MailCity Service X-Priority: 3 Subject: VPNv4 Route Aggregation X-Sender-Ip: 203.197.138.199 Organization: Lycos Mail (http://www.mail.lycos.com:80) Content-Type: text/plain; charset=us-ascii Content-Language: en Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: l3vpn-admin@ietf.org Errors-To: l3vpn-admin@ietf.org X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Is any vendor supporting VPNv4 route aggregation? If so, is the aggregation policy done for per VRF, or will it be a global configuration? Thanx in Advance, PREM ____________________________________________________________ Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail! http://login.mail.lycos.com/r/referral?aid=27005 From exim@www1.ietf.org Wed Dec 10 21:51:51 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01700 for ; Wed, 10 Dec 2003 21:51:51 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUGvE-0004dq-LO for l3vpn-archive@odin.ietf.org; Wed, 10 Dec 2003 21:51:24 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBB2pOgb017836 for l3vpn-archive@odin.ietf.org; Wed, 10 Dec 2003 21:51:24 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUGvE-0004db-EP for l3vpn-web-archive@optimus.ietf.org; Wed, 10 Dec 2003 21:51:24 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01670 for ; Wed, 10 Dec 2003 21:51:20 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUGuy-0000eP-00 for l3vpn-web-archive@ietf.org; Wed, 10 Dec 2003 21:51:08 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AUGuy-0000eL-00 for l3vpn-web-archive@ietf.org; Wed, 10 Dec 2003 21:51:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUGus-0004UL-F8; Wed, 10 Dec 2003 21:51:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUGuO-0004Tl-Ci for l3vpn@optimus.ietf.org; Wed, 10 Dec 2003 21:50:32 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01659 for ; Wed, 10 Dec 2003 21:50:28 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUGuK-0000ax-00 for l3vpn@ietf.org; Wed, 10 Dec 2003 21:50:28 -0500 Received: from smtp806.mail.sc5.yahoo.com ([66.163.168.185]) by ietf-mx with smtp (Exim 4.12) id 1AUGuK-0000at-00 for l3vpn@ietf.org; Wed, 10 Dec 2003 21:50:28 -0500 Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.16.104 with login) by smtp806.mail.sc5.yahoo.com with SMTP; 11 Dec 2003 02:50:28 -0000 Message-ID: <034f01c3bf91$8823b330$681067c0@adithya> From: "Mohan Parthasarathy" To: Subject: Question on draft-ietf-l3vpn-ipsec-2547-01.txt Date: Wed, 10 Dec 2003 18:50:26 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Transfer-Encoding: 7bit Sender: l3vpn-admin@ietf.org Errors-To: l3vpn-admin@ietf.org X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello, In section 2.6, it says that one IPsec SA between the PEs would be sufficient for "N" VPNs. If you have just one IP-IP transport mode SA, how would the VPN demuxing work ? Asssume i am having overlapping addresses in the VPNs. After decrypting the packet, how do i know which VPN routing instance to lookup the route ? I thought SPI was one of the demuxing fields which means you have to have at least one SA per VPN. What am i missing ? -thanks mohan From exim@www1.ietf.org Thu Dec 11 04:33:41 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23380 for ; Thu, 11 Dec 2003 04:33:41 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUNC5-0003U9-6z for l3vpn-archive@odin.ietf.org; Thu, 11 Dec 2003 04:33:13 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBB9XDrE013394 for l3vpn-archive@odin.ietf.org; Thu, 11 Dec 2003 04:33:13 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUNC0-0003Tw-Th for l3vpn-web-archive@optimus.ietf.org; Thu, 11 Dec 2003 04:33:08 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23374 for ; Thu, 11 Dec 2003 04:33:06 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUNBx-0006bZ-00 for l3vpn-web-archive@ietf.org; Thu, 11 Dec 2003 04:33:05 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AUNBw-0006bW-00 for l3vpn-web-archive@ietf.org; Thu, 11 Dec 2003 04:33:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUNBu-0003TF-Ne; Thu, 11 Dec 2003 04:33:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUNAu-0003S7-RM for l3vpn@optimus.ietf.org; Thu, 11 Dec 2003 04:32:00 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23337 for ; Thu, 11 Dec 2003 04:31:57 -0500 (EST) From: jeremy.de_clercq@alcatel.be Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUNAr-0006aG-00 for l3vpn@ietf.org; Thu, 11 Dec 2003 04:31:57 -0500 Received: from colt-na165.alcatel.fr ([62.23.212.165] helo=smail.alcatel.fr) by ietf-mx with esmtp (Exim 4.12) id 1AUNAq-0006aC-00 for l3vpn@ietf.org; Thu, 11 Dec 2003 04:31:56 -0500 Received: from bemail04.netfr.alcatel.fr (bemail04.netfr.alcatel.fr [155.132.251.33]) by smail.alcatel.fr (ALCANET/NETFR) with ESMTP id hBB9VgZq027052; Thu, 11 Dec 2003 10:31:42 +0100 Received: from alcatel.be ([138.203.140.3]) by bemail04.netfr.alcatel.fr (Lotus Domino Release 5.0.11) with ESMTP id 2003121110314098:2794 ; Thu, 11 Dec 2003 10:31:40 +0100 Message-ID: <3FD83973.5E358FFF@alcatel.be> Date: Thu, 11 Dec 2003 10:31:32 +0100 Organization: Alcatel X-Mailer: Mozilla 4.72 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Mohan Parthasarathy CC: l3vpn@ietf.org Subject: Re: Question on draft-ietf-l3vpn-ipsec-2547-01.txt References: <034f01c3bf91$8823b330$681067c0@adithya> X-MIMETrack: Itemize by SMTP Server on BEMAIL04/BE/ALCATEL(Release 5.0.11 |July 24, 2002) at 12/11/2003 10:31:41, Serialize by Router on BEMAIL04/BE/ALCATEL(Release 5.0.11 |July 24, 2002) at 12/11/2003 10:31:42, Serialize complete at 12/11/2003 10:31:42 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-Alcanet-MTA-scanned-and-authorized: yes Content-Transfer-Encoding: 7bit Sender: l3vpn-admin@ietf.org Errors-To: l3vpn-admin@ietf.org X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Mohan, section 2.4 of the draft explains that packets are MPLS-in-IP/GRE encapsulated before IPsec handling. The MPLS label is used as the VPN demux field. So you'll have one SA per PE-PE pair in which you can mux the different VPNs using MPLS labels (that are distributed via BGP just like in 2547). cheers, Jeremy. Mohan Parthasarathy wrote: > > Hello, > > In section 2.6, it says that one IPsec SA between the PEs would be > sufficient for "N" VPNs. > If you have just one IP-IP transport mode SA, how would the VPN demuxing > work ? > Asssume i am having overlapping addresses in the VPNs. After decrypting the > packet, > how do i know which VPN routing instance to lookup the route ? I thought SPI > was > one of the demuxing fields which means you have to have at least one SA per > VPN. > What am i missing ? > > -thanks > mohan From exim@www1.ietf.org Thu Dec 11 13:12:32 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12387 for ; Thu, 11 Dec 2003 13:12:32 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUVIE-0000dF-1H for l3vpn-archive@odin.ietf.org; Thu, 11 Dec 2003 13:12:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBBIC5Go002426 for l3vpn-archive@odin.ietf.org; Thu, 11 Dec 2003 13:12:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUVID-0000d3-Pi for l3vpn-web-archive@optimus.ietf.org; Thu, 11 Dec 2003 13:12:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12374 for ; Thu, 11 Dec 2003 13:12:01 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUVIB-0002nD-00 for l3vpn-web-archive@ietf.org; Thu, 11 Dec 2003 13:12:04 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AUVIB-0002nA-00 for l3vpn-web-archive@ietf.org; Thu, 11 Dec 2003 13:12:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUVIA-0000cP-4D; Thu, 11 Dec 2003 13:12:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUVHL-0000bA-7f for l3vpn@optimus.ietf.org; Thu, 11 Dec 2003 13:11:11 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12344 for ; Thu, 11 Dec 2003 13:11:07 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUVHJ-0002mT-00 for l3vpn@ietf.org; Thu, 11 Dec 2003 13:11:09 -0500 Received: from smtp812.mail.sc5.yahoo.com ([66.163.170.82]) by ietf-mx with smtp (Exim 4.12) id 1AUVHI-0002mP-00 for l3vpn@ietf.org; Thu, 11 Dec 2003 13:11:08 -0500 Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.16.104 with login) by smtp812.mail.sc5.yahoo.com with SMTP; 11 Dec 2003 18:11:07 -0000 Message-ID: <002701c3c012$257e62d0$681067c0@adithya> From: "Mohan Parthasarathy" To: Cc: References: <034f01c3bf91$8823b330$681067c0@adithya> <3FD83973.5E358FFF@alcatel.be> Subject: Re: Question on draft-ietf-l3vpn-ipsec-2547-01.txt Date: Thu, 11 Dec 2003 10:11:06 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Transfer-Encoding: 7bit Sender: l3vpn-admin@ietf.org Errors-To: l3vpn-admin@ietf.org X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit > Hi Mohan, > > section 2.4 of the draft explains that packets are MPLS-in-IP/GRE > encapsulated before IPsec handling. The MPLS label is used as the VPN > demux field. So you'll have one SA per PE-PE pair in which you can mux > the different VPNs using MPLS labels (that are distributed via BGP just > like in 2547). > I don't think this is explicitly mentioned in the draft and it might be good to clarify it thought it may be obvious for some. thanks mohan > cheers, > Jeremy. > > Mohan Parthasarathy wrote: > > > > Hello, > > > > In section 2.6, it says that one IPsec SA between the PEs would be > > sufficient for "N" VPNs. > > If you have just one IP-IP transport mode SA, how would the VPN demuxing > > work ? > > Asssume i am having overlapping addresses in the VPNs. After decrypting the > > packet, > > how do i know which VPN routing instance to lookup the route ? I thought SPI > > was > > one of the demuxing fields which means you have to have at least one SA per > > VPN. > > What am i missing ? > > > > -thanks > > mohan From exim@www1.ietf.org Fri Dec 12 01:29:37 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA13798 for ; Fri, 12 Dec 2003 01:29:37 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUgnU-0000aK-Mm for l3vpn-archive@odin.ietf.org; Fri, 12 Dec 2003 01:29:09 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBC6T89p002242 for l3vpn-archive@odin.ietf.org; Fri, 12 Dec 2003 01:29:08 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUgnU-0000a5-HO for l3vpn-web-archive@optimus.ietf.org; Fri, 12 Dec 2003 01:29:08 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA13795 for ; Fri, 12 Dec 2003 01:29:06 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUgnR-0004jG-00 for l3vpn-web-archive@ietf.org; Fri, 12 Dec 2003 01:29:05 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AUgnR-0004jC-00 for l3vpn-web-archive@ietf.org; Fri, 12 Dec 2003 01:29:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUgnN-0000ZS-8f; Fri, 12 Dec 2003 01:29:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUgn3-0000Yl-U0 for l3vpn@optimus.ietf.org; Fri, 12 Dec 2003 01:28:42 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA13759 for ; Fri, 12 Dec 2003 01:28:39 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUgn0-0004iY-00 for l3vpn@ietf.org; Fri, 12 Dec 2003 01:28:38 -0500 Received: from www1.mail.lycos.com ([209.202.220.140] helo=lycos.com) by ietf-mx with smtp (Exim 4.12) id 1AUgmz-0004hz-00 for l3vpn@ietf.org; Fri, 12 Dec 2003 01:28:38 -0500 Received: from Unknown/Local ([?.?.?.?]) by mailcity.com; Fri, 12 Dec 2003 06:27:53 -0000 To: l3vpn@ietf.org Date: Fri, 12 Dec 2003 01:27:53 -0500 From: "Prem Chand" Message-ID: Mime-Version: 1.0 Cc: isp-bgp@isp-bgp.com X-Sent-Mail: off Reply-To: premac@lycos.com X-Mailer: MailCity Service X-Priority: 3 Subject: (No Subject) X-Sender-Ip: 203.197.138.199 Organization: Lycos Mail (http://www.mail.lycos.com:80) Content-Type: text/plain; charset=us-ascii Content-Language: en Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: l3vpn-admin@ietf.org Errors-To: l3vpn-admin@ietf.org X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi i m giving sample VPN-IPv4 update message below. ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 00 5b 02 00 00 00 44 40 01 01 02 40 02 00 80 04 04 00 00 00 00 40 05 04 00 00 00 64 c0 10 08 00 02 00 03 00 00 00 03 80 0e 21 00 01 80 0c 00 00 00 00 00 00 00 00 0a 0d 01 3e 00 76 00 01 71 00 00 00 01 00 00 00 01 c8 01 3e 04 Here, the total length = 0x5b = 91bytes Withdrawn Length = 0x00 = 0 bytes Path Attributes Length = 0x0044 = 68 bytes MP_REACH_NLRI -- length = 0x21 = 33bytes = <1, 128> Nexthop Length = 0x0c = 12bytes Nexthop = 0:10.13.1.62 Prefix+label length in bits = 0x76 = 118. Label = 0x000171 Prefix -- RD=0x0000000100000001 IPv4 route = 200.1.62.4 This prefix+lable length in bits '118' is not divisible by 8 (i.e doent fall under octet boundary length). Can it be like this? or is it erroneous packet? Label (3 octets) + RD (8 octets) + IPv4 prefix (4 octets) = 15 octets = 120 in bits. How it matches with 118??? Regards, PREM ____________________________________________________________ Free Poetry Contest. Win $10,000. Submit your poem @ Poetry.com! http://ad.doubleclick.net/clk;6750922;3807821;l?http://www.poetry.com/contest/contest.asp?Suite=A59101 From exim@www1.ietf.org Fri Dec 12 01:50:32 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA14670 for ; Fri, 12 Dec 2003 01:50:32 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUh7k-0001ex-3d for l3vpn-archive@odin.ietf.org; Fri, 12 Dec 2003 01:50:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBC6o4pZ006378 for l3vpn-archive@odin.ietf.org; Fri, 12 Dec 2003 01:50:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUh7j-0001en-Ty for l3vpn-web-archive@optimus.ietf.org; Fri, 12 Dec 2003 01:50:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA14655 for ; Fri, 12 Dec 2003 01:50:01 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUh7g-0005Dq-00 for l3vpn-web-archive@ietf.org; Fri, 12 Dec 2003 01:50:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AUh7g-0005Dn-00 for l3vpn-web-archive@ietf.org; Fri, 12 Dec 2003 01:50:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUh7h-0001dr-49; Fri, 12 Dec 2003 01:50:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUh7G-0001dD-EC for l3vpn@optimus.ietf.org; Fri, 12 Dec 2003 01:49:34 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA14649 for ; Fri, 12 Dec 2003 01:49:31 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUh7D-0005De-00 for l3vpn@ietf.org; Fri, 12 Dec 2003 01:49:31 -0500 Received: from [65.246.255.50] (helo=manatick) by ietf-mx with esmtp (Exim 4.12) id 1AUh7C-0005Db-00 for l3vpn@ietf.org; Fri, 12 Dec 2003 01:49:30 -0500 Received: from prattle.redback.com ([155.53.12.9]) by manatick with esmtp (Exim 4.24) id 1AUh7E-00017t-FB for l3vpn@ietf.org; Fri, 12 Dec 2003 01:49:32 -0500 Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id 110207D412E; Thu, 11 Dec 2003 22:49:00 -0800 (PST) Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24021-10; Thu, 11 Dec 2003 22:48:59 -0800 (PST) Received: from popserv2.redback.com (popserv2.redback.com [155.53.12.59]) by prattle.redback.com (Postfix) with ESMTP id 8F92A7D4126; Thu, 11 Dec 2003 22:48:59 -0800 (PST) Received: from redback.com (fall.redback.com [155.53.44.81]) by popserv2.redback.com (Postfix) with ESMTP id C8233979C5; Thu, 11 Dec 2003 22:48:58 -0800 (PST) To: premac@lycos.com Cc: l3vpn@ietf.org, isp-bgp@isp-bgp.com Subject: Re: (No Subject) In-Reply-To: Message from "Prem Chand" of "Fri, 12 Dec 2003 01:27:53 EST." Date: Thu, 11 Dec 2003 22:48:58 -0800 From: Enke Chen Message-Id: <20031212064858.C8233979C5@popserv2.redback.com> X-Virus-Scanned: by amavisd-new at redback.com Sender: l3vpn-admin@ietf.org Errors-To: l3vpn-admin@ietf.org X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , The prefix length is /30 (and not /32) in this case. -- Enke > To: l3vpn@ietf.org > Date: Fri, 12 Dec 2003 01:27:53 -0500 > From: "Prem Chand" > Message-ID: > Mime-Version: 1.0 > Cc: isp-bgp@isp-bgp.com > > Hi i m giving sample VPN-IPv4 update message below. > > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > 00 5b 02 00 00 00 44 40 01 01 02 40 02 00 80 04 > 04 00 00 00 00 40 05 04 00 00 00 64 c0 10 08 00 > 02 00 03 00 00 00 03 80 0e 21 00 01 80 0c 00 00 > 00 00 00 00 00 00 0a 0d 01 3e 00 76 00 01 71 00 > 00 00 01 00 00 00 01 c8 01 3e 04 > > Here, the total length = 0x5b = 91bytes > Withdrawn Length = 0x00 = 0 bytes > Path Attributes Length = 0x0044 = 68 bytes > > MP_REACH_NLRI -- length = 0x21 = 33bytes > = <1, 128> > Nexthop Length = 0x0c = 12bytes > Nexthop = 0:10.13.1.62 > Prefix+label length in bits = 0x76 = 118. > Label = 0x000171 > Prefix -- RD=0x0000000100000001 IPv4 route = 200.1.62.4 > > This prefix+lable length in bits '118' is not divisible by 8 (i.e doent fall under octet boundary length). Can it be like this? or is it erroneous packet? > > Label (3 octets) + RD (8 octets) + IPv4 prefix (4 octets) = 15 octets = 120 in bits. How it matches with 118??? > > Regards, > PREM > > > > > ____________________________________________________________ > Free Poetry Contest. Win $10,000. Submit your poem @ Poetry.com! > http://ad.doubleclick.net/clk;6750922;3807821;l?http://www.poetry.com/contest/contest.asp?Suite=A59101 > From exim@www1.ietf.org Fri Dec 12 11:51:35 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15965 for ; Fri, 12 Dec 2003 11:51:35 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUqVQ-00038b-7v for l3vpn-archive@odin.ietf.org; Fri, 12 Dec 2003 11:51:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBCGp8tm012057 for l3vpn-archive@odin.ietf.org; Fri, 12 Dec 2003 11:51:08 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUqVQ-00038O-2g for l3vpn-web-archive@optimus.ietf.org; Fri, 12 Dec 2003 11:51:08 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15939 for ; Fri, 12 Dec 2003 11:51:04 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUqVO-0001Ae-00 for l3vpn-web-archive@ietf.org; Fri, 12 Dec 2003 11:51:07 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AUqVO-0001Ab-00 for l3vpn-web-archive@ietf.org; Fri, 12 Dec 2003 11:51:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUqVJ-00037a-To; Fri, 12 Dec 2003 11:51:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUqV4-00037K-1e for l3vpn@optimus.ietf.org; Fri, 12 Dec 2003 11:50:46 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15932 for ; Fri, 12 Dec 2003 11:50:42 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUqV2-0001AS-00 for l3vpn@ietf.org; Fri, 12 Dec 2003 11:50:45 -0500 Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx with esmtp (Exim 4.12) id 1AUqV2-00018N-00 for l3vpn@ietf.org; Fri, 12 Dec 2003 11:50:44 -0500 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id hBCGoDBm080028; Fri, 12 Dec 2003 08:50:13 -0800 (PST) (envelope-from rcallon@juniper.net) Received: from rcallon-lt.juniper.net (securepptp096.static.jnpr.net [172.24.253.96]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id hBCGoCX58028; Fri, 12 Dec 2003 08:50:12 -0800 (PST) (envelope-from rcallon@juniper.net) Message-Id: <4.3.2.20031212114754.030d6d20@zircon.juniper.net> X-Sender: rcallon@zircon.juniper.net X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Fri, 12 Dec 2003 11:48:50 -0500 To: l3vpn@ietf.org From: Ross Callon Subject: Re: Extended last call draft-ietf-l3vpn-ospf-2547-00.txt Cc: acee@redback.com, rohit@utstar.com In-Reply-To: <4.3.2.20031111103244.02cc8ce0@zircon.juniper.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: l3vpn-admin@ietf.org Errors-To: l3vpn-admin@ietf.org X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , The last call on draft-ietf-l3vpn-ospf-2547-00.txt has ended successfully, and the document will be forwarded to the IESG for their review. thanks, Ross At 10:37 AM 11/11/2003 -0500, Ross Callon wrote: >The last call deadline on draft-ietf-l3vpn-ospf-2547-00.txt >is extended to 11/21/2003 5PM Eastern. > >This is partly due to the IETF (people are pretty busy this >week), and partly to correspond to the last call on the >companion document draft-ietf-ospf-2547-dnbit-01.txt >whose last call in the OSPF working group has also been >extended to 11/21/2003. > >thanks, Ross > > > >Date: Tue, 28 Oct 2003 08:57:53 -0500 > >To: l3vpn@ietf.org, ospf@peach.ease.lsoft.com > >From: Ross Callon > >Subject: last call draft-ietf-l3vpn-ospf-2547-00.txt > >Sender: l3vpn-admin@ietf.org > > > >This begins the working group last call on: > > > > OSPF as the PE/CE Protocol in BGP/MPLS VPNs > > draft-ietf-l3vpn-ospf-2547-00.txt > > > >While this document is an l3vpn working group document, > >the last call will take place on both the l3vpn and ospf working > >group mailing lists. The last call will terminate at the end of the > >day on Friday November 14th. > > > >Thanks, Ross > > > From exim@www1.ietf.org Mon Dec 22 07:24:35 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12382 for ; Mon, 22 Dec 2003 07:24:35 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYP6U-0006t5-1y for l3vpn-archive@odin.ietf.org; Mon, 22 Dec 2003 07:24:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBMCO6PW026469 for l3vpn-archive@odin.ietf.org; Mon, 22 Dec 2003 07:24:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYP6T-0006sq-RJ for l3vpn-web-archive@optimus.ietf.org; Mon, 22 Dec 2003 07:24:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12378 for ; Mon, 22 Dec 2003 07:24:04 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYP6T-0007NC-00 for l3vpn-web-archive@ietf.org; Mon, 22 Dec 2003 07:24:05 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYP6S-0007N4-00 for l3vpn-web-archive@ietf.org; Mon, 22 Dec 2003 07:24:04 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AYP6S-0007N1-00 for l3vpn-web-archive@ietf.org; Mon, 22 Dec 2003 07:24:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYP6P-0006sE-C5; Mon, 22 Dec 2003 07:24:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYP6M-0006ry-A4 for l3vpn@optimus.ietf.org; Mon, 22 Dec 2003 07:23:58 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12371 for ; Mon, 22 Dec 2003 07:23:56 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYP6L-0007My-00 for l3vpn@ietf.org; Mon, 22 Dec 2003 07:23:57 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYP6K-0007Mr-00 for l3vpn@ietf.org; Mon, 22 Dec 2003 07:23:57 -0500 Received: from ams-iport-1.cisco.com ([144.254.74.5]) by ietf-mx with esmtp (Exim 4.12) id 1AYP6K-0007MN-00 for l3vpn@ietf.org; Mon, 22 Dec 2003 07:23:56 -0500 Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 22 Dec 2003 13:24:19 +0100 Received: from cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id hBMCN8FF024808 for ; Mon, 22 Dec 2003 13:23:09 +0100 (MET) Received: from MBEHRING-W2K1.cisco.com (dhcp-mad-wer4-vl1264-103-20-177.cisco.com [64.103.20.177]) by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id NAA27832 for ; Mon, 22 Dec 2003 13:23:23 +0100 (MET) Message-Id: <4.3.2.7.2.20031222131536.05686e00@madrid.cisco.com> X-Sender: mbehring@madrid.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 22 Dec 2003 13:23:38 +0100 To: l3vpn@ietf.org From: "Michael H. Behringer" Subject: Last comments on draft-behringer-mpls-security Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: l3vpn-admin@ietf.org Errors-To: l3vpn-admin@ietf.org X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 All, This document has been around for a long time, and I think it's getting ready for submission. I'm planning to submit this to the IESG to be considered for an informational RFC. Before I do that, I would like to ask you to please have a final look at the doc, and send me your comments. I will do version -06 with all the comments received by 12 Jan 2004, and submit that to the IESG (unless of course there are major changes necessary). http://www.ietf.org/internet-drafts/draft-behringer-mpls-security-05.txt Thanks in advance, and happy festive days to everyone. Michael From exim@www1.ietf.org Mon Dec 29 05:36:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23613 for ; Mon, 29 Dec 2003 05:36:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aauke-0005od-42 for l3vpn-archive@odin.ietf.org; Mon, 29 Dec 2003 05:35:56 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBTAZur5022355 for l3vpn-archive@odin.ietf.org; Mon, 29 Dec 2003 05:35:56 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aaukd-0005oU-Kb for l3vpn-web-archive@optimus.ietf.org; Mon, 29 Dec 2003 05:35:55 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23593 for ; Mon, 29 Dec 2003 05:35:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aauka-0001Mf-00 for l3vpn-web-archive@ietf.org; Mon, 29 Dec 2003 05:35:52 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aauip-0001Id-00 for l3vpn-web-archive@ietf.org; Mon, 29 Dec 2003 05:34:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1Aaugt-0001FA-00 for l3vpn-web-archive@ietf.org; Mon, 29 Dec 2003 05:32:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aaugq-0005fy-Oj; Mon, 29 Dec 2003 05:32:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aaugf-0005fg-Dj for l3vpn@optimus.ietf.org; Mon, 29 Dec 2003 05:31:49 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23459 for ; Mon, 29 Dec 2003 05:31:45 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aaugb-0001By-00 for l3vpn@ietf.org; Mon, 29 Dec 2003 05:31:46 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aauef-00017p-00 for l3vpn@ietf.org; Mon, 29 Dec 2003 05:29:46 -0500 Received: from [203.197.140.35] (helo=fsnt.future.futsoft.com) by ietf-mx with esmtp (Exim 4.12) id 1Aauck-00012z-00 for l3vpn@ietf.org; Mon, 29 Dec 2003 05:27:47 -0500 Received: from kailash.future.futsoft.com (unverified [203.197.140.36]) by fsnt.future.futsoft.com (Content Technologies SMTPRS 4.3.6) with ESMTP id ; Mon, 29 Dec 2003 16:02:11 +0530 Received: from sakthivss (sakthivss.future.futsoft.com [10.6.4.130]) by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id hBTALoU03145; Mon , 29 Dec 2003 15:51:50 +0530 Reply-To: From: "Sakthivadivu.S.S" To: Cc: Subject: Hub and Spoke vpn topology Date: Mon, 29 Dec 2003 15:56:27 +0530 Message-ID: <000e01c3cdf6$38807f20$8204060a@future.futsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: <3FE05A58.1040507@cisco.com> Content-Transfer-Encoding: 7bit Sender: l3vpn-admin@ietf.org Errors-To: l3vpn-admin@ietf.org X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=EXCUSE_16 autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, Can you pls tell me how do you configure Hub and Spoke topology in Cisco?.I am not able to find any example for this? I found that juniper uses two interfaces between Hub PE and Hub CE?. Can't we manage with one interface?. Can u pls give me some inputs? Regards, Sakthi *************************************************************************** This message is proprietary to Future Software Limited (FSL) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSL accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. *************************************************************************** From exim@www1.ietf.org Tue Dec 30 20:23:00 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22702 for ; Tue, 30 Dec 2003 20:23:00 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AbV4B-0006Om-6Z for l3vpn-archive@odin.ietf.org; Tue, 30 Dec 2003 20:22:31 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBV1MV5J024593 for l3vpn-archive@odin.ietf.org; Tue, 30 Dec 2003 20:22:31 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AbV4B-0006Oa-1N for l3vpn-web-archive@optimus.ietf.org; Tue, 30 Dec 2003 20:22:31 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22683 for ; Tue, 30 Dec 2003 20:22:29 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AbV48-00025W-00 for l3vpn-web-archive@ietf.org; Tue, 30 Dec 2003 20:22:29 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AbV2H-00022u-00 for l3vpn-web-archive@ietf.org; Tue, 30 Dec 2003 20:20:34 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AbV0p-00020x-00 for l3vpn-web-archive@ietf.org; Tue, 30 Dec 2003 20:19:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AbV0n-0006Hp-2H; Tue, 30 Dec 2003 20:19:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AbV0I-0006HO-1N for l3vpn@optimus.ietf.org; Tue, 30 Dec 2003 20:18:30 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22638 for ; Tue, 30 Dec 2003 20:18:28 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AbV0F-0001zW-00 for l3vpn@ietf.org; Tue, 30 Dec 2003 20:18:28 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AbUyN-0001yX-00 for l3vpn@ietf.org; Tue, 30 Dec 2003 20:16:31 -0500 Received: from smtp103.mail.sc5.yahoo.com ([66.163.169.222]) by ietf-mx with smtp (Exim 4.12) id 1AbUxv-0001xH-00 for l3vpn@ietf.org; Tue, 30 Dec 2003 20:16:03 -0500 Received: from unknown (HELO RAKHILAPTOP) (vsharma87@67.117.150.103 with login) by smtp103.mail.sc5.yahoo.com with SMTP; 31 Dec 2003 01:16:03 -0000 From: "Vishal Sharma" To: "L3PPVPN" Subject: Clarification on the L3 framework draft Date: Tue, 30 Dec 2003 17:15:55 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" 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) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Transfer-Encoding: 7bit Sender: l3vpn-admin@ietf.org Errors-To: l3vpn-admin@ietf.org X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Folks, I have the following question, and would appreciate someone clarifying it. On pp. 54, Sec. 4.4.4, the document states that using BGP's route reflectors, PE-PE adjacencies can be completely eliminated, and furthermore that the no. of backbone adjacencies can be made a small constant _independent_ of the number of PEs involved. I figure even if one is using RR's, each PE device would have to have an adjacency to one (typcially two) RRs, so the total adjacencies in the system or on any one RR will be a function of the number of PEs? Or, is the statement talking merely of the adjacencies between the RRs themselves, which I suppose would be independent of the number of PEs, or of the adjacencies on a given PE, which also would be a constant in this case. Any insights would be very helpful. Thanks, -Vishal **************************************************************** Dr. Vishal Sharma Metanoia, Inc. 1600 Villa Street, Unit 352 Mountain View, CA 94041-1174 Phone: +1 408-530-8313. Cell: +1 408-394-6321 Email: v.sharma@ieee.org. http://www.metanoia-inc.com **************************************************************** From exim@www1.ietf.org Wed Dec 31 13:06:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19706 for ; Wed, 31 Dec 2003 13:06:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AbkjE-0006rg-JH for l3vpn-archive@odin.ietf.org; Wed, 31 Dec 2003 13:05:56 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBVI5uM4026382 for l3vpn-archive@odin.ietf.org; Wed, 31 Dec 2003 13:05:56 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AbkjE-0006rR-Ez for l3vpn-web-archive@optimus.ietf.org; Wed, 31 Dec 2003 13:05:56 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19702 for ; Wed, 31 Dec 2003 13:05:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Abkj7-0006Za-00 for l3vpn-web-archive@ietf.org; Wed, 31 Dec 2003 13:05:49 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AbkhU-0006Vo-00 for l3vpn-web-archive@ietf.org; Wed, 31 Dec 2003 13:04:08 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AbkcZ-0006PM-00 for l3vpn-web-archive@ietf.org; Wed, 31 Dec 2003 12:59:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AbkcX-0006ir-Cq; Wed, 31 Dec 2003 12:59:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AbkcI-0006id-0I for l3vpn@optimus.ietf.org; Wed, 31 Dec 2003 12:58:46 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19587 for ; Wed, 31 Dec 2003 12:58:42 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AbkcG-0006NH-00 for l3vpn@ietf.org; Wed, 31 Dec 2003 12:58:44 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AbkaM-0006Jv-00 for l3vpn@ietf.org; Wed, 31 Dec 2003 12:56:47 -0500 Received: from smtp107.mail.sc5.yahoo.com ([66.163.169.227]) by ietf-mx with smtp (Exim 4.12) id 1AbkZo-0006IA-00 for l3vpn@ietf.org; Wed, 31 Dec 2003 12:56:13 -0500 Received: from unknown (HELO RAKHILAPTOP) (vsharma87@63.206.88.209 with login) by smtp107.mail.sc5.yahoo.com with SMTP; 31 Dec 2003 17:56:12 -0000 From: "Vishal Sharma" To: "PamSri" Cc: "L3PPVPN" Subject: RE: Clarification on the L3 framework draft Date: Wed, 31 Dec 2003 09:55:59 -0800 Message-ID: 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 V6.00.2800.1165 In-Reply-To: <20031231162403.84552.qmail@web14104.mail.yahoo.com> Importance: Normal Content-Transfer-Encoding: 7bit Sender: l3vpn-admin@ietf.org Errors-To: l3vpn-admin@ietf.org X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.1 required=5.0 tests=MAILTO_TO_SPAM_ADDR autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Pam, Thanks. I did understand that the aggregate routing model is being talked about here. My question, however, was focused more on how it is possible to make the adjacencies with RRs _independent_ of the no. of PEs, as stated in the draft. As I explained in my email, at least from the perspective of the network as a whole or from that of the RRs, it appears that the no. of adjacencies will, in fact, depend on the no. of PEs (unless I misunderstood something). Thanks, -Vishal > -----Original Message----- > From: PamSri [mailto:pamsri01@yahoo.com] > Sent: Wednesday, December 31, 2003 8:24 AM > To: Vishal Sharma > Subject: Re: Clarification on the L3 framework draft > > > Vishal , > > "PE-PE adjacencies can be > > completely > > eliminated, and furthermore that the no. of backbone > > adjacencies > > can be made a small constant _independent_ of the > > number of > > PEs involved." > > This is from the perspective of a single instance > model that is being talked about, instead of a VFI > model where one routing protocol is used per VFI in > other words one PE-PE peering per VFI. > > sri > > --- Vishal Sharma wrote: > > Folks, > > > > I have the following question, and would appreciate > > someone > > clarifying it. > > > > On pp. 54, Sec. 4.4.4, the document states that > > using > > BGP's route reflectors, PE-PE adjacencies can be > > completely > > eliminated, and furthermore that the no. of backbone > > adjacencies > > can be made a small constant _independent_ of the > > number of > > PEs involved. > > > > I figure even if one is using RR's, each PE device > > would > > have to have an adjacency to one (typcially two) > > RRs, so > > the total adjacencies in the system or on any one RR > > will > > be a function of the number of PEs? > > > > Or, is the statement talking merely of the > > adjacencies between > > the RRs themselves, > > which I suppose would be independent of the number > > of PEs, > > or of the adjacencies on a given PE, which also > > would be > > a constant in this case. > > > > Any insights would be very helpful. > > > > Thanks, > > -Vishal > > > > > **************************************************************** > > Dr. Vishal Sharma > > Metanoia, Inc. > > 1600 Villa Street, Unit 352 > > Mountain View, CA 94041-1174 > > Phone: +1 408-530-8313. Cell: +1 408-394-6321 > > Email: v.sharma@ieee.org. > > http://www.metanoia-inc.com > > > **************************************************************** > > > > > > > __________________________________ > Do you Yahoo!? > Find out what made the Top Yahoo! Searches of 2003 > http://search.yahoo.com/top2003 From exim@www1.ietf.org Wed Dec 31 15:19:29 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24095 for ; Wed, 31 Dec 2003 15:19:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Abmo0-00021Z-94 for l3vpn-archive@odin.ietf.org; Wed, 31 Dec 2003 15:19:00 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBVKJ0QD007775 for l3vpn-archive@odin.ietf.org; Wed, 31 Dec 2003 15:19:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Abmo0-00021J-4F for l3vpn-web-archive@optimus.ietf.org; Wed, 31 Dec 2003 15:19:00 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23961 for ; Wed, 31 Dec 2003 15:18:58 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Abmny-0002ZJ-00 for l3vpn-web-archive@ietf.org; Wed, 31 Dec 2003 15:18:58 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AbmmD-0002MM-00 for l3vpn-web-archive@ietf.org; Wed, 31 Dec 2003 15:17:10 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AbmiV-00025Q-00 for l3vpn-web-archive@ietf.org; Wed, 31 Dec 2003 15:13:19 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AbmiB-0001hW-UB; Wed, 31 Dec 2003 15:12:59 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AbmhR-0001fW-Dd for l3vpn@optimus.ietf.org; Wed, 31 Dec 2003 15:12:13 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23003 for ; Wed, 31 Dec 2003 15:12:07 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AbmhG-00021i-00 for l3vpn@ietf.org; Wed, 31 Dec 2003 15:12:02 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AbmQq-0001h5-00 for l3vpn@ietf.org; Wed, 31 Dec 2003 14:55:05 -0500 Received: from smtp107.mail.sc5.yahoo.com ([66.163.169.227]) by ietf-mx with smtp (Exim 4.12) id 1AbmPO-0001cr-00 for l3vpn@ietf.org; Wed, 31 Dec 2003 14:53:34 -0500 Received: from unknown (HELO RAKHILAPTOP) (vsharma87@67.117.149.209 with login) by smtp107.mail.sc5.yahoo.com with SMTP; 31 Dec 2003 19:53:33 -0000 From: "Vishal Sharma" To: "PamSri" Cc: "L3PPVPN" Subject: RE: Clarification on the L3 framework draft Date: Wed, 31 Dec 2003 11:53:20 -0800 Message-ID: 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 V6.00.2800.1165 In-Reply-To: <20031231191641.40747.qmail@web14105.mail.yahoo.com> Importance: Normal Content-Transfer-Encoding: 7bit Sender: l3vpn-admin@ietf.org Errors-To: l3vpn-admin@ietf.org X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,MAILTO_TO_SPAM_ADDR autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sri, Comments in-line. > -----Original Message----- > From: PamSri [mailto:pamsri01@yahoo.com] > Sent: Wednesday, December 31, 2003 11:17 AM > To: Vishal Sharma > Subject: RE: Clarification on the L3 framework draft > > > Vishal, > The draft says PE-PE adjacencies are eliminated and > the no. of adjacencies in the backbone can be reduced > to a small constant which is independent of PEs when > RRs are used. Seems pretty simple, straightforward and > fair statement. Please look at my explanations more carefully. I have outlined 4 items for which adjacencies may be counted -- i) for the RRs, ii) between the RRs, iii) for the PEs, and iv) for the network as a whole. Of these ii) and iii) may be made constant, and I'd already observed this in my original email. (RRs peer with each other, and this depends on the number of domains that the network is split into, which is likely to be a (long-term) constant. PE's peer with RR's, and typically with 2, so that is also a constant.) > What this is saying is if RRs are used then no matter > how many PEs one adds it does'nt result in that many > PE-PE peerings. In otherwords only PE(RRC) - RR > peerings need to be added when RRs are used. That's right, and I think this fact was pretty clear in my original email itself. But, that does not appear to me to be a case where adjacencies are _independent_ of the number of PEs. (As you add more PE's the no. of adjacencies at the RR's will grow (and thereby so will those in the network as a whole), and moreover, these _will_ be a function of the number of PEs.) So, I was trying to determine the basis of the original statement in the draft, and that question still stands. -Vishal > --- Vishal Sharma wrote: > > Pam, > > > > Thanks. I did understand that the aggregate > > routing model is being talked about here. My > > question, however, was focused more on how it > > is possible to make the adjacencies with RRs > > _independent_ of the no. of PEs, as stated in > > the draft. > > > > As I explained in my email, at least from the > > perspective of the network as a whole or from > > that of the RRs, it appears that the no. of > > adjacencies will, in fact, depend on the no. of > > PEs (unless I misunderstood something). > > > > Thanks, > > -Vishal > > > > > -----Original Message----- > > > From: PamSri [mailto:pamsri01@yahoo.com] > > > Sent: Wednesday, December 31, 2003 8:24 AM > > > To: Vishal Sharma > > > Subject: Re: Clarification on the L3 framework > > draft > > > > > > > > > Vishal , > > > > > > "PE-PE adjacencies can be > > > > completely > > > > eliminated, and furthermore that the no. of > > backbone > > > > adjacencies > > > > can be made a small constant _independent_ of > > the > > > > number of > > > > PEs involved." > > > > > > This is from the perspective of a single instance > > > model that is being talked about, instead of a VFI > > > model where one routing protocol is used per VFI > > in > > > other words one PE-PE peering per VFI. > > > > > > sri > > > > > > --- Vishal Sharma wrote: > > > > Folks, > > > > > > > > I have the following question, and would > > appreciate > > > > someone > > > > clarifying it. > > > > > > > > On pp. 54, Sec. 4.4.4, the document states that > > > > using > > > > BGP's route reflectors, PE-PE adjacencies can be > > > > completely > > > > eliminated, and furthermore that the no. of > > backbone > > > > adjacencies > > > > can be made a small constant _independent_ of > > the > > > > number of > > > > PEs involved. > > > > > > > > I figure even if one is using RR's, each PE > > device > > > > would > > > > have to have an adjacency to one (typcially two) > > > > RRs, so > > > > the total adjacencies in the system or on any > > one RR > > > > will > > > > be a function of the number of PEs? > > > > > > > > Or, is the statement talking merely of the > > > > adjacencies between > > > > the RRs themselves, > > > > which I suppose would be independent of the > > number > > > > of PEs, > > > > or of the adjacencies on a given PE, which also > > > > would be > > > > a constant in this case. > > > > > > > > Any insights would be very helpful. > > > > > > > > Thanks, > > > > -Vishal > > > > > > > > > > > > > > **************************************************************** > > > > Dr. Vishal Sharma > > > > Metanoia, Inc. > > > > 1600 Villa Street, Unit 352 > > > > Mountain View, CA 94041-1174 > > > > Phone: +1 408-530-8313. Cell: +1 408-394-6321 > > > > Email: v.sharma@ieee.org. > > > > http://www.metanoia-inc.com > > > > > > > > > > **************************************************************** > > > > > > > > > > > > > > > > > __________________________________ > > > Do you Yahoo!? > > > Find out what made the Top Yahoo! Searches of 2003 > > > http://search.yahoo.com/top2003 > > > > > __________________________________ > Do you Yahoo!? > Find out what made the Top Yahoo! Searches of 2003 > http://search.yahoo.com/top2003