Re: notification-08 comments

[Andy Bierman <ietf@andybierman.com>]

Balazs Lengyel wrote:
> Andy Bierman wrote:
> > > On the other hand if the agent may store requests that arrived before 
> > > the replayComplete was sent you end up with a lot of other questions:
> > > - how long must an agent store rpc requests? 1 year?
> > > - how many requests must it store?
> >
> >
> > This is an artifact of TCP.
> > The bytes will be there as long as the connection (and/or session)
> > has not been dropped.
> >
> > Andy
>
> Sadly you can not use TCP buffer to store much data because:
> - The maximum receive buffer for a socket on a linux system is usually 
> (2*)87 kB. You may push that somewhat higher but a netconf manager can 
> send you MBytes of requests. The agent's receive buffer will fill up, so 
> it will not send ACK messages to the Manager. Then the manager's send 
> buffer will also fill up which might block the manager program.

We are not trying to use TCP to store a lot of data for the
agent, in this weird corner-case.  There is clear WG consensus
that the agent can process these interleaved RPC requests
if it chooses, but this is not required.


> So in notification mode the agent better read the socket and do 
> something with any arrived data, either discard it or store it in 
> application space.

No, the client will eventually block, and stop sending.
This is no different than (normal mode) where the client
sends <rpc> requests faster than the agent is sending replies.

> Balazs

Andy

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>