> 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? :)
E.g. If and when (;-)) we add origin validation for VPN routes and we do it by adding a VPN prefix PDU. > 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. :) By definition, if it's the same version#, all unknown PDUs are unimportant... Otherwise, they are important ;-) > 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 > ... This should work if it can be done! _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
