search

juberti / cryptex

IETF Internet-Draft for Completely Encrypting RTP Header Extensions and Contributing Sources
Other
3 stars 4 forks source link

[Lars Eggert]Markdown nit #70

Closed murillo128 closed 2 years ago

murillo128 commented 2 years ago 
     When the mechanism defined by this specification has been negotiated,
     sending a RTP packet that has any CSRCs or contains any {[RFC8285](https://datatracker.ietf.org/doc/rfc8285/)}}
     header extensions follows the steps below.  This mechanism MUST NOT
     be used with header extensions other than the [[RFC8285](https://datatracker.ietf.org/doc/rfc8285/)] variety.

Likely Markdown nit: {RFC8285}}

murillo128 commented 2 years ago

solved