PCP Considerations for WebRTC Usage
draft-penno-rtcweb-pcp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Reinaldo Penno , Tirumaleswar Reddy.K , Dan Wing , Mohamed Boucadair | ||
| Last updated | 2013-11-25 (Latest revision 2013-05-24) | ||
| 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 document describes the motivations for WebRTC applications to be PCP-aware and the benefits provided by PCP-capable NATs and Firewalls.
Authors
Reinaldo Penno
Tirumaleswar Reddy.K
Dan Wing
Mohamed Boucadair
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)