[secdir] secdir review of draft-ietf-pim-registry-03

Catherine Meadows <catherine.meadows@nrl.navy.mil> Tue, 18 January 2011 22:34 UTC

Return-Path: <catherine.meadows@nrl.navy.mil>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id B677A28C0E0; Tue, 18 Jan 2011 14:34:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id wiaM2ZoFb0w3; Tue, 18 Jan 2011 14:34:53 -0800 (PST)
Received: from fw5540.nrl.navy.mil (fw5540.nrl.navy.mil []) by core3.amsl.com (Postfix) with ESMTP id B1AC03A7068; Tue, 18 Jan 2011 14:34:53 -0800 (PST)
Received: from chacs.nrl.navy.mil (sun1.fw5540.net []) by fw5540.nrl.navy.mil (8.13.8/8.13.6) with ESMTP id p0IMbT06013189; Tue, 18 Jan 2011 17:37:29 -0500 (EST)
Received: from chacs.nrl.navy.mil (sun1 []) by chacs.nrl.navy.mil (8.13.8/8.13.6) with SMTP id p0IMbRC6027966; Tue, 18 Jan 2011 17:37:27 -0500 (EST)
Received: from siduri.fw5540.net ([]) by chacs.nrl.navy.mil (SMSSMTP with SMTP id M2011011817372617948 ; Tue, 18 Jan 2011 17:37:26 -0500
From: Catherine Meadows <catherine.meadows@nrl.navy.mil>
Content-Type: multipart/alternative; boundary=Apple-Mail-10--744066565
Date: Tue, 18 Jan 2011 17:45:13 -0500
Message-Id: <F0189CCC-CC55-4A8D-A0A0-EE61F155B40D@nrl.navy.mil>
To: iesg@ietf.org, secdir@ietf.org, draft-ietf-pim-registry.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
Subject: [secdir] secdir review of draft-ietf-pim-registry-03
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jan 2011 22:34:54 -0000

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  Document editors and WG chairs should treat these comments just
like any other last call comments.

This short draft provides instructions for an IANA  registry for Protocol Independent Multicast (PIM) message types.  There is currently no such registry, and there
are already several RFCs specifying PIM message types that should be included.  The document gives the initial content of the
registry based on these RFCs, as well as a new type which is reserved for the extension of type space.

The authors not that other than the possible security benefits of having one place where the various PIM message types can
be found, there are no security considerations.  I agree with them, and so don't have anything further to add.

Catherine Meadows
Naval Research Laboratory
Code 5543
4555 Overlook Ave., S.W.
Washington DC, 20375
phone: 202-767-3490
fax: 202-404-7942
email: catherine.meadows@nrl.navy.mil