search

juberti / cryptex

IETF Internet-Draft for Completely Encrypting RTP Header Extensions and Contributing Sources
Other
3 stars 4 forks source link

[Warren Kumari] IANA registry for "defined by profile" #95

Closed murillo128 closed 2 years ago

murillo128 commented 2 years ago

"[RFC8285] defines two values for the "defined by profile" field for carrying one-byte and two-byte header extensions." - RFC8285 defines 0XBEDE, and has a cute justification. This document defines 0xCODE and 0XC2DE... but it was quite hard to figure out what the other value that RFC8285 defined -- and that's my issue. Should this document create an IANA registry to track these? Is there already a registry? E.g: If I magically become an RTP expert and write draft-ietf-avtcode-even-more-awesome-protocol how do I know not to use any of these existing numbers?

murillo128 commented 2 years ago

I think this an issue for the RFC8285, or even for rfc3550. There is no IANA register for the "defined by profile" values, so we can't add the values specified in this doc to it.