PCP Server Selection
draft-ietf-pcp-server-selection-01

The information below is for an old version of the document
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 IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Reviews
Additional Resources
- Mailing list discussion
Stream WG state WG Document
Revised I-D Needed - Issue raised by WG
Document shepherd None
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
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 (mohamed.boucadair@orange.com)
Reinaldo Penno (repenno@cisco.com)
Dan Wing (dwing@cisco.com)
Prashanth Patil (praspati@cisco.com)
Tirumaleswar Reddy.K (tireddy@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)