From idr-bounces@ietf.org Wed Jun 01 15:52:45 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DdZGf-0006C3-Du; Wed, 01 Jun 2005 15:52:45 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DdZGd-0006Bx-UV for idr@megatron.ietf.org; Wed, 01 Jun 2005 15:52:43 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22114 for ; Wed, 1 Jun 2005 15:52:41 -0400 (EDT) Received: from web33702.mail.mud.yahoo.com ([68.142.201.199]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DdZaV-0007FR-Oq for idr@ietf.org; Wed, 01 Jun 2005 16:13:17 -0400 Received: (qmail 50619 invoked by uid 60001); 1 Jun 2005 19:52:33 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=kdHT79fVIMbY2TQBvncm2e+fZn/4TNIO8AwfM7eBaUrK6qHJXu2NTX4kCpPc3LKUlhJj/tNN+qzPJPsFCdNil2GB7HAmGDC1mgqiIOSEYeU2YjKDG1CN5wBU1MlP+7Ebs1mitm3NvLFKcMUkLiBqyEosQMnM7/KvwNjoPDCPFu0= ; Message-ID: <20050601195233.50617.qmail@web33702.mail.mud.yahoo.com> Received: from [209.78.40.100] by web33702.mail.mud.yahoo.com via HTTP; Wed, 01 Jun 2005 12:52:32 PDT Date: Wed, 1 Jun 2005 12:52:32 -0700 (PDT) From: saravana kumar To: idr@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.5 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Content-Transfer-Encoding: 8bit Subject: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Hi, The Active State on the draft reads : "In response to a TCP connection succeeding (Event 16 or Event 17)" I am assuming in Active State there is no pending outbound connection attempt. If this assumption is correct, then is Event 16 Tcp_CR_Acked really valid/possible in active state? I apologize if this question has been answered already, i couldn't locate in the archives. Thanks, skumar. __________________________________ Discover Yahoo! Get on-the-go sports scores, stock quotes, news and more. Check it out! http://discover.yahoo.com/mobile.html _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr From idr-bounces@ietf.org Thu Jun 02 00:28:09 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DdhJR-0002xU-BJ; Thu, 02 Jun 2005 00:28:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DdhJQ-0002xP-KV for idr@megatron.ietf.org; Thu, 02 Jun 2005 00:28:08 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09207 for ; Thu, 2 Jun 2005 00:28:05 -0400 (EDT) Received: from web60723.mail.yahoo.com ([209.73.178.211]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DdhdJ-0002yU-LY for idr@ietf.org; Thu, 02 Jun 2005 00:48:46 -0400 Received: (qmail 74891 invoked by uid 60001); 2 Jun 2005 04:27:54 -0000 Message-ID: <20050602042754.74889.qmail@web60723.mail.yahoo.com> Received: from [66.17.149.13] by web60723.mail.yahoo.com via HTTP; Thu, 02 Jun 2005 00:27:54 EDT Date: Thu, 2 Jun 2005 00:27:54 -0400 (EDT) From: Tulip Rasputin To: idr@ietf.org In-Reply-To: <20050601195233.50617.qmail@web33702.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 2.9 (++) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: 8bit Subject: [Idr] Route Origin Community in *-bgp-ext-communities-08.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Hi, Is the Route Origin Community defined in draft-ietf-idr-bgp-ext-communities-08.txt the same as the Site Of Origin that is explained in a lot of online and regular BGP/MPLS VPN documentation? If not, then I would appreciate if somebody could point me to an IETF doc that tells more about SOO in terms of IANA values, etc. Thanks, Tulip __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr From idr-bounces@ietf.org Thu Jun 02 06:15:54 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ddmjy-0003Q8-Eu; Thu, 02 Jun 2005 06:15:54 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ddmjw-0003Nz-F2 for idr@megatron.ietf.org; Thu, 02 Jun 2005 06:15:52 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26238 for ; Thu, 2 Jun 2005 06:15:49 -0400 (EDT) Received: from astro.systems.pipex.net ([62.241.163.6]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ddn3v-0003fO-RB for idr@ietf.org; Thu, 02 Jun 2005 06:36:33 -0400 Received: from pc6 (1Cust159.tnt3.lnd4.gbr.da.uu.net [62.188.132.159]) by astro.systems.pipex.net (Postfix) with SMTP id B148EE000065; Thu, 2 Jun 2005 11:15:22 +0100 (BST) Message-ID: <029901c56752$f8ea21c0$0601a8c0@pc6> From: "Tom Petch" To: "saravana kumar" , References: <20050601195233.50617.qmail@web33702.mail.mud.yahoo.com> Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) Date: Thu, 2 Jun 2005 10:24:10 +0200 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.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Score: 2.9 (++) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Content-Transfer-Encoding: 7bit Cc: X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tom Petch List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Possible, perhaps not valid, depending on your implementation and what's happening at the other end. Note that Active state is the bucket into which things fall, so while the normal way there is from Idle, you can also get there from Connect state or Open Sent state after a failure. If, in such transitions, you wipe all traces from your memory of having sent a TCP SYN, then the SYN-ACK could appear out of the blue as an invalid packet and be discarded. But if you remember that while in Connect state you sent a SYN and are now getting a second SYN-ACK - perhaps the ACK and OPEN you sent got lost - then that could count as a further event 16. So you certainly can receive a SYN-ACK in Active state but your TCP processing might not let it get to the BGP machine. Tom Petch ----- Original Message ----- From: "saravana kumar" To: Sent: Wednesday, June 01, 2005 9:52 PM Subject: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) > Hi, > The Active State on the draft reads : > "In response to a TCP connection succeeding (Event 16 > or Event 17)" > > I am assuming in Active State there is no pending > outbound connection attempt. > > If this assumption is correct, then is Event 16 > Tcp_CR_Acked really valid/possible in active state? > > I apologize if this question has been answered > already, i couldn't locate in the archives. > > Thanks, > skumar. > > > > __________________________________ > Discover Yahoo! > Get on-the-go sports scores, stock quotes, news and more. Check it out! > http://discover.yahoo.com/mobile.html > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www1.ietf.org/mailman/listinfo/idr _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr From idr-bounces@ietf.org Thu Jun 02 10:36:10 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ddqnq-0004x0-Ii; Thu, 02 Jun 2005 10:36:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ddqno-0004sn-S1 for idr@megatron.ietf.org; Thu, 02 Jun 2005 10:36:09 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21104 for ; Thu, 2 Jun 2005 10:36:06 -0400 (EDT) Received: from web33708.mail.mud.yahoo.com ([68.142.201.205]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Ddr7p-0000kk-ED for idr@ietf.org; Thu, 02 Jun 2005 10:56:51 -0400 Received: (qmail 3868 invoked by uid 60001); 2 Jun 2005 14:35:56 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=adoID0oqsFnsVrjz1JY+2DTv/vxFE5RMjCTLGY3KMLK/+uLpmv1p3IV/4pOkneqxCNrkW/lb8OmWbocRmsmsjFc52V0Y7u1reKkxo+BVWKK708nEPF68dRe+kzzBRP7zYHfKja9TlCZyTD8RM9wVs10VAEyll3mKHaQNAf22ckc= ; Message-ID: <20050602143556.3866.qmail@web33708.mail.mud.yahoo.com> Received: from [209.78.40.100] by web33708.mail.mud.yahoo.com via HTTP; Thu, 02 Jun 2005 07:35:56 PDT Date: Thu, 2 Jun 2005 07:35:56 -0700 (PDT) From: saravana kumar Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) To: Tom Petch , idr@ietf.org In-Reply-To: <029901c56752$f8ea21c0$0601a8c0@pc6> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.5 (/) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 Content-Transfer-Encoding: 8bit Cc: X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Thanks, I realized that, but Event 18 ( TCP connection fail detection by local TCP machinery ) is what gets us to active state. So an outbound connection success after this point seems not likely. Another question along the same lines : In the connect state, if Event 16 happens (inbound connection was successful), the draft suggests "sending an open or start open delay timer." Aren't there two connections (fsms ) to track here : one for the pending outbound connection and the inbound connection? Thanks, -skumar. --- Tom Petch wrote: > Possible, perhaps not valid, depending on your > implementation and what's > happening at the other end. > > Note that Active state is the bucket into which > things fall, so while the normal > way there is from Idle, you can also get there from > Connect state or Open Sent > state after a failure. If, in such transitions, you > wipe all traces from your > memory of having sent a TCP SYN, then the SYN-ACK > could appear out of the blue > as an invalid packet and be discarded. But if you > remember that while in > Connect state you sent a SYN and are now getting a > second SYN-ACK - perhaps the > ACK and OPEN you sent got lost - then that could > count as a further event 16. > So you certainly can receive a SYN-ACK in Active > state but your TCP processing > might not let it get to the BGP machine. > > Tom Petch > > ----- Original Message ----- > From: "saravana kumar" > To: > Sent: Wednesday, June 01, 2005 9:52 PM > Subject: [Idr] draft-ietf-idr-bgp4-26.txt: active > state (page 61) > > > > Hi, > > The Active State on the draft reads : > > "In response to a TCP connection succeeding (Event > 16 > > or Event 17)" > > > > I am assuming in Active State there is no > pending > > outbound connection attempt. > > > > If this assumption is correct, then is Event 16 > > Tcp_CR_Acked really valid/possible in active > state? > > > > I apologize if this question has been answered > > already, i couldn't locate in the archives. > > > > Thanks, > > skumar. > > > > > > > > __________________________________ > > Discover Yahoo! > > Get on-the-go sports scores, stock quotes, news > and more. Check it out! > > http://discover.yahoo.com/mobile.html > > > > _______________________________________________ > > Idr mailing list > > Idr@ietf.org > > https://www1.ietf.org/mailman/listinfo/idr > > __________________________________ Discover Yahoo! Use Yahoo! to plan a weekend, have fun online and more. Check it out! http://discover.yahoo.com/ _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr From idr-bounces@ietf.org Thu Jun 02 14:45:53 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DduhU-00081T-Vq; Thu, 02 Jun 2005 14:45:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DduhS-00081I-LG for idr@megatron.ietf.org; Thu, 02 Jun 2005 14:45:50 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15807 for ; Thu, 2 Jun 2005 14:45:48 -0400 (EDT) Received: from galaxy.systems.pipex.net ([62.241.162.31]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ddv1W-00057C-5a for idr@ietf.org; Thu, 02 Jun 2005 15:06:35 -0400 Received: from pc6 (1Cust241.tnt28.lnd4.gbr.da.uu.net [62.188.156.241]) by galaxy.systems.pipex.net (Postfix) with SMTP id 06ABEE000132; Thu, 2 Jun 2005 19:45:36 +0100 (BST) Message-ID: <005201c5679a$4067dbe0$0601a8c0@pc6> From: "Tom Petch" To: "saravana kumar" , References: <20050602143556.3866.qmail@web33708.mail.mud.yahoo.com> Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) Date: Thu, 2 Jun 2005 19:40:12 +0200 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.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Score: 0.1 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Content-Transfer-Encoding: 7bit Cc: X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tom Petch List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org I don't follow you here. Event 16 I would regard as outbound connection complete; I sent SYN, received SYN-ACK and sent ACK (TCP three-way handshake). Connection established, I send BGP OPEN (or start the DelayOpen timer); I don't see a second connection. Tom Petch ----- Original Message ----- From: "saravana kumar" To: "Tom Petch" ; Sent: Thursday, June 02, 2005 4:35 PM Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) > In the connect state, if Event 16 happens (inbound > connection was successful), the draft suggests > "sending an open or start open delay timer." > > Aren't there two connections (fsms ) to track here : > one for the pending outbound connection and the > inbound connection? > > Thanks, > -skumar. > _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr From idr-bounces@ietf.org Thu Jun 02 17:22:30 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ddx94-0001rD-KP; Thu, 02 Jun 2005 17:22:30 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ddx92-0001r6-WB for idr@megatron.ietf.org; Thu, 02 Jun 2005 17:22:29 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02354 for ; Thu, 2 Jun 2005 17:22:26 -0400 (EDT) Received: from web33704.mail.mud.yahoo.com ([68.142.201.201]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DdxT4-0001lx-GT for idr@ietf.org; Thu, 02 Jun 2005 17:43:15 -0400 Received: (qmail 84990 invoked by uid 60001); 2 Jun 2005 21:22:14 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=lygfplzWVVH/yC6Rp7LFJQAEu1buSzNHW/NJEi70jUKNgoYUn40cy/lgSlPnE3d5xy6FqM9ndYIq0hLOw43lvHAn8jWf7Hmi5jhD0olunAdyXQ0OMFg1hethhCnvKsLaZtqlpAp6f/gRR/suWPXvZ6TcFR8XtPKnRkdB/WuJ0NA= ; Message-ID: <20050602212214.84988.qmail@web33704.mail.mud.yahoo.com> Received: from [209.78.40.100] by web33704.mail.mud.yahoo.com via HTTP; Thu, 02 Jun 2005 14:22:13 PDT Date: Thu, 2 Jun 2005 14:22:13 -0700 (PDT) From: saravana kumar Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) To: Tom Petch , idr@ietf.org In-Reply-To: <005201c5679a$4067dbe0$0601a8c0@pc6> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.5 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Content-Transfer-Encoding: 8bit Cc: X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org correction: Read that as Event 17. -skumar. --- Tom Petch wrote: > I don't follow you here. Event 16 I would regard as > outbound connection > complete; I sent SYN, received SYN-ACK and sent ACK > (TCP three-way handshake). > Connection established, I send BGP OPEN (or start > the DelayOpen timer); I don't > see a second connection. > > Tom Petch > > ----- Original Message ----- > From: "saravana kumar" > To: "Tom Petch" ; > > Sent: Thursday, June 02, 2005 4:35 PM > Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: > active state (page 61) > > > In the connect state, if Event 16 happens (inbound > > connection was successful), the draft suggests > > "sending an open or start open delay timer." > > > > Aren't there two connections (fsms ) to track here > : > > one for the pending outbound connection and the > > inbound connection? > > > > Thanks, > > -skumar. > > > > > __________________________________ Discover Yahoo! Get on-the-go sports scores, stock quotes, news and more. Check it out! http://discover.yahoo.com/mobile.html _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr From idr-bounces@ietf.org Sun Jun 05 05:27:39 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DerPu-0006CL-Oo; Sun, 05 Jun 2005 05:27:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DerPs-0006CG-OA for idr@megatron.ietf.org; Sun, 05 Jun 2005 05:27:36 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23961 for ; Sun, 5 Jun 2005 05:27:34 -0400 (EDT) Received: from ranger.systems.pipex.net ([62.241.162.32]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DerkU-0003Qe-Nh for idr@ietf.org; Sun, 05 Jun 2005 05:48:55 -0400 Received: from pc6 (1Cust104.tnt13.lnd4.gbr.da.uu.net [62.188.142.104]) by ranger.systems.pipex.net (Postfix) with SMTP id 097AAE00028A; Sun, 5 Jun 2005 10:27:23 +0100 (BST) Message-ID: <004701c569a7$c215f140$0601a8c0@pc6> From: "Tom Petch" To: "saravana kumar" , References: <20050602212214.84988.qmail@web33704.mail.mud.yahoo.com> Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) Date: Sun, 5 Jun 2005 10:20:06 +0200 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.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Score: 0.1 (/) X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8 Content-Transfer-Encoding: 7bit Cc: X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tom Petch List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Probably two connections. Event 17 in the Connect state should have been preceded by Event 14 TcpConnection_Valid in Connect state, most likely with DelayOpenTimer running. But the intention of this fsm is to model all that happens between a particular pair of configured peers with a single fsm at each end. (Modelling each connection between a particular pair of peers as an fsm requires a different set of events and states; it was discussed but would have greater changes to the existing specification which was not considered within the remit of the WG). The challenge then is, as discussed in 8.2.1, that the identifier of the peer is not known until OPENs are exchanged, so each tcp connection may start as a separate fsm and then when it becomes apparent that there is already an fsm for this peer, 6.8 BGP connection collision detection comes into play and you end up with one. But you are not required to implement it this way as long as the appearance you present conforms with the specification. You may choose to know from the TCP SYN that this packet relates to an existing fsm and not create a second. As with any fsm, it is a matter of judgement what states there are, what events there are. What you see is considered the best compromise. Read section 8.2.1 carefully; it says what there is to be said. Tom Petch ----- Original Message ----- From: "saravana kumar" To: "Tom Petch" ; Sent: Thursday, June 02, 2005 11:22 PM Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) > correction: Read that as Event 17. > -skumar. > --- Tom Petch wrote: > > > I don't follow you here. Event 16 I would regard as > > outbound connection > > complete; I sent SYN, received SYN-ACK and sent ACK > > (TCP three-way handshake). > > Connection established, I send BGP OPEN (or start > > the DelayOpen timer); I don't > > see a second connection. > > > > Tom Petch > > > > ----- Original Message ----- > > From: "saravana kumar" > > To: "Tom Petch" ; > > > > Sent: Thursday, June 02, 2005 4:35 PM > > Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: > > active state (page 61) > > > > > In the connect state, if Event 16 happens (inbound > > > connection was successful), the draft suggests > > > "sending an open or start open delay timer." > > > > > > Aren't there two connections (fsms ) to track here > > : > > > one for the pending outbound connection and the > > > inbound connection? > > > > > > Thanks, > > > -skumar. > > > > > > > > > > > > > > __________________________________ > Discover Yahoo! > Get on-the-go sports scores, stock quotes, news and more. Check it out! > http://discover.yahoo.com/mobile.html > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www1.ietf.org/mailman/listinfo/idr _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr From idr-bounces@ietf.org Sun Jun 05 12:12:53 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dexk5-0006H8-Kx; Sun, 05 Jun 2005 12:12:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dexk3-0006Gz-JZ for idr@megatron.ietf.org; Sun, 05 Jun 2005 12:12:51 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15976 for ; Sun, 5 Jun 2005 12:12:49 -0400 (EDT) Received: from web33715.mail.mud.yahoo.com ([68.142.201.212]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Dey4f-00028V-2E for idr@ietf.org; Sun, 05 Jun 2005 12:34:13 -0400 Received: (qmail 21068 invoked by uid 60001); 5 Jun 2005 16:12:37 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=stDtzAJ4y+OTTowPGjeV5u1jT73vxc1gtcNFyQKaUkaZiYTSofT1VRHWtqm/ZiBu72uV/CJOoAVkuqN2l08yHWXlHHhzHht5VSr7R49rLwaUB4ZiRqp1UypoVAMHxhuJ4wE5bnlYgGbRfP92NZRrRihkIC1zI5OsqyYQrB0oIjY= ; Message-ID: <20050605161237.21066.qmail@web33715.mail.mud.yahoo.com> Received: from [209.78.40.100] by web33715.mail.mud.yahoo.com via HTTP; Sun, 05 Jun 2005 09:12:37 PDT Date: Sun, 5 Jun 2005 09:12:37 -0700 (PDT) From: saravana kumar Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) To: Tom Petch , idr@ietf.org In-Reply-To: <004701c569a7$c215f140$0601a8c0@pc6> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.5 (/) X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8 Content-Transfer-Encoding: 8bit Cc: X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Thanks for your response. I am deriving : on detecting an inbound connection attempt : 1) In the connect state, continue to be in the connect state; process the new connection with a new fsm in active state. I am not sure you could 'choose' to close the outbound connection fsm as that would cause both sides to potentially close the connection same way. 2) In the active state ( no outbound connection pending ), associate the inbound connection with the current fsm. Question : Suppose unconfigured peers were never allowed by the draft (as i suppose is reality), is it correct to say that one could've used source tcp address comparison as a means to break the tie as soon as it is detected? (assuming both sides use this mechanism). -skumar. --- Tom Petch wrote: > Probably two connections. Event 17 in the Connect > state should have been > preceded by Event 14 TcpConnection_Valid in Connect > state, most likely with > DelayOpenTimer running. > > But the intention of this fsm is to model all that > happens between a particular > pair of configured peers with a single fsm at each > end. (Modelling each > connection between a particular pair of peers as an > fsm requires a different set > of events and states; it was discussed but would > have greater changes to the > existing specification which was not considered > within the remit of the WG). > The challenge then is, as discussed in 8.2.1, that > the identifier of the peer is > not known until OPENs are exchanged, so each tcp > connection may start as a > separate fsm and then when it becomes apparent that > there is already an fsm for > this peer, 6.8 BGP connection collision detection > comes into play and you end > up with one. But you are not required to implement > it this way as long as the > appearance you present conforms with the > specification. You may choose to know > from the TCP SYN that this packet relates to an > existing fsm and not create a > second. > > As with any fsm, it is a matter of judgement what > states there are, what events > there are. What you see is considered the best > compromise. Read section 8.2.1 > carefully; it says what there is to be said. > > Tom Petch > > ----- Original Message ----- > From: "saravana kumar" > To: "Tom Petch" ; > > Sent: Thursday, June 02, 2005 11:22 PM > Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: > active state (page 61) > > > > correction: Read that as Event 17. > > -skumar. > > --- Tom Petch wrote: > > > > > I don't follow you here. Event 16 I would > regard as > > > outbound connection > > > complete; I sent SYN, received SYN-ACK and sent > ACK > > > (TCP three-way handshake). > > > Connection established, I send BGP OPEN (or > start > > > the DelayOpen timer); I don't > > > see a second connection. > > > > > > Tom Petch > > > > > > ----- Original Message ----- > > > From: "saravana kumar" > > > > To: "Tom Petch" ; > > > > > > Sent: Thursday, June 02, 2005 4:35 PM > > > Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: > > > active state (page 61) > > > > > > > In the connect state, if Event 16 happens > (inbound > > > > connection was successful), the draft suggests > > > > "sending an open or start open delay timer." > > > > > > > > Aren't there two connections (fsms ) to track > here > > > : > > > > one for the pending outbound connection and > the > > > > inbound connection? > > > > > > > > Thanks, > > > > -skumar. > > > > > > > > > > > > > > > > > > > > > > > __________________________________ > > Discover Yahoo! > > Get on-the-go sports scores, stock quotes, news > and more. Check it out! > > http://discover.yahoo.com/mobile.html > > > > _______________________________________________ > > Idr mailing list > > Idr@ietf.org > > https://www1.ietf.org/mailman/listinfo/idr > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr From idr-bounces@ietf.org Mon Jun 06 06:07:33 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DfEW5-0000JE-49; Mon, 06 Jun 2005 06:07:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DfEW3-0000Iy-56 for idr@megatron.ietf.org; Mon, 06 Jun 2005 06:07:31 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15564 for ; Mon, 6 Jun 2005 06:07:28 -0400 (EDT) Received: from galaxy.systems.pipex.net ([62.241.162.31]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DfEqr-000581-U3 for idr@ietf.org; Mon, 06 Jun 2005 06:29:02 -0400 Received: from pc6 (1Cust154.tnt109.lnd4.gbr.da.uu.net [62.188.172.154]) by galaxy.systems.pipex.net (Postfix) with SMTP id 58FB5E000155; Mon, 6 Jun 2005 11:07:16 +0100 (BST) Message-ID: <02f901c56a76$7e2eab00$0601a8c0@pc6> From: "Tom Petch" To: "saravana kumar" , "idr" References: <20050605161237.21066.qmail@web33715.mail.mud.yahoo.com> Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) Date: Mon, 6 Jun 2005 10:59:19 +0200 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.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Score: 0.1 (/) X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4 Content-Transfer-Encoding: 7bit Cc: X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tom Petch List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org I think you should do what the I-D says if you wish to interoperate with other implementations:-). The issue, which I think lay behind your initial question, is that depending on how you choose to set up the fsm, some events are unlikely to occur (I hesitate to say cannot without spending more time thinking about it). In particular, it is BGP identifier, usually from the OPEN message, that you must use to identify which peer wins a collision. s6.8 defines what a connection collision is in terms of source and destination IP address so, at TCP SYN time, you see a collision coming but then have to track the progress of the TCP connection until you find out what you do about it and ensure the BGP peer has the information to take the same decision as you ie, assuming no errors, you should send SYN-ACK and OPEN and then NOTIFICATION on the one that is to be closed. Quite how you do this is up to you. One constraint is that the bgp4-mib has a peer table indexed by remote ip address with fsm state in it which pushes you towards having one fsm per remote ip address/peer as far as possible. You will find the fsm discussed in the idr archives, at least from Jan2002 to Nov2003; the issue of how many fsm to have crops up several times, eg in January, July and September 2002. To quote one suggestion (not quite the wording we ended up with) An instance of an FSM is created by a BGP speaker for each configured peer. It may also be created dynamically when an incoming transport connection is reported, there's no matching configured peer and the speaker is configured to accept such connections This, as another post says, is a temporary breach of the idea that BGP limits you to a single connection between a pair of ip addresses and that there is one fsm associated with it Tom Petch ----- Original Message ----- From: "saravana kumar" To: "Tom Petch" ; Sent: Sunday, June 05, 2005 6:12 PM Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) > Thanks for your response. > > I am deriving : > > on detecting an inbound connection attempt : > 1) In the connect state, continue to be in the > connect state; process the new connection with a new > fsm in active state. I am not sure you could 'choose' > to close the outbound connection fsm as that would > cause > both sides to potentially close the connection same > way. > > 2) In the active state ( no outbound connection > pending ), associate the inbound connection with the > current fsm. > > Question : Suppose unconfigured peers were never > allowed by the draft (as i suppose is reality), is it > correct to say that one could've used source tcp > address comparison as a means to break the tie as soon > as it is detected? (assuming both sides use this > mechanism). > > -skumar. /listinfo/idr _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr From idr-bounces@ietf.org Fri Jun 10 09:06:18 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DgjDF-0000HF-SF; Fri, 10 Jun 2005 09:06:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DgjDD-0000Ei-QI for idr@megatron.ietf.org; Fri, 10 Jun 2005 09:06:15 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17992 for ; Fri, 10 Jun 2005 09:06:13 -0400 (EDT) Received: from colo-dns-ext1.juniper.net ([207.17.137.57]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DgjYr-00075R-Eu for idr@ietf.org; Fri, 10 Jun 2005 09:28:39 -0400 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id j5AD64906461 for ; Fri, 10 Jun 2005 06:06:04 -0700 (PDT) (envelope-from yakov@juniper.net) Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j5AD5xe06718 for ; Fri, 10 Jun 2005 06:05:59 -0700 (PDT) (envelope-from yakov@juniper.net) Message-Id: <200506101305.j5AD5xe06718@merlot.juniper.net> To: idr@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <17310.1118408758.1@juniper.net> Date: Fri, 10 Jun 2005 06:05:59 -0700 From: Yakov Rekhter X-Spam-Score: 0.0 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Subject: [Idr] Internet Draft submission Cutoff Dates X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org fyi ------- Forwarded Message Date: Fri, 10 Jun 2005 00:00:01 -0400 From: ietf-secretariat@ietf.org To: ietf-announce@ietf.org Subject: Internet-Drafts Submission Cutoff Dates for the 63rd IETF Meeting in P aris, France There are two (2) Internet-Draft cutoff dates for the 63rd IETF Meeting in Paris, France: July 11th: Cutoff Date for Initial (i.e., version -00) Internet-Draft Submissions All initial Internet-Drafts (version -00) must be submitted by Monday, July 11th at 9:00 AM ET. As always, all initial submissions with a filename beginning with "draft-ietf" must be approved by the appropriate WG Chair before they can be processed or announced. The Secretariat would appreciate receiving WG Chair approval by Tuesday, July 5th at 9:00 AM ET. July 18th: Cutoff Date for Revised (i.e., version -01 and higher) Internet-Draft Submissions All revised Internet-Drafts (version -01 and higher) must be submitted by Monday, July 18th at 9:00 AM ET. Initial and revised Internet-Drafts received after their respective cutoff dates will not be made available in the Internet-Drafts directory or announced until on or after Monday, August 1st at 9:00 AM ET, when Internet-Draft posting resumes. Please do not wait until the last minute to submit. PLEASE NOTE THE CHANGE OF PROCEDURE: If you submit an initial or revised Internet-Draft after their respective cutoff deadlines, then your document will be retained and posted when Internet-Draft processing resumes. You will no longer be required to resubmit the document. Thank you for your understanding and cooperation. If you have any questions or concerns, then please send a message to internet-drafts@ietf.org. The IETF Secretariat FYI: The Internet-Draft cutoff dates as well as other significant dates for the 63rd IETF Meeting can be found at http://www.ietf.org/meetings/cutoff_d ates_63.html. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce ------- End of Forwarded Message _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr From idr-bounces@ietf.org Mon Jun 20 09:41:13 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DkMWX-00022E-8b; Mon, 20 Jun 2005 09:41:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DkMWV-00021v-Ox for idr@megatron.ietf.org; Mon, 20 Jun 2005 09:41:11 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28254 for ; Mon, 20 Jun 2005 09:41:10 -0400 (EDT) Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DkMuB-0001cH-Px for idr@ietf.org; Mon, 20 Jun 2005 10:05:43 -0400 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 j5KDewBm028488; Mon, 20 Jun 2005 06:40:58 -0700 (PDT) (envelope-from yakov@juniper.net) Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j5KDeqj73105; Mon, 20 Jun 2005 06:40:52 -0700 (PDT) (envelope-from yakov@juniper.net) Message-Id: <200506201340.j5KDeqj73105@merlot.juniper.net> To: idr@ietf.org Subject: [Idr] IDR WG agenda MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <95945.1119274852.1@juniper.net> Date: Mon, 20 Jun 2005 06:40:52 -0700 From: Yakov Rekhter X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Cc: skh@nexthop.com, yakov@juniper.net X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Folks, Its about time to start thinking about agenda items for the next IETF. Please forward any IDR agenda items you might have to me and Sue. And if you plan to make a presentation, please also keep in mind the rule "no document - no time slot". Sue & Yakov. _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr From idr-bounces@ietf.org Tue Jun 21 15:50:35 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DkolX-0005GO-05; Tue, 21 Jun 2005 15:50:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dkol4-00058u-Jk; Tue, 21 Jun 2005 15:50:06 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24754; Tue, 21 Jun 2005 15:50:04 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dkp90-0007RL-Ji; Tue, 21 Jun 2005 16:14:51 -0400 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1Dkol0-0002aW-B5; Tue, 21 Jun 2005 15:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Tue, 21 Jun 2005 15:50:02 -0400 X-Spam-Score: 0.4 (/) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Cc: idr@ietf.org Subject: [Idr] I-D ACTION:draft-ietf-idr-dynamic-cap-07.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing Working Group of the IETF. Title : Dynamic Capability for BGP-4 Author(s) : E. Chen, S. Sangli Filename : draft-ietf-idr-dynamic-cap-07.txt Pages : 8 Date : 2005-6-21 This document defines a new BGP capability termed "Dynamic Capability", which would allow the dynamic update of capabilities over an established BGP session. This capability would facilitate non-disruptive capability changes by BGP speakers. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idr-dynamic-cap-07.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-idr-dynamic-cap-07.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-idr-dynamic-cap-07.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-6-21151547.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-idr-dynamic-cap-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-idr-dynamic-cap-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-6-21151547.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr --NextPart-- From idr-bounces@ietf.org Tue Jun 21 15:50:54 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dkolp-0005Kl-Tr; Tue, 21 Jun 2005 15:50:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dkol6-0005AS-Qh; Tue, 21 Jun 2005 15:50:08 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24782; Tue, 21 Jun 2005 15:50:06 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dkp90-0007RK-Ff; Tue, 21 Jun 2005 16:14:51 -0400 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1Dkol0-0002aR-A3; Tue, 21 Jun 2005 15:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Tue, 21 Jun 2005 15:50:02 -0400 X-Spam-Score: 0.4 (/) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Cc: idr@ietf.org Subject: [Idr] I-D ACTION:draft-ietf-idr-avoid-transition-02.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing Working Group of the IETF. Title : Avoid BGP Best Path Transitions from One External to Another Author(s) : E. Chen, S. Sangli Filename : draft-ietf-idr-avoid-transition-02.txt Pages : 6 Date : 2005-6-21 In this document we propose a revision to the BGP route selection rules that would avoid unnecessary best path transitions between external paths under certain conditions. The proposed revision would help the overall network stability, and more importantly, would eliminate certain BGP route oscillations in which more than one external paths from one router contribute to the churn. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idr-avoid-transition-02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-idr-avoid-transition-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-idr-avoid-transition-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-6-21151528.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-idr-avoid-transition-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-idr-avoid-transition-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-6-21151528.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr --NextPart-- From idr-bounces@ietf.org Wed Jun 22 07:17:49 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl3Er-00053D-Na; Wed, 22 Jun 2005 07:17:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl3Ep-000537-Gg for idr@megatron.ietf.org; Wed, 22 Jun 2005 07:17:47 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25947 for ; Wed, 22 Jun 2005 07:17:46 -0400 (EDT) Received: from frontend-2.servers.ua.pt ([193.136.173.3] helo=cgpmail.ua.pt) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dl3cv-0003Q7-Co for idr@ietf.org; Wed, 22 Jun 2005 07:42:42 -0400 Received: from [192.168.0.204] (account a20081@alunos.det.ua.pt HELO tiago) by frontend2.cgpmail.ua.pt (CommuniGate Pro SMTP 4.3.4) with ESMTPSA id 15283690 for idr@ietf.org; Wed, 22 Jun 2005 12:17:28 +0100 From: "Tiago Costa" To: Date: Wed, 22 Jun 2005 12:17:30 +0100 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Thread-Index: AcV3G/rlFI8X0Pi1QECKM9de4cmkgg== X-Spam-Score: 0.9 (/) X-Scan-Signature: 612a16ba5c5f570bfc42b3ac5606ac53 Subject: [Idr] PIM inter AS X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1033117083==" Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org This is a multi-part message in MIME format. --===============1033117083== Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01C57724.5D0A6EE0" This is a multi-part message in MIME format. ------=_NextPart_000_000E_01C57724.5D0A6EE0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi! I' am a student from University of Aveiro and in my final project I need to configure multicast protocol between tow Autonomous System. I have configured in each AS one RP with MSDP, one border router with MBGP to the outside of the AS and PIM SM to the inside. My unicast protocol in each AS is RIP. My question is. Do I need to configure PIM SM between MBGP peers?? Tiago Costa ------=_NextPart_000_000E_01C57724.5D0A6EE0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi!

I’ am a student from = University of = Aveiro and in my final project = I need to configure multicast protocol between tow Autonomous = System.

I have configured in each AS = one RP with MSDP, one border router with MBGP to the outside of the AS and PIM = SM to the inside. My unicast protocol in each AS is = RIP.

My question is. Do I need to configure PIM SM between MBGP peers??

 

Tiago = Costa

 

 

 

------=_NextPart_000_000E_01C57724.5D0A6EE0-- --===============1033117083== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr --===============1033117083==-- From idr-bounces@ietf.org Wed Jun 22 14:18:48 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl9oG-0002Ui-LZ; Wed, 22 Jun 2005 14:18:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl9oE-0002TW-3x for idr@megatron.ietf.org; Wed, 22 Jun 2005 14:18:46 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12347 for ; Wed, 22 Jun 2005 14:18:43 -0400 (EDT) Received: from kanfw1.ottawa.alcatel.ca ([192.75.23.69] helo=tm2.ca.alcatel.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DlA4j-0002ky-Aw for idr@ietf.org; Wed, 22 Jun 2005 14:35:50 -0400 Received: from [138.120.52.226] (localhost [127.0.0.1]) by tm2.ca.alcatel.com (8.13.0/8.13.0) with ESMTP id j5MIAKDI014859; Wed, 22 Jun 2005 14:10:21 -0400 (EDT) Message-ID: <42B9A98C.8090005@alcatel.com> Date: Wed, 22 Jun 2005 14:10:20 -0400 From: REZA ROKUI Organization: Alcatel User-Agent: Mozilla Thunderbird 1.0 (X11/20050201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tiago Costa Subject: Re: [Idr] PIM inter AS References: In-Reply-To: Content-Type: multipart/mixed; boundary="------------030109090601040408010807" X-Spam-Score: 1.0 (+) X-Scan-Signature: 86f85b2f88b0d50615aed44a7f9e33c7 Cc: idr@ietf.org X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org This is a multi-part message in MIME format. --------------030109090601040408010807 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Tiago,

Yes you should do it because when the RP in AS2 receives the MSDP SA (source active) message from AS1, it
causes RP to send (S,G) Join toward the source in AS1. So, you will see that the link between MBGP peers should
be PIM enabled. In addition, if any host in AS2 wants to do SPT-switchover, it should send Join(S,G) toward
source in AS1 which again shows that the link between MBGP peers should be PIM enabled.

REZA
 
Tiago Costa wrote:

Hi!

I’ am a student from University of Aveiro and in my final project I need to configure multicast protocol between tow Autonomous System.

I have configured in each AS one RP with MSDP, one border router with MBGP to the outside of the AS and PIM SM to the inside. My unicast protocol in each AS is RIP.

My question is. Do I need to configure PIM SM between MBGP peers??

 

Tiago Costa

 

 

 


_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr

--------------030109090601040408010807 Content-Type: text/x-vcard; charset=utf-8; name="reza.rokui.vcf" Content-Disposition: attachment; filename="reza.rokui.vcf" Content-Transfer-Encoding: 7bit begin:vcard org:
7670 RSP IP Routing Group
Alcatel IP Division (IPD) title:
Reza Rokui, Ph.D.
Software Designer x-mozilla-html:FALSE version:2.1 end:vcard --------------030109090601040408010807 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr --------------030109090601040408010807-- From idr-bounces@ietf.org Mon Jun 27 18:50:14 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dn2Qg-0004pl-Sv; Mon, 27 Jun 2005 18:50:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dn2QV-0004mP-3J; Mon, 27 Jun 2005 18:50:03 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05746; Mon, 27 Jun 2005 18:49:59 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dn2pj-0003GT-98; Mon, 27 Jun 2005 19:16:07 -0400 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1Dn2QT-0001di-NS; Mon, 27 Jun 2005 18:50:01 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 27 Jun 2005 18:50:01 -0400 X-Spam-Score: 0.4 (/) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: idr@ietf.org Subject: [Idr] I-D ACTION:draft-ietf-idr-cease-subcode-06.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing Working Group of the IETF. Title : Subcodes for BGP Cease Notification Message Author(s) : E. Chen, V. Gillet Filename : draft-ietf-idr-cease-subcode-06.txt Pages : 6 Date : 2005-6-27 This document defines several subcodes for the BGP Cease NOTIFICATION message that would provide more information to aid network operators in correlating network events and diagnosing BGP peering issues. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idr-cease-subcode-06.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-idr-cease-subcode-06.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-idr-cease-subcode-06.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-6-27162255.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-idr-cease-subcode-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-idr-cease-subcode-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-6-27162255.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr --NextPart-- Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id TAA08894 for ; Mon, 27 Jun 2005 19:03:11 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dn2Qg-0004pl-QP; Mon, 27 Jun 2005 18:50:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dn2QV-0004mP-3J; Mon, 27 Jun 2005 18:50:03 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05746; Mon, 27 Jun 2005 18:49:59 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dn2pj-0003GT-98; Mon, 27 Jun 2005 19:16:07 -0400 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1Dn2QT-0001di-NS; Mon, 27 Jun 2005 18:50:01 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 27 Jun 2005 18:50:01 -0400 X-Spam-Score: 0.4 (/) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: idr@ietf.org Subject: [Idr] I-D ACTION:draft-ietf-idr-cease-subcode-06.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing Working Group of the IETF. Title : Subcodes for BGP Cease Notification Message Author(s) : E. Chen, V. Gillet Filename : draft-ietf-idr-cease-subcode-06.txt Pages : 6 Date : 2005-6-27 This document defines several subcodes for the BGP Cease NOTIFICATION message that would provide more information to aid network operators in correlating network events and diagnosing BGP peering issues. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idr-cease-subcode-06.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-idr-cease-subcode-06.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-idr-cease-subcode-06.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-6-27162255.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-idr-cease-subcode-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-idr-cease-subcode-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-6-27162255.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr --NextPart-- Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id OAA06145 for ; Wed, 22 Jun 2005 14:24:03 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl9oG-0002Ui-HB; Wed, 22 Jun 2005 14:18:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl9oE-0002TW-3x for idr@megatron.ietf.org; Wed, 22 Jun 2005 14:18:46 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12347 for ; Wed, 22 Jun 2005 14:18:43 -0400 (EDT) Received: from kanfw1.ottawa.alcatel.ca ([192.75.23.69] helo=tm2.ca.alcatel.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DlA4j-0002ky-Aw for idr@ietf.org; Wed, 22 Jun 2005 14:35:50 -0400 Received: from [138.120.52.226] (localhost [127.0.0.1]) by tm2.ca.alcatel.com (8.13.0/8.13.0) with ESMTP id j5MIAKDI014859; Wed, 22 Jun 2005 14:10:21 -0400 (EDT) Message-ID: <42B9A98C.8090005@alcatel.com> Date: Wed, 22 Jun 2005 14:10:20 -0400 From: REZA ROKUI Organization: Alcatel User-Agent: Mozilla Thunderbird 1.0 (X11/20050201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tiago Costa Subject: Re: [Idr] PIM inter AS References: In-Reply-To: Content-Type: multipart/mixed; boundary="------------030109090601040408010807" X-Spam-Score: 1.0 (+) X-Scan-Signature: 86f85b2f88b0d50615aed44a7f9e33c7 Cc: idr@ietf.org X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org This is a multi-part message in MIME format. --------------030109090601040408010807 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Tiago,

Yes you should do it because when the RP in AS2 receives the MSDP SA (source active) message from AS1, it
causes RP to send (S,G) Join toward the source in AS1. So, you will see that the link between MBGP peers should
be PIM enabled. In addition, if any host in AS2 wants to do SPT-switchover, it should send Join(S,G) toward
source in AS1 which again shows that the link between MBGP peers should be PIM enabled.

REZA
 
Tiago Costa wrote:

Hi!

I’ am a student from University of Aveiro and in my final project I need to configure multicast protocol between tow Autonomous System.

I have configured in each AS one RP with MSDP, one border router with MBGP to the outside of the AS and PIM SM to the inside. My unicast protocol in each AS is RIP.

My question is. Do I need to configure PIM SM between MBGP peers??

 

Tiago Costa

 

 

 


_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr

--------------030109090601040408010807 Content-Type: text/x-vcard; charset=utf-8; name="reza.rokui.vcf" Content-Disposition: attachment; filename="reza.rokui.vcf" Content-Transfer-Encoding: 7bit begin:vcard org:
7670 RSP IP Routing Group
Alcatel IP Division (IPD) title:
Reza Rokui, Ph.D.
Software Designer x-mozilla-html:FALSE version:2.1 end:vcard --------------030109090601040408010807 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr --------------030109090601040408010807-- Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id HAA03254 for ; Wed, 22 Jun 2005 07:18:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl3Er-00053D-IL; Wed, 22 Jun 2005 07:17:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl3Ep-000537-Gg for idr@megatron.ietf.org; Wed, 22 Jun 2005 07:17:47 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25947 for ; Wed, 22 Jun 2005 07:17:46 -0400 (EDT) Received: from frontend-2.servers.ua.pt ([193.136.173.3] helo=cgpmail.ua.pt) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dl3cv-0003Q7-Co for idr@ietf.org; Wed, 22 Jun 2005 07:42:42 -0400 Received: from [192.168.0.204] (account a20081@alunos.det.ua.pt HELO tiago) by frontend2.cgpmail.ua.pt (CommuniGate Pro SMTP 4.3.4) with ESMTPSA id 15283690 for idr@ietf.org; Wed, 22 Jun 2005 12:17:28 +0100 From: "Tiago Costa" To: Date: Wed, 22 Jun 2005 12:17:30 +0100 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Thread-Index: AcV3G/rlFI8X0Pi1QECKM9de4cmkgg== X-Spam-Score: 0.9 (/) X-Scan-Signature: 612a16ba5c5f570bfc42b3ac5606ac53 Subject: [Idr] PIM inter AS X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1033117083==" Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org This is a multi-part message in MIME format. --===============1033117083== Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01C57724.5D0A6EE0" This is a multi-part message in MIME format. ------=_NextPart_000_000E_01C57724.5D0A6EE0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi! I' am a student from University of Aveiro and in my final project I need to configure multicast protocol between tow Autonomous System. I have configured in each AS one RP with MSDP, one border router with MBGP to the outside of the AS and PIM SM to the inside. My unicast protocol in each AS is RIP. My question is. Do I need to configure PIM SM between MBGP peers?? Tiago Costa ------=_NextPart_000_000E_01C57724.5D0A6EE0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi!

I’ am a student from = University of = Aveiro and in my final project = I need to configure multicast protocol between tow Autonomous = System.

I have configured in each AS = one RP with MSDP, one border router with MBGP to the outside of the AS and PIM = SM to the inside. My unicast protocol in each AS is = RIP.

My question is. Do I need to configure PIM SM between MBGP peers??

 

Tiago = Costa

 

 

 

------=_NextPart_000_000E_01C57724.5D0A6EE0-- --===============1033117083== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr --===============1033117083==-- Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id QAA23477 for ; Tue, 21 Jun 2005 16:25:20 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DkolW-0005GO-Tg; Tue, 21 Jun 2005 15:50:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dkol4-00058u-Jk; Tue, 21 Jun 2005 15:50:06 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24754; Tue, 21 Jun 2005 15:50:04 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dkp90-0007RL-Ji; Tue, 21 Jun 2005 16:14:51 -0400 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1Dkol0-0002aW-B5; Tue, 21 Jun 2005 15:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Tue, 21 Jun 2005 15:50:02 -0400 X-Spam-Score: 0.4 (/) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Cc: idr@ietf.org Subject: [Idr] I-D ACTION:draft-ietf-idr-dynamic-cap-07.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing Working Group of the IETF. Title : Dynamic Capability for BGP-4 Author(s) : E. Chen, S. Sangli Filename : draft-ietf-idr-dynamic-cap-07.txt Pages : 8 Date : 2005-6-21 This document defines a new BGP capability termed "Dynamic Capability", which would allow the dynamic update of capabilities over an established BGP session. This capability would facilitate non-disruptive capability changes by BGP speakers. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idr-dynamic-cap-07.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-idr-dynamic-cap-07.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-idr-dynamic-cap-07.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-6-21151547.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-idr-dynamic-cap-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-idr-dynamic-cap-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-6-21151547.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr --NextPart-- Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id QAA22972 for ; Tue, 21 Jun 2005 16:18:50 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dkolp-0005Kl-R5; Tue, 21 Jun 2005 15:50:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dkol6-0005AS-Qh; Tue, 21 Jun 2005 15:50:08 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24782; Tue, 21 Jun 2005 15:50:06 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dkp90-0007RK-Ff; Tue, 21 Jun 2005 16:14:51 -0400 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1Dkol0-0002aR-A3; Tue, 21 Jun 2005 15:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Tue, 21 Jun 2005 15:50:02 -0400 X-Spam-Score: 0.4 (/) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Cc: idr@ietf.org Subject: [Idr] I-D ACTION:draft-ietf-idr-avoid-transition-02.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing Working Group of the IETF. Title : Avoid BGP Best Path Transitions from One External to Another Author(s) : E. Chen, S. Sangli Filename : draft-ietf-idr-avoid-transition-02.txt Pages : 6 Date : 2005-6-21 In this document we propose a revision to the BGP route selection rules that would avoid unnecessary best path transitions between external paths under certain conditions. The proposed revision would help the overall network stability, and more importantly, would eliminate certain BGP route oscillations in which more than one external paths from one router contribute to the churn. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idr-avoid-transition-02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-idr-avoid-transition-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-idr-avoid-transition-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-6-21151528.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-idr-avoid-transition-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-idr-avoid-transition-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-6-21151528.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr --NextPart-- Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id JAA01888 for ; Mon, 20 Jun 2005 09:44:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DkMWX-00022E-5W; Mon, 20 Jun 2005 09:41:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DkMWV-00021v-Ox for idr@megatron.ietf.org; Mon, 20 Jun 2005 09:41:11 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28254 for ; Mon, 20 Jun 2005 09:41:10 -0400 (EDT) Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DkMuB-0001cH-Px for idr@ietf.org; Mon, 20 Jun 2005 10:05:43 -0400 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 j5KDewBm028488; Mon, 20 Jun 2005 06:40:58 -0700 (PDT) (envelope-from yakov@juniper.net) Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j5KDeqj73105; Mon, 20 Jun 2005 06:40:52 -0700 (PDT) (envelope-from yakov@juniper.net) Message-Id: <200506201340.j5KDeqj73105@merlot.juniper.net> To: idr@ietf.org Subject: [Idr] IDR WG agenda MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <95945.1119274852.1@juniper.net> Date: Mon, 20 Jun 2005 06:40:52 -0700 From: Yakov Rekhter X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Cc: skh@nexthop.com, yakov@juniper.net X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Folks, Its about time to start thinking about agenda items for the next IETF. Please forward any IDR agenda items you might have to me and Sue. And if you plan to make a presentation, please also keep in mind the rule "no document - no time slot". Sue & Yakov. _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id JAA07524 for ; Fri, 10 Jun 2005 09:07:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DgjDF-0000HF-LB; Fri, 10 Jun 2005 09:06:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DgjDD-0000Ei-QI for idr@megatron.ietf.org; Fri, 10 Jun 2005 09:06:15 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17992 for ; Fri, 10 Jun 2005 09:06:13 -0400 (EDT) Received: from colo-dns-ext1.juniper.net ([207.17.137.57]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DgjYr-00075R-Eu for idr@ietf.org; Fri, 10 Jun 2005 09:28:39 -0400 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id j5AD64906461 for ; Fri, 10 Jun 2005 06:06:04 -0700 (PDT) (envelope-from yakov@juniper.net) Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j5AD5xe06718 for ; Fri, 10 Jun 2005 06:05:59 -0700 (PDT) (envelope-from yakov@juniper.net) Message-Id: <200506101305.j5AD5xe06718@merlot.juniper.net> To: idr@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <17310.1118408758.1@juniper.net> Date: Fri, 10 Jun 2005 06:05:59 -0700 From: Yakov Rekhter X-Spam-Score: 0.0 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Subject: [Idr] Internet Draft submission Cutoff Dates X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org fyi ------- Forwarded Message Date: Fri, 10 Jun 2005 00:00:01 -0400 From: ietf-secretariat@ietf.org To: ietf-announce@ietf.org Subject: Internet-Drafts Submission Cutoff Dates for the 63rd IETF Meeting in P aris, France There are two (2) Internet-Draft cutoff dates for the 63rd IETF Meeting in Paris, France: July 11th: Cutoff Date for Initial (i.e., version -00) Internet-Draft Submissions All initial Internet-Drafts (version -00) must be submitted by Monday, July 11th at 9:00 AM ET. As always, all initial submissions with a filename beginning with "draft-ietf" must be approved by the appropriate WG Chair before they can be processed or announced. The Secretariat would appreciate receiving WG Chair approval by Tuesday, July 5th at 9:00 AM ET. July 18th: Cutoff Date for Revised (i.e., version -01 and higher) Internet-Draft Submissions All revised Internet-Drafts (version -01 and higher) must be submitted by Monday, July 18th at 9:00 AM ET. Initial and revised Internet-Drafts received after their respective cutoff dates will not be made available in the Internet-Drafts directory or announced until on or after Monday, August 1st at 9:00 AM ET, when Internet-Draft posting resumes. Please do not wait until the last minute to submit. PLEASE NOTE THE CHANGE OF PROCEDURE: If you submit an initial or revised Internet-Draft after their respective cutoff deadlines, then your document will be retained and posted when Internet-Draft processing resumes. You will no longer be required to resubmit the document. Thank you for your understanding and cooperation. If you have any questions or concerns, then please send a message to internet-drafts@ietf.org. The IETF Secretariat FYI: The Internet-Draft cutoff dates as well as other significant dates for the 63rd IETF Meeting can be found at http://www.ietf.org/meetings/cutoff_d ates_63.html. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce ------- End of Forwarded Message _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id GAA15541 for ; Mon, 6 Jun 2005 06:09:40 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DfEW5-0000JE-0G; Mon, 06 Jun 2005 06:07:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DfEW3-0000Iy-56 for idr@megatron.ietf.org; Mon, 06 Jun 2005 06:07:31 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15564 for ; Mon, 6 Jun 2005 06:07:28 -0400 (EDT) Received: from galaxy.systems.pipex.net ([62.241.162.31]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DfEqr-000581-U3 for idr@ietf.org; Mon, 06 Jun 2005 06:29:02 -0400 Received: from pc6 (1Cust154.tnt109.lnd4.gbr.da.uu.net [62.188.172.154]) by galaxy.systems.pipex.net (Postfix) with SMTP id 58FB5E000155; Mon, 6 Jun 2005 11:07:16 +0100 (BST) Message-ID: <02f901c56a76$7e2eab00$0601a8c0@pc6> From: "Tom Petch" To: "saravana kumar" , "idr" References: <20050605161237.21066.qmail@web33715.mail.mud.yahoo.com> Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) Date: Mon, 6 Jun 2005 10:59:19 +0200 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.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Score: 0.1 (/) X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4 Content-Transfer-Encoding: 7bit Cc: X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tom Petch List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org I think you should do what the I-D says if you wish to interoperate with other implementations:-). The issue, which I think lay behind your initial question, is that depending on how you choose to set up the fsm, some events are unlikely to occur (I hesitate to say cannot without spending more time thinking about it). In particular, it is BGP identifier, usually from the OPEN message, that you must use to identify which peer wins a collision. s6.8 defines what a connection collision is in terms of source and destination IP address so, at TCP SYN time, you see a collision coming but then have to track the progress of the TCP connection until you find out what you do about it and ensure the BGP peer has the information to take the same decision as you ie, assuming no errors, you should send SYN-ACK and OPEN and then NOTIFICATION on the one that is to be closed. Quite how you do this is up to you. One constraint is that the bgp4-mib has a peer table indexed by remote ip address with fsm state in it which pushes you towards having one fsm per remote ip address/peer as far as possible. You will find the fsm discussed in the idr archives, at least from Jan2002 to Nov2003; the issue of how many fsm to have crops up several times, eg in January, July and September 2002. To quote one suggestion (not quite the wording we ended up with) An instance of an FSM is created by a BGP speaker for each configured peer. It may also be created dynamically when an incoming transport connection is reported, there's no matching configured peer and the speaker is configured to accept such connections This, as another post says, is a temporary breach of the idea that BGP limits you to a single connection between a pair of ip addresses and that there is one fsm associated with it Tom Petch ----- Original Message ----- From: "saravana kumar" To: "Tom Petch" ; Sent: Sunday, June 05, 2005 6:12 PM Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) > Thanks for your response. > > I am deriving : > > on detecting an inbound connection attempt : > 1) In the connect state, continue to be in the > connect state; process the new connection with a new > fsm in active state. I am not sure you could 'choose' > to close the outbound connection fsm as that would > cause > both sides to potentially close the connection same > way. > > 2) In the active state ( no outbound connection > pending ), associate the inbound connection with the > current fsm. > > Question : Suppose unconfigured peers were never > allowed by the draft (as i suppose is reality), is it > correct to say that one could've used source tcp > address comparison as a means to break the tie as soon > as it is detected? (assuming both sides use this > mechanism). > > -skumar. /listinfo/idr _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id MAA09642 for ; Sun, 5 Jun 2005 12:13:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dexk5-0006H8-GM; Sun, 05 Jun 2005 12:12:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dexk3-0006Gz-JZ for idr@megatron.ietf.org; Sun, 05 Jun 2005 12:12:51 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15976 for ; Sun, 5 Jun 2005 12:12:49 -0400 (EDT) Received: from web33715.mail.mud.yahoo.com ([68.142.201.212]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Dey4f-00028V-2E for idr@ietf.org; Sun, 05 Jun 2005 12:34:13 -0400 Received: (qmail 21068 invoked by uid 60001); 5 Jun 2005 16:12:37 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=stDtzAJ4y+OTTowPGjeV5u1jT73vxc1gtcNFyQKaUkaZiYTSofT1VRHWtqm/ZiBu72uV/CJOoAVkuqN2l08yHWXlHHhzHht5VSr7R49rLwaUB4ZiRqp1UypoVAMHxhuJ4wE5bnlYgGbRfP92NZRrRihkIC1zI5OsqyYQrB0oIjY= ; Message-ID: <20050605161237.21066.qmail@web33715.mail.mud.yahoo.com> Received: from [209.78.40.100] by web33715.mail.mud.yahoo.com via HTTP; Sun, 05 Jun 2005 09:12:37 PDT Date: Sun, 5 Jun 2005 09:12:37 -0700 (PDT) From: saravana kumar Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) To: Tom Petch , idr@ietf.org In-Reply-To: <004701c569a7$c215f140$0601a8c0@pc6> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.5 (/) X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8 Content-Transfer-Encoding: 8bit Cc: X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Thanks for your response. I am deriving : on detecting an inbound connection attempt : 1) In the connect state, continue to be in the connect state; process the new connection with a new fsm in active state. I am not sure you could 'choose' to close the outbound connection fsm as that would cause both sides to potentially close the connection same way. 2) In the active state ( no outbound connection pending ), associate the inbound connection with the current fsm. Question : Suppose unconfigured peers were never allowed by the draft (as i suppose is reality), is it correct to say that one could've used source tcp address comparison as a means to break the tie as soon as it is detected? (assuming both sides use this mechanism). -skumar. --- Tom Petch wrote: > Probably two connections. Event 17 in the Connect > state should have been > preceded by Event 14 TcpConnection_Valid in Connect > state, most likely with > DelayOpenTimer running. > > But the intention of this fsm is to model all that > happens between a particular > pair of configured peers with a single fsm at each > end. (Modelling each > connection between a particular pair of peers as an > fsm requires a different set > of events and states; it was discussed but would > have greater changes to the > existing specification which was not considered > within the remit of the WG). > The challenge then is, as discussed in 8.2.1, that > the identifier of the peer is > not known until OPENs are exchanged, so each tcp > connection may start as a > separate fsm and then when it becomes apparent that > there is already an fsm for > this peer, 6.8 BGP connection collision detection > comes into play and you end > up with one. But you are not required to implement > it this way as long as the > appearance you present conforms with the > specification. You may choose to know > from the TCP SYN that this packet relates to an > existing fsm and not create a > second. > > As with any fsm, it is a matter of judgement what > states there are, what events > there are. What you see is considered the best > compromise. Read section 8.2.1 > carefully; it says what there is to be said. > > Tom Petch > > ----- Original Message ----- > From: "saravana kumar" > To: "Tom Petch" ; > > Sent: Thursday, June 02, 2005 11:22 PM > Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: > active state (page 61) > > > > correction: Read that as Event 17. > > -skumar. > > --- Tom Petch wrote: > > > > > I don't follow you here. Event 16 I would > regard as > > > outbound connection > > > complete; I sent SYN, received SYN-ACK and sent > ACK > > > (TCP three-way handshake). > > > Connection established, I send BGP OPEN (or > start > > > the DelayOpen timer); I don't > > > see a second connection. > > > > > > Tom Petch > > > > > > ----- Original Message ----- > > > From: "saravana kumar" > > > > To: "Tom Petch" ; > > > > > > Sent: Thursday, June 02, 2005 4:35 PM > > > Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: > > > active state (page 61) > > > > > > > In the connect state, if Event 16 happens > (inbound > > > > connection was successful), the draft suggests > > > > "sending an open or start open delay timer." > > > > > > > > Aren't there two connections (fsms ) to track > here > > > : > > > > one for the pending outbound connection and > the > > > > inbound connection? > > > > > > > > Thanks, > > > > -skumar. > > > > > > > > > > > > > > > > > > > > > > > __________________________________ > > Discover Yahoo! > > Get on-the-go sports scores, stock quotes, news > and more. Check it out! > > http://discover.yahoo.com/mobile.html > > > > _______________________________________________ > > Idr mailing list > > Idr@ietf.org > > https://www1.ietf.org/mailman/listinfo/idr > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id FAA26614 for ; Sun, 5 Jun 2005 05:29:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DerPu-0006CL-MF; Sun, 05 Jun 2005 05:27:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DerPs-0006CG-OA for idr@megatron.ietf.org; Sun, 05 Jun 2005 05:27:36 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23961 for ; Sun, 5 Jun 2005 05:27:34 -0400 (EDT) Received: from ranger.systems.pipex.net ([62.241.162.32]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DerkU-0003Qe-Nh for idr@ietf.org; Sun, 05 Jun 2005 05:48:55 -0400 Received: from pc6 (1Cust104.tnt13.lnd4.gbr.da.uu.net [62.188.142.104]) by ranger.systems.pipex.net (Postfix) with SMTP id 097AAE00028A; Sun, 5 Jun 2005 10:27:23 +0100 (BST) Message-ID: <004701c569a7$c215f140$0601a8c0@pc6> From: "Tom Petch" To: "saravana kumar" , References: <20050602212214.84988.qmail@web33704.mail.mud.yahoo.com> Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) Date: Sun, 5 Jun 2005 10:20:06 +0200 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.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Score: 0.1 (/) X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8 Content-Transfer-Encoding: 7bit Cc: X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tom Petch List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Probably two connections. Event 17 in the Connect state should have been preceded by Event 14 TcpConnection_Valid in Connect state, most likely with DelayOpenTimer running. But the intention of this fsm is to model all that happens between a particular pair of configured peers with a single fsm at each end. (Modelling each connection between a particular pair of peers as an fsm requires a different set of events and states; it was discussed but would have greater changes to the existing specification which was not considered within the remit of the WG). The challenge then is, as discussed in 8.2.1, that the identifier of the peer is not known until OPENs are exchanged, so each tcp connection may start as a separate fsm and then when it becomes apparent that there is already an fsm for this peer, 6.8 BGP connection collision detection comes into play and you end up with one. But you are not required to implement it this way as long as the appearance you present conforms with the specification. You may choose to know from the TCP SYN that this packet relates to an existing fsm and not create a second. As with any fsm, it is a matter of judgement what states there are, what events there are. What you see is considered the best compromise. Read section 8.2.1 carefully; it says what there is to be said. Tom Petch ----- Original Message ----- From: "saravana kumar" To: "Tom Petch" ; Sent: Thursday, June 02, 2005 11:22 PM Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) > correction: Read that as Event 17. > -skumar. > --- Tom Petch wrote: > > > I don't follow you here. Event 16 I would regard as > > outbound connection > > complete; I sent SYN, received SYN-ACK and sent ACK > > (TCP three-way handshake). > > Connection established, I send BGP OPEN (or start > > the DelayOpen timer); I don't > > see a second connection. > > > > Tom Petch > > > > ----- Original Message ----- > > From: "saravana kumar" > > To: "Tom Petch" ; > > > > Sent: Thursday, June 02, 2005 4:35 PM > > Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: > > active state (page 61) > > > > > In the connect state, if Event 16 happens (inbound > > > connection was successful), the draft suggests > > > "sending an open or start open delay timer." > > > > > > Aren't there two connections (fsms ) to track here > > : > > > one for the pending outbound connection and the > > > inbound connection? > > > > > > Thanks, > > > -skumar. > > > > > > > > > > > > > > __________________________________ > Discover Yahoo! > Get on-the-go sports scores, stock quotes, news and more. Check it out! > http://discover.yahoo.com/mobile.html > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www1.ietf.org/mailman/listinfo/idr _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id RAA27474 for ; Thu, 2 Jun 2005 17:25:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ddx94-0001rD-HL; Thu, 02 Jun 2005 17:22:30 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ddx92-0001r6-WB for idr@megatron.ietf.org; Thu, 02 Jun 2005 17:22:29 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02354 for ; Thu, 2 Jun 2005 17:22:26 -0400 (EDT) Received: from web33704.mail.mud.yahoo.com ([68.142.201.201]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DdxT4-0001lx-GT for idr@ietf.org; Thu, 02 Jun 2005 17:43:15 -0400 Received: (qmail 84990 invoked by uid 60001); 2 Jun 2005 21:22:14 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=lygfplzWVVH/yC6Rp7LFJQAEu1buSzNHW/NJEi70jUKNgoYUn40cy/lgSlPnE3d5xy6FqM9ndYIq0hLOw43lvHAn8jWf7Hmi5jhD0olunAdyXQ0OMFg1hethhCnvKsLaZtqlpAp6f/gRR/suWPXvZ6TcFR8XtPKnRkdB/WuJ0NA= ; Message-ID: <20050602212214.84988.qmail@web33704.mail.mud.yahoo.com> Received: from [209.78.40.100] by web33704.mail.mud.yahoo.com via HTTP; Thu, 02 Jun 2005 14:22:13 PDT Date: Thu, 2 Jun 2005 14:22:13 -0700 (PDT) From: saravana kumar Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) To: Tom Petch , idr@ietf.org In-Reply-To: <005201c5679a$4067dbe0$0601a8c0@pc6> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.5 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Content-Transfer-Encoding: 8bit Cc: X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org correction: Read that as Event 17. -skumar. --- Tom Petch wrote: > I don't follow you here. Event 16 I would regard as > outbound connection > complete; I sent SYN, received SYN-ACK and sent ACK > (TCP three-way handshake). > Connection established, I send BGP OPEN (or start > the DelayOpen timer); I don't > see a second connection. > > Tom Petch > > ----- Original Message ----- > From: "saravana kumar" > To: "Tom Petch" ; > > Sent: Thursday, June 02, 2005 4:35 PM > Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: > active state (page 61) > > > In the connect state, if Event 16 happens (inbound > > connection was successful), the draft suggests > > "sending an open or start open delay timer." > > > > Aren't there two connections (fsms ) to track here > : > > one for the pending outbound connection and the > > inbound connection? > > > > Thanks, > > -skumar. > > > > > __________________________________ Discover Yahoo! Get on-the-go sports scores, stock quotes, news and more. Check it out! http://discover.yahoo.com/mobile.html _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id OAA22360 for ; Thu, 2 Jun 2005 14:48:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DduhU-00081T-Su; Thu, 02 Jun 2005 14:45:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DduhS-00081I-LG for idr@megatron.ietf.org; Thu, 02 Jun 2005 14:45:50 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15807 for ; Thu, 2 Jun 2005 14:45:48 -0400 (EDT) Received: from galaxy.systems.pipex.net ([62.241.162.31]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ddv1W-00057C-5a for idr@ietf.org; Thu, 02 Jun 2005 15:06:35 -0400 Received: from pc6 (1Cust241.tnt28.lnd4.gbr.da.uu.net [62.188.156.241]) by galaxy.systems.pipex.net (Postfix) with SMTP id 06ABEE000132; Thu, 2 Jun 2005 19:45:36 +0100 (BST) Message-ID: <005201c5679a$4067dbe0$0601a8c0@pc6> From: "Tom Petch" To: "saravana kumar" , References: <20050602143556.3866.qmail@web33708.mail.mud.yahoo.com> Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) Date: Thu, 2 Jun 2005 19:40:12 +0200 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.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Score: 0.1 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Content-Transfer-Encoding: 7bit Cc: X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tom Petch List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org I don't follow you here. Event 16 I would regard as outbound connection complete; I sent SYN, received SYN-ACK and sent ACK (TCP three-way handshake). Connection established, I send BGP OPEN (or start the DelayOpen timer); I don't see a second connection. Tom Petch ----- Original Message ----- From: "saravana kumar" To: "Tom Petch" ; Sent: Thursday, June 02, 2005 4:35 PM Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) > In the connect state, if Event 16 happens (inbound > connection was successful), the draft suggests > "sending an open or start open delay timer." > > Aren't there two connections (fsms ) to track here : > one for the pending outbound connection and the > inbound connection? > > Thanks, > -skumar. > _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id KAA14169 for ; Thu, 2 Jun 2005 10:37:02 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ddqnq-0004x0-Ed; Thu, 02 Jun 2005 10:36:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ddqno-0004sn-S1 for idr@megatron.ietf.org; Thu, 02 Jun 2005 10:36:09 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21104 for ; Thu, 2 Jun 2005 10:36:06 -0400 (EDT) Received: from web33708.mail.mud.yahoo.com ([68.142.201.205]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Ddr7p-0000kk-ED for idr@ietf.org; Thu, 02 Jun 2005 10:56:51 -0400 Received: (qmail 3868 invoked by uid 60001); 2 Jun 2005 14:35:56 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=adoID0oqsFnsVrjz1JY+2DTv/vxFE5RMjCTLGY3KMLK/+uLpmv1p3IV/4pOkneqxCNrkW/lb8OmWbocRmsmsjFc52V0Y7u1reKkxo+BVWKK708nEPF68dRe+kzzBRP7zYHfKja9TlCZyTD8RM9wVs10VAEyll3mKHaQNAf22ckc= ; Message-ID: <20050602143556.3866.qmail@web33708.mail.mud.yahoo.com> Received: from [209.78.40.100] by web33708.mail.mud.yahoo.com via HTTP; Thu, 02 Jun 2005 07:35:56 PDT Date: Thu, 2 Jun 2005 07:35:56 -0700 (PDT) From: saravana kumar Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) To: Tom Petch , idr@ietf.org In-Reply-To: <029901c56752$f8ea21c0$0601a8c0@pc6> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.5 (/) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 Content-Transfer-Encoding: 8bit Cc: X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Thanks, I realized that, but Event 18 ( TCP connection fail detection by local TCP machinery ) is what gets us to active state. So an outbound connection success after this point seems not likely. Another question along the same lines : In the connect state, if Event 16 happens (inbound connection was successful), the draft suggests "sending an open or start open delay timer." Aren't there two connections (fsms ) to track here : one for the pending outbound connection and the inbound connection? Thanks, -skumar. --- Tom Petch wrote: > Possible, perhaps not valid, depending on your > implementation and what's > happening at the other end. > > Note that Active state is the bucket into which > things fall, so while the normal > way there is from Idle, you can also get there from > Connect state or Open Sent > state after a failure. If, in such transitions, you > wipe all traces from your > memory of having sent a TCP SYN, then the SYN-ACK > could appear out of the blue > as an invalid packet and be discarded. But if you > remember that while in > Connect state you sent a SYN and are now getting a > second SYN-ACK - perhaps the > ACK and OPEN you sent got lost - then that could > count as a further event 16. > So you certainly can receive a SYN-ACK in Active > state but your TCP processing > might not let it get to the BGP machine. > > Tom Petch > > ----- Original Message ----- > From: "saravana kumar" > To: > Sent: Wednesday, June 01, 2005 9:52 PM > Subject: [Idr] draft-ietf-idr-bgp4-26.txt: active > state (page 61) > > > > Hi, > > The Active State on the draft reads : > > "In response to a TCP connection succeeding (Event > 16 > > or Event 17)" > > > > I am assuming in Active State there is no > pending > > outbound connection attempt. > > > > If this assumption is correct, then is Event 16 > > Tcp_CR_Acked really valid/possible in active > state? > > > > I apologize if this question has been answered > > already, i couldn't locate in the archives. > > > > Thanks, > > skumar. > > > > > > > > __________________________________ > > Discover Yahoo! > > Get on-the-go sports scores, stock quotes, news > and more. Check it out! > > http://discover.yahoo.com/mobile.html > > > > _______________________________________________ > > Idr mailing list > > Idr@ietf.org > > https://www1.ietf.org/mailman/listinfo/idr > > __________________________________ Discover Yahoo! Use Yahoo! to plan a weekend, have fun online and more. Check it out! http://discover.yahoo.com/ _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id GAA05736 for ; Thu, 2 Jun 2005 06:17:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ddmjy-0003Q8-Bh; Thu, 02 Jun 2005 06:15:54 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ddmjw-0003Nz-F2 for idr@megatron.ietf.org; Thu, 02 Jun 2005 06:15:52 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26238 for ; Thu, 2 Jun 2005 06:15:49 -0400 (EDT) Received: from astro.systems.pipex.net ([62.241.163.6]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ddn3v-0003fO-RB for idr@ietf.org; Thu, 02 Jun 2005 06:36:33 -0400 Received: from pc6 (1Cust159.tnt3.lnd4.gbr.da.uu.net [62.188.132.159]) by astro.systems.pipex.net (Postfix) with SMTP id B148EE000065; Thu, 2 Jun 2005 11:15:22 +0100 (BST) Message-ID: <029901c56752$f8ea21c0$0601a8c0@pc6> From: "Tom Petch" To: "saravana kumar" , References: <20050601195233.50617.qmail@web33702.mail.mud.yahoo.com> Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) Date: Thu, 2 Jun 2005 10:24:10 +0200 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.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Score: 2.9 (++) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Content-Transfer-Encoding: 7bit Cc: X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tom Petch List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Possible, perhaps not valid, depending on your implementation and what's happening at the other end. Note that Active state is the bucket into which things fall, so while the normal way there is from Idle, you can also get there from Connect state or Open Sent state after a failure. If, in such transitions, you wipe all traces from your memory of having sent a TCP SYN, then the SYN-ACK could appear out of the blue as an invalid packet and be discarded. But if you remember that while in Connect state you sent a SYN and are now getting a second SYN-ACK - perhaps the ACK and OPEN you sent got lost - then that could count as a further event 16. So you certainly can receive a SYN-ACK in Active state but your TCP processing might not let it get to the BGP machine. Tom Petch ----- Original Message ----- From: "saravana kumar" To: Sent: Wednesday, June 01, 2005 9:52 PM Subject: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) > Hi, > The Active State on the draft reads : > "In response to a TCP connection succeeding (Event 16 > or Event 17)" > > I am assuming in Active State there is no pending > outbound connection attempt. > > If this assumption is correct, then is Event 16 > Tcp_CR_Acked really valid/possible in active state? > > I apologize if this question has been answered > already, i couldn't locate in the archives. > > Thanks, > skumar. > > > > __________________________________ > Discover Yahoo! > Get on-the-go sports scores, stock quotes, news and more. Check it out! > http://discover.yahoo.com/mobile.html > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www1.ietf.org/mailman/listinfo/idr _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id AAA24050 for ; Thu, 2 Jun 2005 00:32:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DdhJR-0002xU-8e; Thu, 02 Jun 2005 00:28:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DdhJQ-0002xP-KV for idr@megatron.ietf.org; Thu, 02 Jun 2005 00:28:08 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09207 for ; Thu, 2 Jun 2005 00:28:05 -0400 (EDT) Received: from web60723.mail.yahoo.com ([209.73.178.211]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DdhdJ-0002yU-LY for idr@ietf.org; Thu, 02 Jun 2005 00:48:46 -0400 Received: (qmail 74891 invoked by uid 60001); 2 Jun 2005 04:27:54 -0000 Message-ID: <20050602042754.74889.qmail@web60723.mail.yahoo.com> Received: from [66.17.149.13] by web60723.mail.yahoo.com via HTTP; Thu, 02 Jun 2005 00:27:54 EDT Date: Thu, 2 Jun 2005 00:27:54 -0400 (EDT) From: Tulip Rasputin To: idr@ietf.org In-Reply-To: <20050601195233.50617.qmail@web33702.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 2.9 (++) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: 8bit Subject: [Idr] Route Origin Community in *-bgp-ext-communities-08.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Hi, Is the Route Origin Community defined in draft-ietf-idr-bgp-ext-communities-08.txt the same as the Site Of Origin that is explained in a lot of online and regular BGP/MPLS VPN documentation? If not, then I would appreciate if somebody could point me to an IETF doc that tells more about SOO in terms of IANA values, etc. Thanks, Tulip __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id PAA06910 for ; Wed, 1 Jun 2005 15:57:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DdZGf-0006C3-BE; Wed, 01 Jun 2005 15:52:45 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DdZGd-0006Bx-UV for idr@megatron.ietf.org; Wed, 01 Jun 2005 15:52:43 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22114 for ; Wed, 1 Jun 2005 15:52:41 -0400 (EDT) Received: from web33702.mail.mud.yahoo.com ([68.142.201.199]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DdZaV-0007FR-Oq for idr@ietf.org; Wed, 01 Jun 2005 16:13:17 -0400 Received: (qmail 50619 invoked by uid 60001); 1 Jun 2005 19:52:33 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=kdHT79fVIMbY2TQBvncm2e+fZn/4TNIO8AwfM7eBaUrK6qHJXu2NTX4kCpPc3LKUlhJj/tNN+qzPJPsFCdNil2GB7HAmGDC1mgqiIOSEYeU2YjKDG1CN5wBU1MlP+7Ebs1mitm3NvLFKcMUkLiBqyEosQMnM7/KvwNjoPDCPFu0= ; Message-ID: <20050601195233.50617.qmail@web33702.mail.mud.yahoo.com> Received: from [209.78.40.100] by web33702.mail.mud.yahoo.com via HTTP; Wed, 01 Jun 2005 12:52:32 PDT Date: Wed, 1 Jun 2005 12:52:32 -0700 (PDT) From: saravana kumar To: idr@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.5 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Content-Transfer-Encoding: 8bit Subject: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Hi, The Active State on the draft reads : "In response to a TCP connection succeeding (Event 16 or Event 17)" I am assuming in Active State there is no pending outbound connection attempt. If this assumption is correct, then is Event 16 Tcp_CR_Acked really valid/possible in active state? I apologize if this question has been answered already, i couldn't locate in the archives. Thanks, skumar. __________________________________ Discover Yahoo! Get on-the-go sports scores, stock quotes, news and more. Check it out! http://discover.yahoo.com/mobile.html _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr