RFC 6496 on Secure Proxy ND Support for SEcure Neighbor Discovery (SEND)
rfc-editor@rfc-editor.org Sat, 04 February 2012 01:38 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C251911E80BD; Fri, 3 Feb 2012 17:38:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.41
X-Spam-Level:
X-Spam-Status: No, score=-102.41 tagged_above=-999 required=5 tests=[AWL=0.190, 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 JlZyK62Z9Q8X; Fri, 3 Feb 2012 17:38:21 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 52C7211E8098; Fri, 3 Feb 2012 17:38:21 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id F3153B1E034; Fri, 3 Feb 2012 17:22:15 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6496 on Secure Proxy ND Support for SEcure Neighbor Discovery (SEND)
From: rfc-editor@rfc-editor.org
Message-Id: <20120204012215.F3153B1E034@rfc-editor.org>
Date: Fri, 03 Feb 2012 17:22:15 -0800
Cc: cga-ext@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: <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: Sat, 04 Feb 2012 01:38:21 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6496
Title: Secure Proxy ND Support for
SEcure Neighbor Discovery (SEND)
Author: S. Krishnan, J. Laganier,
M. Bonola, A. Garcia-Martinez
Status: Experimental
Stream: IETF
Date: February 2012
Mailbox: suresh.krishnan@ericsson.com,
julien.ietf@gmail.com,
marco.bonola@gmail.com, alberto@it.uc3m.es
Pages: 24
Characters: 57746
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-csi-proxy-send-05.txt
URL: http://www.rfc-editor.org/rfc/rfc6496.txt
SEcure Neighbor Discovery (SEND) specifies a method for securing
Neighbor Discovery (ND) signaling against specific threats. As
defined today, SEND assumes that the node sending an ND message is
the owner of the address from which the message is sent and/or
possesses a key that authorizes the node to act as a router, so that
it is in possession of the private key or keys used to generate the
digital signature on each message. This means that the Proxy ND
signaling performed by nodes that do not possess knowledge of the
address owner's private key and/or knowledge of a router's key cannot
be secured using SEND. This document extends the current SEND
specification in order to secure Proxy ND operation. This document
defines an Experimental Protocol for the Internet community.
This document is a product of the Cga & Send maIntenance Working Group of the IETF.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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