[core] CoAP Option for Authentication Token

[Patrick Barrett <[e-mail]>]

Our company is currently in the process of porting our HTTP API over
to CoAP. With our current API we use an HTTP header (X-Exosite-CIK)
for sending an auth token and in our current CoAP implementation we're
just sending this as a query parameter. Since we'd like the option of
sending it in a raw binary value from to save bytes, it's my
understanding that this actually violates the protocol since it isn't
guaranteed to be valid UTF-8. The only two options in the main RFC
that allow opaque byte strings (If-Match and ETag) don't seem
appropriate and don't allow long enough values. I looked through the
other drafts and didn't see any that added options that seemed more
appropriate. I also looked at the IANA registry, but that seems to
only have the options from the RFC.

Is there an existing option that would be appropriate for this use? If
not what is the process for proposing one? I'm not fimilar with what
the terms "IETF Review or IESG Approval", "Specification Required", or
"Expert Review" mean. I'm willing to help in any way I can.

Thanks

-- 
Patrick Barrett  //  E X O S I T E  //  Minneapolis, MN  //  www.exosite.com