Its above my pay grade to decide on what to do. Ball is in your court. > We need to ask IANA for a value different from 5 and currently unassigned, > and at the same time deprecate the encoding in RFC8060.
If that is what you think, I'm fine with it. > Yes, this means as well fixing implementations that shouldn’t have used type > 5 in the first place. Yes, but be realistic. You know what this means. Implementations will accept both type values until there is enough evidence that no one uses the old type anymore. Dino _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
