For the router, it's not about the time, its about the buffer space.
Configure the buffer space allowed to buffer incoming updates during
the down time. If the buffer runs out, new sesssion.
Regards,
Jakob.
-Original Message-
From: thomas.g...@swisscom.com
Sent: Wednesday, March 10, 202
Hi Tomas,
According to the RFC7854, the BMP session is closely bound to the TCP
session. So the BMP session will end when TCP is closed.
Now we want to keep the BMP session active even the TCP session is
closed, I think it means the BMP session state separate from the TCP sess
Then your proposal is not an alternative to Sriram's, but a complement. No?
Regards,
Jakob.
-Original Message-
From: Job Snijders
Sent: Wednesday, March 10, 2021 1:12 AM
To: Jakob Heitz (jheitz)
Cc: grow@ietf.org
Subject: Re: [GROW] An alternative approach to
draft-ietf-grow-route-lea
Hi Haibo,
Quite the contrary. draft-tppy-bmp-seamless-session is not about the separation
of the transport session from the BMP session. It is about to delay the
termination of the BMP session when transport session is closed and introducing
a mechanism to re-establish the BMP session.
The aut
Hi Jakob and Job,
Ack on all. I would define 60 seconds to be default and configurable.
Best wishes
Thomas
-Original Message-
From: Jakob Heitz (jheitz)
Sent: Wednesday, March 10, 2021 1:12 PM
To: Job Snijders
Cc: draft-tppy-bmp-seamless-sess...@ietf.org; grow@ietf.org
Subject: RE: [G
Hi Jakob,
Thats clear. Apology. I was not precise enough. I would prefer the reliability
to be solved on application layer than on transport layer since in a large
scale BMP data collection, multiple daemons collect the BMP messages and
failover among can occur.
Best wishes
Thomas
From: Jakob
Hi Jakob,
Ack on all. The difference between sequence numbers in TCP transport and BMP
application is clear. What I wondered if you could describe a bit more what
benefit we would gain with BMP sequence numbers. At which point within the BMP
client application loss technically could occur.
Bes
A primary use-case of the BMP data is to provide information to a route
collector/optimizer to determine what feasible paths may be sent to a router by
these offline computational systems. This requires a reliable transport where
messages are delivered in order.
I understand others may be fine
I would say 60 seconds or until the client runs out of configured buffer space
to save messages that need to be sent to the session once the new session comes
up.
Regards,
Jakob.
-Original Message-
From: Job Snijders
Sent: Wednesday, March 10, 2021 1:04 AM
To: Jakob Heitz (jheitz)
Cc
Hi Tomas,
I think the main problem is how to separate the BMP session with the
transport session. Even we choose a stateless transport, we also need to use
some mechanism to ensure the message is succeed send to the sever, e.g., use
sequence number in BMP RM message.
Regards,
Haibo
F
sed ´s/sensible/sensitive´
In pt_BR both words are "Sensível", and what defines the real meaning is
the phrase context.
Same with Safety and Security, both are "segurança" in pt_BR.
Dã... Sorry!
Em qua., 10 de mar. de 2021 às 07:16, Douglas Fischer <
fischerdoug...@gmail.com> escreveu:
> I'm no
I'm not sure about what I'm going to say... But.
BMP would transfer sensible data.
Then some cryptographic layer would be recommended/necessary.
Considering that, following on this approach of "fast connection", will not
have time/space to negotiate some crypto on those fast reconnections.
So I p
Dear Jakob,
On Wed, Mar 10, 2021 at 02:10:24AM +, Jakob Heitz (jheitz) wrote:
> Job, your suggestion kicks a different goal than
> draft-ietf-grow-route-leak-detection-mitigation does.
Yes, I'm aware I am suggesting a different approach to solve the problem
of route leaks.
> draft-ietf-grow-
On Wed, Mar 10, 2021 at 03:08:34AM +, Jakob Heitz (jheitz) wrote:
> >From the BGP speaker (client) implementation point of view,
>
> I would do it like this:
> The client keeps a ring buffer of data it sent to the server.
> The bottom of the buffer is at a certain sequence number.
> As messages
14 matches
Mail list logo
