Re: [Netconf] #1: message-id attribute not used

[Andy Bierman <ietf@andybierman.com>]

Netconf wrote:
> #1: message-id attribute not used
> -----------------------------------+----------------------------------------
>   Reporter:  ietf@andybierman.com  |       Owner:            
>       Type:  defect                |      Status:  new       
>   Priority:  minor                 |   Milestone:  milestone1
>  Component:  RFC4741               |     Version:  1.0       
> Resolution:                        |    Keywords:  message-id
> -----------------------------------+----------------------------------------
> Comment (by balazs.lengyel@ericsson.com):
>
>  We do want to use it. We want to send notifications about long running
>  operations like backup. We will identify the original operation using the
>  message-id.
>  It could also be useful for logging, to pair the request and the answer.
>  [[BR]]
>  Please do not remove it.

You misunderstand. I did not make the ticket clear enough.
The 'message-id' attribute is not being removed.  The requirement
to generate an error and reject the <rpc> request if it is missing
is being removed.

The agent is already required to return every attribute in <rpc>
unchanged in the <rpc-reply> anyway.  The message-id rule is redundant.
(Phil already explained it all to us, remember?)

>  [[BR]]
>  Balazs Lengyel

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/>