[secdir] secdir review of draft-hollenbeck-rfc4931bis-01
Barry Leiba <barryleiba@computer.org> Thu, 11 June 2009 06:04 UTC
Return-Path: <barryleiba@gmail.com>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E6D7E3A6899; Wed, 10 Jun 2009 23:04:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SBC3F6jGFHDc; Wed, 10 Jun 2009 23:04:36 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.25]) by core3.amsl.com (Postfix) with ESMTP id 950AC3A67A7; Wed, 10 Jun 2009 23:04:35 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 4so16812eyf.9 for <multiple recipients>; Wed, 10 Jun 2009 23:04:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=t6GpepcZA8s4qlLMol1z4OfMezBMDYrDVUOrG3/Gd+4=; b=dhMT+jVFV/K3VRon16u7GNnxRE0GHFo50ezIfB+SWnKwg62fXEKXvgoZ8iFIjZrV+F WCLh3FpaTzhvCIkdwxMRW0rhl7uRJ7StC26BXUkxzSNF4A92MQ+1ewzjQbEzzkUH73R3 Atdx/rayo4/e/leQEP2NKgYZ7/niidjcrTryQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; b=rz6/rz3rO0OKBhmAyTADSKQzaJoln7bzfkufh+Sczf6t3MNNeFt8qeyT0DQIV4CX1v Ifs/rFcDke1HWIuq56HPz5rPSFdo9LpUiRynzpv8x0vJCVRPawUB1SY9s/RcSuuTfj2F spKZ+IWCkkVIpyBESG8HoMAVnZrd37AspEea0=
MIME-Version: 1.0
Sender: barryleiba@gmail.com
Received: by 10.210.38.5 with SMTP id l5mr2690253ebl.4.1244700278166; Wed, 10 Jun 2009 23:04:38 -0700 (PDT)
Date: Thu, 11 Jun 2009 02:04:38 -0400
X-Google-Sender-Auth: 17f8fec344d530f7
Message-ID: <9abf48a60906102304q27f92dcbmc51553fa1ae4c39d@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: secdir@ietf.org, iesg@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: shollenbeck@verisign.com, Chris Newman <Chris.Newman@Sun.COM>
Subject: [secdir] secdir review of draft-hollenbeck-rfc4931bis-01
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: Thu, 11 Jun 2009 06:04:37 -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. These comments were written primarily for the benefit of the security area directors. Document editors and WG chairs should treat these comments just like any other last call comments. This document is progressing RFC 4931 from Draft Standard to [full] Standard. That's an entirely appropriate thing to do, and I see no issues with this document. I also note, as requested in the Last Call notice, that I think the downreference to RFC 952 is appropriate. Two nits that I noticed, both in Section 1.1: OLD Name server hosts for domain delegation can be specified as either references to existing host objects or as domain attributes that describe a host machine. NEW Name server hosts for domain delegation can be specified either as references to existing host objects or as domain attributes that describe a host machine. OLD - Zero or more OPTIONAL <domain:hostAddr> element that contain the IP addresses to be associated with the host. Each element MAY NEW - Zero or more OPTIONAL <domain:hostAddr> elements that contain the IP addresses to be associated with the host. Each element MAY Barry -- Barry Leiba (barryleiba@computer.org) http://internetmessagingtechnology.org/