Handling Considerations for the RTP fields in PERC
draft-westerlund-perc-rtp-field-considerations-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Magnus Westerlund | ||
| Last updated | 2016-04-21 (Latest revision 2015-10-19) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This draft discusses how the Privacy Enhanced RTP Conferencing solution will need consider the different RTP header fields in regards to both hop-by-hop and end-to-end security.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)