Re: about Hold Time

Hwang Hyojung <jung@h2o.kotel.co.kr> Thu, 05 June 1997 06:30 UTC

From: Hwang Hyojung <jung@h2o.kotel.co.kr>
Message-Id: <199706050540.OAA03853@h2o.kotel.co.kr>
Subject: Re: about Hold Time
To: Herve Degrand <herve@gideon.bt.co.uk>
Date: Thu, 05 Jun 1997 14:40:18 +0900
Cc: bgp@ans.net
In-Reply-To: <Pine.SOL.3.95.970527075236.13174B-100000@gideon> from "Herve Degrand" at May 27, 97 08:00:02 am
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-2022-kr"
Content-Transfer-Encoding: 7
Sender: owner-idr@merit.edu
Precedence: bulk

Then, 

When the HOLD TIME is zero, the Hold Timer is not set.
And a BGP speaker thinks that the BGP connections with peers are always alive.
If the peers did not send UPDATE message, a BGP speaker think there is 
no change of routing information. 
How do a BGP speaker know that the peers are working or not ? 

According to Herve Degrand:
> 
> 
> Hello,
> 
> about Hold Time at zero, it is written in RFC 1771 =
> " Hold Time MUST be either zero or at least three seconds...
> If the negotiated Hold Time interval is zero, then periodic
> KEEPALIVE messages MUST NOT be sent... = the Hold Time timer and
> KeepAlive timers are not started."
> 
> So, you seem to be right,  BGP speaker doesn't need to send/receive
> KEEPALIVE message.
> 
> Herve
> 
> -------------------------------------------------------------
>  Herve DEGRAND   <herve@gideon.bt.co.uk>
>    BT Labs
> -------------------------------------------------------------

about Hold Time Hwang Hyojung
Re: about Hold Time Herve Degrand
Re: about Hold Time Hwang Hyojung