Re: Presentation for a call if DTLS Association be started if not requested in the offer
Christer Holmberg <[email protected]> Thu, 28 Sep 2017 14:29:10 +0000
| Newsgroups | gmane.ietf.mmusic |
|---|---|
| Message-ID | <D5F2E2BE.22E87%[email protected]> |
Hi, ... >>>>Also, I¹d like to hear your suggestion on how to handle backward >>>>compatibility with endpoints that don¹t support tls-id >>>>(read: endpoints that may trigger new DTLS association in the answer). >>>>Maybe the problem will go away one day, but I don¹t think we >>>>an just close our eyes and wait for that day to comeŠ >>> >>>Which endpoints do that? Because that's absolutely going to be forbidden >>>by JSEP. >> >>‘Legacy' RFC 5763-compliant endpoints that don¹t support tls-id. >> > Sorry, I was asking "which actual implementations do this"? I don’t know - perhaps Roman knows? Regards, Christer On Thu, Sep 28, 2017 at 11:14 AM, Roman Shpount <[email protected]> wrote: Hi All, I would also like to see if and how exactly allowing new DTLS association when not requested in the offer, contradicts JSEP. Roman Shpount On Sep 28, 2017 02:22, "Christer Holmberg" <[email protected]> wrote: Thanks Roman! I would request those that do NOT want to allow an answerer to trigger a new DTLS association to prepare a description (verbally or using slides) on how they suggest handling interoperability with legacy peers that may trigger a new DTLS association in the answer. Regards, Christer From: Roman Shpount <[email protected]> Date: Thursday 28 September 2017 at 08:37 To: Christer Holmberg <[email protected]>, "[email protected]" <[email protected]>, Ben Campbell <[email protected]>, Bernard Aboba <[email protected]>, Bo Burman <[email protected]>, Eric Rescorla <[email protected]>, Flemming Andreasen <[email protected]>, Jonathan Lennox <[email protected]>, Justin Uberti <[email protected]>, "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Subject: Presentation for a call if DTLS Association be started if not requested in the offer Hi All, Attached is the presentation for the call tomorrow (or later today) Once again, conference call information: Join the meeting: join.me/112-807-485 <http://join.me/112-807-485> <https://join.me/112-807-485> Thursday, September 28, 2017 12:00 PM Eastern Time (US & Canada) In my time zone? <https://join.me/timezone/1506614400000/1506621600000> To dial in by phone:United States - Los Angeles, CA +1.213.226.1066 <tel:%2B1.213.226.1066> <tel:+1.213.226.1066 <tel:%2B1.213.226.1066>,,112807485#> United States - New York, NY +1.646.307.1990 <tel:%2B1.646.307.1990> <tel:+1.646.307.1990 <tel:%2B1.646.307.1990>,,112807485#> United States - San Francisco, CA +1.415.594.5500 <tel:%2B1.415.594.5500> <tel:+1.415.594.5500 <tel:%2B1.415.594.5500>,,112807485#> United States - Washington, DC +1.202.602.1295 <tel:%2B1.202.602.1295> <tel:+1.202.602.1295 <tel:%2B1.202.602.1295>,,112807485#> Australia - Sydney +61.2.9191.6319 <tel:%2B61.2.9191.6319> <tel:+61.2.9191.6319 <tel:%2B61.2.9191.6319>,,112807485#> France - Paris +33.1.8288.3590 <tel:%2B33.1.8288.3590> <tel:+33.1.8288.3590 <tel:%2B33.1.8288.3590>,,112807485#> Germany - Berlin +49.30.2240.3071 <tel:+49.30.2240.3071,,112807485#> Singapore - national +65.3158.1842 <tel:+65.3158.1842,,112807485#> United Kingdom - London +44.20.3582.4515 <tel:+44.20.3582.4515,,112807485#> More phone numbers <https://join.me/intphone/112807485/0> Conference ID: 112-807-485 # Need to share screen? Download the app <https://join.me/app> Regards, _____________ Roman Shpount _______________________________________________ mmusic mailing list [email protected] https://www.ietf.org/mailman/listinfo/mmusic