Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61)
"Tom Petch" <nwnetworks@dial.pipex.com> Sun, 05 June 2005 09:27 UTC
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 <idr@ietf.org>; 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 <nwnetworks@dial.pipex.com>
To: saravana kumar <skumar_saravana@yahoo.com>, idr@ietf.org
References: <20050602212214.84988.qmail@web33704.mail.mud.yahoo.com>
Subject: Re: [Idr] draft-ietf-idr-bgp4-26.txt: active state (page 61)
Date: Sun, 05 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 <nwnetworks@dial.pipex.com>
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
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 _______________________________________________ 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