[mpls] New version of draft-ietf-mpls-ldp-hello-crypto-auth-07.txt
Loa Andersson <loa@pi.nu> Fri, 30 May 2014 13:27 UTC
Return-Path: <loa@pi.nu>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFCC11A6F62 for <mpls@ietfa.amsl.com>; Fri, 30 May 2014 06:27:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 JivGMT9qy9TN for <mpls@ietfa.amsl.com>; Fri, 30 May 2014 06:27:12 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 704211A6FF3 for <mpls@ietf.org>; Fri, 30 May 2014 06:27:12 -0700 (PDT)
Received: from [192.168.1.8] (unknown [119.94.254.248]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 73B7D1801294; Fri, 30 May 2014 15:27:05 +0200 (CEST)
Message-ID: <53888725.1050907@pi.nu>
Date: Fri, 30 May 2014 15:27:01 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: "mpls@ietf.org" <mpls@ietf.org>, "<mpls-ads@tools.ietf.org>" <mpls-ads@tools.ietf.org>
References: <20140530021024.7021.55736.idtracker@ietfa.amsl.com>
In-Reply-To: <20140530021024.7021.55736.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20140530021024.7021.55736.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mpls/prOapton6qpWJaB8ZoXO61SNXrE
Cc: "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, "draft-ietf-mpls-ldp-hello-crypto-auth@tools.ietf.org" <draft-ietf-mpls-ldp-hello-crypto-auth@tools.ietf.org>
Subject: [mpls] New version of draft-ietf-mpls-ldp-hello-crypto-auth-07.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 May 2014 13:27:14 -0000
Working Group, During the IANA review of draft-ietf-mpls-ldp-hello-crypto-auth we discovered what Adrian call a snafu*. The document assigns a new LDP TLV and the text in most of document is correct, however in the IANA section we did not point to the LDP TLVs, but to LSP Ping TLVs. This has been corrected in the new version. The document shepherd (me) and the responsible AD (Adrian) has discussed this and agree that this is minor and we don't need to issue a new wglc. /Loa * Note: I'm considering asking Adrian to explain the meaning of "snafu", at e.g. the rtgwg meeting next IETF. For the time being my understanding is that snafus is nothing that we want in our documents, or a word that the RFC Editor under normal circumstances would allow us to use. -------- Original Message -------- Subject: [mpls] I-D Action: draft-ietf-mpls-ldp-hello-crypto-auth-07.txt Date: Thu, 29 May 2014 19:10:24 -0700 From: internet-drafts@ietf.org To: i-d-announce@ietf.org CC: mpls@ietf.org A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF. Title : LDP Hello Cryptographic Authentication Authors : Lianshu Zheng Mach(Guoyi) Chen Manav Bhatia Filename : draft-ietf-mpls-ldp-hello-crypto-auth-07.txt Pages : 14 Date : 2014-05-29 Abstract: 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 National Institute of Standards and Technology (NIST) Secure Hash Standard family of algorithms. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-mpls-ldp-hello-crypto-auth/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-mpls-ldp-hello-crypto-auth-07 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-mpls-ldp-hello-crypto-auth-07 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ mpls mailing list mpls@ietf.org https://www.ietf.org/mailman/listinfo/mpls
- [mpls] I-D Action: draft-ietf-mpls-ldp-hello-cryp… internet-drafts
- [mpls] New version of draft-ietf-mpls-ldp-hello-c… Loa Andersson