RFC 7767: Application-Initiated Check-Pointing via the Port Control Protocol (PCP)
In plain English — editorial summary, not part of the RFC
This document specifies a mechanism for a host to indicate via the Port Control Protocol (PCP) which connections should be protected against network failures. These connections will then be subject to high-availability mechanisms enabled on the network side. This approach assumes that applications and/or users have more visibility about sensitive connections than any heuristic that can be enabled on the network side to guess which connections should be check-pointed.
Document record
- Document ID
- RFC7767
- Published
- February 2016
- Authors
- S. Vinapamula; S. Sivakumar; M. Boucadair; T. Reddy
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9244Distributed Denial-of-Service Open Threat Signaling (DOTS) TelemetryCurrent
June 2022
- RFC 8921Dynamic Service Negotiation: The Connectivity Provisioning Negotiation Protocol (CPNP)Current
October 2020
- RFC 8768Constrained Application Protocol (CoAP) Hop-Limit OptionCurrent
March 2020
- RFC 8782Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel SpecificationObsoleted
May 2020
- RFC 8783Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel SpecificationCurrent
May 2020
- RFC 8969A Framework for Automating Service and Network Management with YANGCurrent
January 2021
- RFC 9132Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel SpecificationCurrent
September 2021
- RFC 9145Integrity Protection for the Network Service Header (NSH) and Encryption of Sensitive Context HeadersCurrent
December 2021
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?