RE: message-id attribute issues

["Rob Enns" <rpe@juniper.net>]

> I just noticed a couple more details in the schema in prot-10:
> 
>   - the message-id is mandatory to use in the <rpc> element
>     but optional in the <rpc-reply> element.  It should also be
>     mandatory in the <rpc-reply>, since all attributes passed in
>     the <rpc> have to be copied in the <rpc-reply>.

This was done because if the client sends an <rpc> without
a message-id (which is an error), the server has to respond.

>  - the data type for this attribute is xsd:string
>    This means everyone has to accept a message-id size of 
> 65535 octets.
>    That is a bit excessive IMO.
>    Can we limit this mandatory attribute to a reasonable 
> size, like 255?

CLR? ;-) Seriously, I think implementors may find creative things
to do with message-id, and 255 could be a bit short. Every
implementation
will have a practical limit on the messages that can be received; do you
think we should limit it in the spec?

Rob

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