RFC 5796 on Authentication and Confidentiality in Protocol Independent Multicast Sparse Mode (PIM-SM) Link-Local Messages

rfc-editor@rfc-editor.org Fri, 19 March 2010 02:19 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 65CB23A6CC0; Thu, 18 Mar 2010 19:19:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.373
X-Spam-Status: No, score=-1.373 tagged_above=-999 required=5 tests=[AWL=-0.503, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id gw2W6BELkHJQ; Thu, 18 Mar 2010 19:19:00 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 6E2E03A6CC8; Thu, 18 Mar 2010 19:18:50 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 22EBBE077E; Thu, 18 Mar 2010 19:19:03 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5796 on Authentication and Confidentiality in Protocol Independent Multicast Sparse Mode (PIM-SM) Link-Local Messages
From: rfc-editor@rfc-editor.org
Message-Id: <20100319021903.22EBBE077E@rfc-editor.org>
Date: Thu, 18 Mar 2010 19:19:03 -0700 (PDT)
Cc: pim@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Fri, 19 Mar 2010 02:19:01 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 5796

        Title:      Authentication and Confidentiality in Protocol 
                    Independent Multicast Sparse Mode (PIM-SM) Link-Local 
        Author:     W. Atwood, S. Islam,
                    M. Siami
        Status:     Standards Track
        Date:       March 2010
        Mailbox:    bill@cse.concordia.ca, 
        Pages:      21
        Characters: 45442
        Updates:    RFC4601

        I-D Tag:    draft-ietf-pim-sm-linklocal-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5796.txt

RFC 4601 mandates the use of IPsec to ensure authentication of the
link-local messages in the Protocol Independent Multicast - Sparse
Mode (PIM-SM) routing protocol.  This document specifies mechanisms
to authenticate the PIM-SM link-local messages using the IP security
(IPsec) Encapsulating Security Payload (ESP) or (optionally) the
Authentication Header (AH).  It specifies optional mechanisms to
provide confidentiality using the ESP.  Manual keying is specified as
the mandatory and default group key management solution.  To deal
with issues of scalability and security that exist with manual
keying, optional support for an automated group key management
mechanism is provided.  However, the procedures for implementing
automated group key management are left to other documents.  This
document updates RFC 4601.  [STANDARDS TRACK]

This document is a product of the Protocol Independent Multicast Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

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