[AVTCORE] RFC 8088 and draft-ietf-avtcore-rtp-sframe

[Bernard Aboba <[e-mail]>]

This draft is attempting to provide an RTP payload format for SFrame, which
provides for E2E encryption of RTP payloads.  As such, readers (including
the IESG) will expect it to conform to RFC 8088 "How to Write an RTP
Payload Format".

https://imgflip.com/i/85y9ko

So you should expect the IESG to ask many of the same questions asked of
the SCIP RTP payload format, and to expect them to be answered in the
document. Some of the questions you might expect include:

Packetization/depacketization

Details of the packetization/depacketization process, answering questions
like:
a. Does the SFrame packetizer or depacketizer need to parse SFrame? If so,
will the packetizer/depacketizer need to be revised if the SFrame format
changes?
b.Does the packetizer/depacketizer need to keep track of the state of
SFrame key negotiation?

SDP
How is Sframe negotiated in SDP? What profiles are used?  What are the
associated SDP parameters? What are the requirements for SBCs to pass Frame
over RTP through without causing problems?

Transport
Can SFrame be negotiated along with RTP/RTCP mux and BUNDLE?

Security Considerations

What are the SFrame security services provided for RTP and RTCP?

What attacks are prevented by using SRTP (e.g. SAVP and SAVPF profiles) and
cryptex in addition to SFrame?