Browse Prior Art Database

Application-Initiated Check-Pointing via the Port Control Protocol (PCP) (RFC7767) Disclosure Number: IPCOM000245109D
Original Publication Date: 2016-Feb-01
Included in the Prior Art Database: 2016-Feb-10
Document File: 24 page(s) / 24K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Vinapamula: AUTHOR [+4]


The risk of Internet service disruption is critical in service providers and enterprise networking environments. Such a risk is often mitigated with the introduction of active/backup systems. Such designs not only contribute to minimize the risk of service disruption, but also facilitate maintenance operations (e.g., hitless hardware or software upgrades).

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 11% of the total text.

Independent Submission                                     S. Vinapamula Request for Comments: 7767                              Juniper Networks Category: Informational                                     S. Sivakumar ISSN: 2070-1721                                            Cisco Systems                                                             M. Boucadair                                                                   Orange                                                                 T. Reddy                                                                    Cisco                                                            February 2016

 Application-Initiated Check-Pointing via the Port Control Protocol (PCP)


   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.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This is a contribution to the RFC Series, independently of any other    RFC stream.  The RFC Editor has chosen to publish this document at    its discretion and makes no statement about its value for    implementation or deployment.  Documents approved for publication by    the RFC Editor are not a candidate for any level of Internet    Standard; see 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

Vinapamula, et al.            Informational                     [Page 1]
 RFC 7767                     HA through PCP                February 2016

 Copyright Notice

   Copyright (c) 2016 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    ( in effect on the date of    publication of this docum...