Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61)
saravana kumar <skumar_saravana@yahoo.com> Sun, 05 June 2005 16:12 UTC
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 <idr@ietf.org>; 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, 05 Jun 2005 09:12:37 -0700
From: saravana kumar <skumar_saravana@yahoo.com>
Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61)
To: Tom Petch <nwnetworks@dial.pipex.com>, 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 <idr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=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 <nwnetworks@dial.pipex.com> 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" <skumar_saravana@yahoo.com> > To: "Tom Petch" <nwnetworks@dial.pipex.com>; > <idr@ietf.org> > 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 <nwnetworks@dial.pipex.com> 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" > <skumar_saravana@yahoo.com> > > > To: "Tom Petch" <nwnetworks@dial.pipex.com>; > > > <idr@ietf.org> > > > 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. > > > > > > > <snip> > > > > > > > > > > > > > > > > __________________________________ > > 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
- [Idr] draft-ietf-idr-bgp4-26.txt: active state (p… saravana kumar
- [Idr] Route Origin Community in *-bgp-ext-communi… Tulip Rasputin
- Re: [Idr] draft-ietf-idr-bgp4-26.txt: active stat… Tom Petch
- Re: [Idr] draft-ietf-idr-bgp4-26.txt: active stat… saravana kumar
- Re: [Idr] draft-ietf-idr-bgp4-26.txt: active stat… Tom Petch
- Re: [Idr] draft-ietf-idr-bgp4-26.txt: active stat… saravana kumar
- Re: [Idr] draft-ietf-idr-bgp4-26.txt: active stat… Tom Petch
- Re: [Idr] draft-ietf-idr-bgp4-26.txt: active stat… saravana kumar
- Re: [Idr] draft-ietf-idr-bgp4-26.txt: active stat… Tom Petch