>> it is already in the version number field.
> Oops! sorry ;-( I meant to say that should suffice (as a version
> exchange mechanism) since the router always sends a reset query after
> session establishment.
that part is easy:
o router sends version
o if server can sing that version, all goes ahead
o if not, server sends error and disconnects
o router tries another server
but you bring up allowing the router to ignore unknown pdu types if the
version matches. i.e. there can be new pdu types which do not have
important semantics. just so i can wrap my head, which is on first
cuppa, around this, could you give me an example? my first reaction is,
if it has no important semantics, then why add it? :)
if a sender MUST only send unimportant unknown pdus, to enforce this,
how does the recipient know if the unknown pdu type it just received is
important or not? i guess the sender can paint them grey. :)
but moving past this cloudy space, ...
how do we tell the iana that it can only add to the pdu type registry if
the version is bumped? or is it a registry of
version pdu-type
0 0
0 1
...
1 13
1 14
...
randy
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr
