RFC 7488: Port Control Protocol (PCP) Server Selection
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7488
- Published
- March 2015
- Authors
- M. Boucadair; R. Penno; D. Wing; P. Patil; T. Reddy
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 12
- Also known as
- —
- Updates:
- RFC 6887
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7291DHCP Options for the Port Control Protocol (PCP)Current
July 2014
- RFC 7648Port Control Protocol (PCP) Proxy FunctionCurrent
September 2015
- RFC 7723Port Control Protocol (PCP) Anycast AddressesCurrent
January 2016
- RFC 8045RADIUS Extensions for IP Port Configuration and ReportingCurrent
January 2017
- RFC 6284Port Mapping between Unicast and Multicast RTP SessionsCurrent
June 2011
- RFC 3605Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)Current
October 2003
- RFC 7513Source Address Validation Improvement (SAVI) Solution for DHCPCurrent
May 2015
- RFC 7458Extensible Authentication Protocol (EAP) Attributes for Wi-Fi Integration with the Evolved Packet CoreCurrent
February 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?