Re: [RTG-DIR] Routing directorate review of draft-ietf-mpls-ldp-hello-crypto-auth-08.txt

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 04 June 2014 01:19 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: rtg-dir@ietfa.amsl.com
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCCBF1A0004; Tue, 3 Jun 2014 18:19:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 yM8fBCKKCATJ; Tue, 3 Jun 2014 18:19:40 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A03E1A03B9; Tue, 3 Jun 2014 18:19:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id D862D2414AB; Tue, 3 Jun 2014 18:19:34 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-218.clppva.east.verizon.net [70.106.135.218]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 19B59241489; Tue, 3 Jun 2014 18:19:33 -0700 (PDT)
Message-ID: <538E7425.2080305@joelhalpern.com>
Date: Tue, 03 Jun 2014 21:19:33 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>, draft-ietf-mpls-ldp-hello-crypto-auth@tools.ietf.org, "mpls@ietf.org" <mpls@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtg-dir/LoGaXhV7Zd5qURISCTiqRldo5Ww
Subject: Re: [RTG-DIR] Routing directorate review of draft-ietf-mpls-ldp-hello-crypto-auth-08.txt
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-dir/>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jun 2014 01:19:42 -0000

[Apologies, this review was due two weeks ago.  On the other hand, you 
have reved it 3 times during my laggard behavior.]

Hello mpls WG,

I have been selected as the Routing Directorate reviewer for this draft. 
The Routing Directorate seeks to review all routing or routing-related 
drafts as they pass through IETF last call and IESG review, and 
sometimes on special request. The purpose of the review is to provide 
assistance to the Routing ADs. For more information about the Routing 
Directorate, please see ​ 
http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir

Although these comments are primarily for the use of the Routing ADs, it 
would be helpful if you could consider them along with any other IETF 
Last Call comments that you receive, and strive to resolve them through 
discussion or by updating the draft.

Document: draft-ietf-mpls-ldp-hello-crypto-auth-08.txt
Reviewer: Joel M. Halpern
Review Date: 3-June-2014
IETF LC End Date: closed
Intended Status: Standards Track

This document is basically ready for publication, but has nits that 
should be considered prior to publication.

The one nit is that I could not find the text indicating that if a 
receiver receives an unauthenticated LDP Hello packet, and is expecting 
authentication to be used (either always, or with the source the packet 
claims to be from) then the hello packet should be silently discarded.

Yours,
Joel