Re: Unknown key shares in MMUSIC

Roman Shpount <[email protected]>
Newsgroups gmane.ietf.mmusic
Message-ID <CAD5OKxtmz8cP+hmJF6bq7VTX5SOduS5=U-e17iCiAs12KOa5MQ@mail.gmail.com>
On Mon, Mar 13, 2017 at 7:48 PM, Martin Thomson <[email protected]>
wrote:

> After completely failing to remember and take into account feedback
> during the avtcore meeting last time (thanks for the reminder
> Jonathan), I would like to draw the attention of this group to this
> draft:
>
> https://datatracker.ietf.org/doc/draft-thomson-avtcore-sdp-uks/
>
> The latest version builds on the a=dtls-id work in this group.
> However, Jonathan's reminder highlighted a critical shortcoming of
> that: it only works for DTLS.  We still have uses of TLS-over-TCP that
> would not be addressed by the current iteration of the draft (though
> they would have for the previous version).
>
> One relatively simple solution is to define dtls-id as tls-id instead,
> but that's disruptive.
>
> I'd like to discuss this issue with an eye to resolving it before or
> at Chicago; I realize that there is a probably a tight agenda, but the
> outcome of that discussion might affect a very-far-advanced
> draft-ietf-mmusic-dtls-sdp-21.
>

Alternatively we can keep dtls-id the way it is currently defined and
define tls-id to be used for TLS-over-TCP  in the new draft.

I would also prefer a more generic name for the TLS extension itself. It
does not have to be related to SDP, so some sort of endpoint_id would work
better then sdp_dtls_id.

Regards,
_____________
Roman Shpount

_______________________________________________
mmusic mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/mmusic
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.