PCP Server Selection
draft-ietf-pcp-server-selection-01
| Document | Type | Expired Internet-Draft (pcp WG) | |
|---|---|---|---|
| Authors | Mohamed Boucadair , Reinaldo Penno , Dan Wing , Prashanth Patil , Tirumaleswar Reddy.K | ||
| Last updated | 2013-11-23 (Latest revision 2013-05-22) | ||
| Replaces | draft-boucadair-pcp-server-selection | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Reviews |
SECDIR Telechat review
(of
-07)
Has Issues
|
||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-ietf-pcp-server-selection-01.txt
Abstract
This document specifies the behavior to be followed by the PCP client to contact its PCP server(s) when one or several PCP server names are configured. Multiple names may be configured to a PCP client in some deployment contexts such as multi-homing. This document updates RFC6887.
Authors
Mohamed Boucadair
Reinaldo Penno
Dan Wing
Prashanth Patil
Tirumaleswar Reddy.K
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)