Re: [rtcweb] SAVPF history (Re: Final plea about SRTP)

[Roman Shpount <[e-mail]>]

On Tue, May 8, 2012 at 3:57 AM, Harald Alvestrand <[e-mail]>wrote:

> **
> On 05/04/2012 07:45 PM, Roman Shpount wrote:
>
> I used to work on hardware endpoints that have been using SAVPF since
> 2004, with hundreds of thousands of units in the field.
>
>>
> I thought SAVPF was only standardized in 2008 and AVPF was standardized in
> 2006. AVPF was discussed for a while though, so I would assumed you worked
> with something that implemented one of the drafts...
>
> The -00 version of the SAVPF draft is dated 19 October 2003.
>
> According to
> https://datatracker.ietf.org/doc/draft-ietf-avt-profile-savpf/history/publication was requested in February 2006, and it was approved by the IESG
> in November 2007. The publication delay was 3 months.
>
> The technical changes that resulted from these 4 years of work can be seen
> here:
>
>
> http://tools.ietf.org/rfcdiff?difftype=--hwdiff&url1=draft-ietf-avt-profile-savpf-00.txt&url2=draft-ietf-avt-profile-savpf-12.txt
>
>

I would say that something that changes to rfc4585 would be more relevant.
Regardless of the actual changes in the draft, my point is there are very
few actual SIP devices that implement SAVPF or AVPF. Specifying this as the
only profile supported by WebRTC will create yet another challenge to
legacy interop, since it will require not only processing of ICE messages,
and DTLS-SRTP re-encoding, but also RTCP re-generation.
_____________
Roman Shpount