Re: [Netconf] Netconf Notification: One last bit of Discuss: Session Accumulation
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Netconf] Netconf Notification: One last bit of Discuss: Session Accumulation



Sharon Chisholm wrote:
> Hi
> 
> That version works for me.
> 

My concern is that is seems to imply that
an agent is going to support multiple, concurrent
notification subscriptions on the same session.
The WG never agreed to this feature.

Does this text refer to 1 subscription on each session,
or N subscriptions on 1 session, or both?  (A: yes ;-)

In my (even recent experience), when the standard is silent
on a subject, it is harder to interpret the specification incorrectly.
However, when a standard is *almost* silent (i.e., partially specified)
then it is very easy for people to interpret the standard incorrectly,
in N different ways.

It should be clear that the standard does not define what
happens when a <create-subscription> is received on a session
while in notification mode already.  Some vendors want to utilize
this feature, and I think they should be able to experiment.
Vendors who reject <create-subscription> requests while in
notification mode are also compliant to the standard.


> Sharon 

Andy


> 
> -----Original Message-----
> From: Juergen Schoenwaelder
> [mailto:j.schoenwaelder at jacobs-university.de] 
> Sent: Monday, June 16, 2008 1:10 PM
> To: Chisholm, Sharon (CAR:ZZ00)
> Cc: netconf at ietf.org
> Subject: Re: [Netconf] Netconf Notification: One last bit of Discuss:
> Session Accumulation
> 
> On Mon, Jun 16, 2008 at 07:52:51AM -0400, Sharon Chisholm wrote:
>  
>> If a malicious or buggy NETCONF client sends a number of 
>> <create-subscription> requests  without ever terminating any of them, 
>> they will accumulate subscriptions and begin to use up system
> resources.
>> They do so while accumulating NETCONF sessions and when the underlying
> 
>> NETCONF session is terminated, so is the Notification subscription. 
>> The <kill-session> operation should be used to terminate any suspect 
>> NETCONF sessions.
> 
> I do not understand the second sentence. And who is "they" in the first
> sentence? What about this wording:
> 
>   If a malicious or buggy NETCONF client sends a number of
>   <create-subscription> requests, then these subscriptions accumulate
>   and may use up system resources. In such a situation, subscriptions
>   can be terminated by terminating the suspect underlying NETCONF
>   sessions using the <kill-session> operation.
> 
> /js
> 


_______________________________________________
Netconf mailing list
Netconf at ietf.org
https://www.ietf.org/mailman/listinfo/netconf



Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.