PCP Server Selection
draft-boucadair-pcp-server-selection-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mohamed Boucadair , Reinaldo Penno , Dan Wing | ||
| Last updated | 2013-03-12 (Latest revision 2012-09-13) | ||
| Replaced by | draft-ietf-pcp-server-selection | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-pcp-server-selection | |
| 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 specifies the behavior to be followed by the PCP Client to contact its PCP Server(s) when one or several PCP Names are configured. Multiple Names may be configured to a PCP Client in some deployment contexts such as multi-homing.
Authors
Mohamed Boucadair
Reinaldo Penno
Dan Wing
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)