> On 14 Feb 2022, at 16:46, Salz, Rich <[email protected]>
> wrote:
>
> I’ve tried to register ALPN for SIP/2.0 for a long time now, but fail to get
> responses and confusing ones.
>
> I don’t recall seeing the request, and I am one of the designated experts for
> the TLS registries. I wonder where you asked? [email protected]
> <mailto:[email protected]> is the place to write to. That address
> doesn’t seem to be written down anywhere well-known.
I have sent you separately our previous conversation that seemed to end in a
black hole after I wrote the draft.
>
> It seems unclear whether we need to write new RFCs for SIP in order to get a
> registration, but that seems wrong to me.
>
> The requirement is that somewhere there be a stable document. Since they
> don’t expire, an internet-draft is sufficient. More likely, if the SIP
> documents talk about TLS, and ideally mention ALPN, that’s enough, just
> mention whatever docs in your email.
There’s a draft
>
> It must be much easier to get this done.
>
> Sorry for your frustration. Perhaps the current draft could add a sentence
> giving the email address?
>
Add a clarification that for old protocols, at least a draft is needed to make
life simpler and avoid at least one round-trip :-)
/O
_______________________________________________
Uta mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/uta
