RFC 6411 on Applicability of Keying Methods for RSVP Security
rfc-editor@rfc-editor.org Tue, 01 November 2011 05:09 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2F1121F8E17; Mon, 31 Oct 2011 22:09:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.895
X-Spam-Level:
X-Spam-Status: No, score=-101.895 tagged_above=-999 required=5 tests=[AWL=0.705, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ohFXc3R74-oE; Mon, 31 Oct 2011 22:09:56 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 3AC6D21F8E15; Mon, 31 Oct 2011 22:09:56 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 50922B1E009; Mon, 31 Oct 2011 21:52:53 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6411 on Applicability of Keying Methods for RSVP Security
From: rfc-editor@rfc-editor.org
Message-Id: <20111101045253.50922B1E009@rfc-editor.org>
Date: Mon, 31 Oct 2011 21:52:53 -0700
Cc: tsvwg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2011 05:09:56 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6411
Title: Applicability of Keying Methods for
RSVP Security
Author: M. Behringer, F. Le Faucheur,
B. Weis
Status: Informational
Stream: IETF
Date: October 2011
Mailbox: mbehring@cisco.com,
flefauch@cisco.com,
bew@cisco.com
Pages: 19
Characters: 46072
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-tsvwg-rsvp-security-groupkeying-11.txt
URL: http://www.rfc-editor.org/rfc/rfc6411.txt
The Resource reSerVation Protocol (RSVP) allows hop-by-hop integrity
protection of RSVP neighbors. This requires messages to be
cryptographically protected using a shared secret between
participating nodes. This document compares group keying for RSVP
with per-neighbor or per-interface keying, and discusses the
associated key provisioning methods as well as applicability and
limitations of these approaches. This document also discusses
applicability of encrypting RSVP messages. This document is not an
Internet Standards Track specification; it is published for informational
purposes.
This document is a product of the Transport Area Working Group Working Group of the IETF.
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
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
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