RFC 7767 on Application-Initiated Check-Pointing via the Port Control Protocol (PCP)
rfc-editor@rfc-editor.org Tue, 09 February 2016 05:37 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B75F1A1A8C for <ietf-announce@ietfa.amsl.com>; Mon, 8 Feb 2016 21:37:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level:
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8LD5cDh8POiX for <ietf-announce@ietfa.amsl.com>; Mon, 8 Feb 2016 21:37:23 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0F8A1A1A88 for <ietf-announce@ietf.org>; Mon, 8 Feb 2016 21:37:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id BACD618000C; Mon, 8 Feb 2016 21:36:53 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7767 on Application-Initiated Check-Pointing via the Port Control Protocol (PCP)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160209053653.BACD618000C@rfc-editor.org>
Date: Mon, 08 Feb 2016 21:36:53 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/sBGioYQSJFOUzab8G_jDSsje1z4>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 05:37:25 -0000
A new Request for Comments is now available in online RFC libraries. RFC 7767 Title: Application-Initiated Check-Pointing via the Port Control Protocol (PCP) Author: S. Vinapamula, S. Sivakumar, M. Boucadair, T. Reddy Status: Informational Stream: Independent Date: February 2016 Mailbox: sureshk@juniper.net, ssenthil@cisco.com, mohamed.boucadair@orange.com, tireddy@cisco.com Pages: 12 Characters: 24178 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-vinapamula-flow-ha-14.txt URL: https://www.rfc-editor.org/info/rfc7767 DOI: http://dx.doi.org/10.17487/RFC7767 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. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC