XSD session-id clarification

[Andy Bierman <ietf@andybierman.com>]

Hi Rob,

I hate to make you add another change,
but I think the XSD is supposed to help automate
tool development, and the 'session-id' schema is wrong.
Zero is never a valid value for session-id in a hello
message or kill-session operation.

There are really 2 types:

SessionId  (type="unsignedInt" minInclusive="1")

SessionIdOrZero    (type="unsignedInt")


The places SessionId is used (should leave alone):

 - kill-session : session-id parameter

 - hello : session-id parameter

The place SessionId should be changed to SessionIdOrZero:

 - not in the XSD!
 - the <error-info> content for a lock-denied error is
   a session-id element (type is really SessionIdOrZero)
 - I guess we don't technically need this simpleType


If you add a minInclusive="1" restriction to the SessionId
simpleType, then the XSD will be correct (for sessionId at least ;-)



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