RFC 7349 on LDP Hello Cryptographic Authentication
rfc-editor@rfc-editor.org Thu, 14 August 2014 18:40 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 075271A032A for <ietf-announce@ietfa.amsl.com>; Thu, 14 Aug 2014 11:40:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.57
X-Spam-Level:
X-Spam-Status: No, score=-107.57 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, 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 TFvnVw4P3ZP3 for <ietf-announce@ietfa.amsl.com>; Thu, 14 Aug 2014 11:40:19 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id AAC4A1A7029 for <ietf-announce@ietf.org>; Thu, 14 Aug 2014 11:39:59 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id EC0601801A4; Thu, 14 Aug 2014 11:38:05 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7349 on LDP Hello Cryptographic Authentication
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140814183805.EC0601801A4@rfc-editor.org>
Date: Thu, 14 Aug 2014 11:38:05 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/2f9sjpAsR-t8W-ynLhyhwenygtc
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: <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: Thu, 14 Aug 2014 18:40:21 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7349
Title: LDP Hello Cryptographic Authentication
Author: L. Zheng, M. Chen, M. Bhatia
Status: Standards Track
Stream: IETF
Date: August 2014
Mailbox: vero.zheng@huawei.com,
mach.chen@huawei.com,
manav@ionosnetworks.com
Pages: 14
Characters: 32447
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mpls-ldp-hello-crypto-auth-10.txt
URL: https://www.rfc-editor.org/rfc/rfc7349.txt
This document introduces a new optional Cryptographic Authentication
TLV that LDP can use to secure its Hello messages. It secures the
Hello messages against spoofing attacks and some well-known attacks
against the IP header. This document describes a mechanism to secure
the LDP Hello messages using Hashed Message Authentication Code
(HMAC) with the National Institute of Standards and Technology (NIST)
Secure Hash Standard family of algorithms.
This document is a product of the Multiprotocol Label Switching Working Group of the IETF.
This is now a Proposed Standard.
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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
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/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