<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.vinapamula-flow-ha" target="https://datatracker.ietf.org/doc/html/draft-vinapamula-flow-ha-14">
   <front>
      <title>Application-Initiated Check-Pointing via the Port Control Protocol (PCP)</title>
      <author initials="S." surname="Vinapamula" fullname="Suresh Vinapamula">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="S." surname="Sivakumar" fullname="Senthil Sivakumar">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="M." surname="Boucadair" fullname="Mohamed Boucadair">
         <organization>Orange</organization>
      </author>
      <author initials="T." surname="Reddy.K" fullname="Tirumaleswar Reddy.K">
         <organization>Cisco</organization>
      </author>
      <date month="November" day="1" year="2015" />
      <abstract>
	 <t>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.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-vinapamula-flow-ha-14" />
   
</reference>
