Port Control Protocol (PCP) Failure Scenarios
draft-boucadair-pcp-failure-02
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
---|---|---|---|
Authors | Mohamed Boucadair , Francis Dupont , Reinaldo Penno | ||
Last updated | 2012-03-26 (Latest revision 2011-09-12) | ||
RFC stream | (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 identifies and analyzes several PCP failure scenarios. A procedure to retrieve the explicit dynamic mapping(s) from the PCP Server is proposed. This procedure relies upon the use of a new PCP OpCode and Option: GET/NEXT.
Authors
Mohamed Boucadair
Francis Dupont
Reinaldo Penno
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)