[AVTCORE] Re: I-D Action: draft-lennox-sdp-raw-key-fingerprints-00.txt

[Roman Shpount <[e-mail]>]

Hi Jonathan,

I do support this draft since it will simplify and optimize common WebRTC
use cases.

This draft should take into account RFC 8842 and tls-id use in addition to
connection:new/existing.

Best Regards,
_____________
Roman Shpount


On Fri, Oct 18, 2024 at 5:32 PM Jonathan Lennox <jonathan.lennox=
[e-mail]> wrote:

> Hi, all —
>
> I have submitted this draft defining how to use raw public keys (rather
> than self-signed certificates) in TLS or DTLS negotiated with SDP, with of
> course the specific use case in mind of SDP-negotiated DTLS/SRTP such as is
> used in WebRTC.
>
> Comments are welcome, as well as any suggestions as to the best forum in
> which to develop this work; the base TLS in SDP (i.e. “a=fingerprint”) work
> was done in MMUSIC, but that group is closing down.
>
> Thank you!
>
> > On Oct 18, 2024, at 5:15 PM, [e-mail] wrote:
> >
> > Internet-Draft draft-lennox-sdp-raw-key-fingerprints-00.txt is now
> available.
> >
> >   Title:   Session Description Protocol Fingerprints for Raw Public Keys
> in (Datagram) Transport Layer Security
> >   Author:  Jonathan Lennox
> >   Name:    draft-lennox-sdp-raw-key-fingerprints-00.txt
> >   Pages:   9
> >   Dates:   2024-10-18
> >
> > Abstract:
> >
> >   This document defines how to negotiate the use of raw keys for TLS
> >   and DTLS with the Session Description Protocol (SDP).  Raw keys are
> >   more efficient than certificates for typical uses of TLS and DTLS
> >   negotiated with SDP, without loss of security.
> >
> > The IETF datatracker status page for this Internet-Draft is:
> > https://datatracker.ietf.org/doc/draft-lennox-sdp-raw-key-fingerprints/
> >
> > There is also an HTML version available at:
> >
> https://www.ietf.org/archive/id/draft-lennox-sdp-raw-key-fingerprints-00.html
> >
> > Internet-Drafts are also available by rsync at:
> > rsync.ietf.org::internet-drafts
> >
> >
>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> To unsubscribe send an email to [e-mail]
>