Port Control Protocol (PCP) Server Selection
RFC 7488
| Document | Type |
RFC - Proposed Standard
(March 2015; No errata)
Updates RFC 6887
|
|
|---|---|---|---|
| Last updated | 2018-12-20 | ||
| Replaces | draft-boucadair-pcp-server-selection | ||
| Stream | IETF | ||
| Formats | plain text pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Dave Thaler | ||
| Shepherd write-up | Show (last changed 2014-09-18) | ||
| IESG | IESG state | RFC 7488 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Ted Lemon | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | No IANA Actions | ||
Internet Engineering Task Force (IETF) M. Boucadair
Request for Comments: 7488 France Telecom
Updates: 6887 R. Penno
Category: Standards Track D. Wing
ISSN: 2070-1721 P. Patil
T. Reddy
Cisco
March 2015
Port Control Protocol (PCP) Server Selection
Abstract
This document specifies the behavior to be followed by a Port Control
Protocol (PCP) client to contact its PCP server(s) when one or
several PCP server IP addresses are configured.
This document updates RFC 6887.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7488.
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Boucadair, et al. Standards Track [Page 1]
RFC 7488 PCP Server Selection March 2015
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology and Conventions . . . . . . . . . . . . . . . . . 3
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
3. IP Address Selection: PCP Server with Multiple IP Addresses . 3
4. IP Address Selection: Multiple PCP Servers . . . . . . . . . 4
5. Example: Multiple PCP Servers on a Single Interface . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
7.1. Normative References . . . . . . . . . . . . . . . . . . 7
7.2. Informative References . . . . . . . . . . . . . . . . . 8
Appendix A. Multihoming . . . . . . . . . . . . . . . . . . . . 9
A.1. IPv6 Multihoming . . . . . . . . . . . . . . . . . . . . 9
A.2. IPv4 Multihoming . . . . . . . . . . . . . . . . . . . . 10
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
A host may have multiple network interfaces (e.g., 3G, IEEE 802.11,
etc.), each configured with different PCP servers. Each PCP server
learned must be associated with the interface on which it was
learned. Generic multi-interface considerations are documented in
Section 8.4 of [RFC6887]. Multiple PCP server IP addresses may be
configured on a PCP client in some deployment contexts such as
multihoming (see Appendix A). A PCP server may also have multiple IP
addresses associated with it. It is out of the scope of this
document to enumerate all deployment scenarios that require multiple
PCP server IP addresses to be configured.
If a PCP client discovers multiple PCP server IP addresses, it needs
to determine which actions it needs to undertake (e.g., whether PCP
entries are to be installed in all or a subset of discovered IP
addresses, whether some PCP entries are to be removed, etc.). This
document makes the following assumptions:
o There is no requirement that multiple PCP servers configured on
the same interface have the same capabilities.
o PCP requests to different PCP servers are independent, the result
of a PCP request to one PCP server does not influence another.
o The configuration mechanism must distinguish IP addresses that
belong to the same PCP server.
Boucadair, et al. Standards Track [Page 2]
RFC 7488 PCP Server Selection March 2015
Show full document text