Re: Gen-ART LC Review of draft-ietf-netmod-dsdl-map-07

Ben Campbell <ben@nostrum.com> Tue, 07 September 2010 21:07 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 561AB3A6AE5; Tue, 7 Sep 2010 14:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.523
X-Spam-Level:
X-Spam-Status: No, score=-102.523 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 kVlc0S-PtvI7; Tue, 7 Sep 2010 14:07:57 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 7D94C3A6AA9; Tue, 7 Sep 2010 14:07:54 -0700 (PDT)
Received: from [10.0.1.13] (adsl-68-94-18-213.dsl.rcsntx.swbell.net [68.94.18.213]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o87L8LOe005025 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 7 Sep 2010 16:08:21 -0500 (CDT) (envelope-from ben@nostrum.com)
Subject: Re: Gen-ART LC Review of draft-ietf-netmod-dsdl-map-07
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <647F7E1D-EC9B-47FC-A716-3FF96C8AC349@estacado.net>
Date: Tue, 07 Sep 2010 16:08:18 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <BDAFF84D-D78B-45D6-BA9B-2472F39730B8@nostrum.com>
References: <647F7E1D-EC9B-47FC-A716-3FF96C8AC349@estacado.net>
To: draft-ietf-netmod-dsdl-map.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
X-Mailer: Apple Mail (2.1081)
Received-SPF: pass (nostrum.com: 68.94.18.213 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Wed, 08 Sep 2010 09:30:12 -0700
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Sep 2010 21:07:58 -0000

I further note that  schishol@nortel.com gets bounced by Nortel as a non-existant address. Is there an updated address?

On Sep 7, 2010, at 4:04 PM, Ben Campbell wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> 
> Please resolve these comments along with any other Last Call comments
> you may receive.
> 
> Document: draft-ietf-netmod-dsdl-map-07
> Reviewer: Ben Campbell
> Review Date: 2010-09-07
> IETF LC End Date: 2010-09-07
> IESG Telechat date: (if known)
> 
> Summary: The draft is basically ready for publication as a proposed standard. I have a few editorial comments and nits that should be considered if there is another revision.
> 
> Note: This draft delves deeply into XML esoterica, and I am far from an XML expert. I assume the authors and work group feel this has had sufficient review from XML experts (and as far as I know, they _are_ the experts). I also assume the schemas, etc, have been mechanically verified. If not, I suggest this be done as much as practical.
> 
> Major issues:
> 
> None
> 
> Minor issues:
> 
> Nits/editorial comments:
> 
> -- Idnits complains about a number of normative references to external documents. I don't know if that's a problem--I merely point it out for consideration. It looks like it's mostly ISO docs, so I doubt there's an issue
> 
> -- There are a number of acronyms that should be expanded on first use. E.g. YANG, RELAX NG, XLST, etc.
> 
> -- section 2.1, definition of "implicit node"
> 
> Can a node be considered implicit if it is _not_ missing? If not, then the "if missing" condition is non-contraining.
> 
> -- section 3, 1st sentence:
> 
> s/by/with
> 
> -- section 9.1.1:
> 
> Is it explicitly illegal for a mandatory node to have a default?
> 
> -- section 9.1.1, third paragraph from the end:
> 
> "...and only if..." seems non-constraining in context.
> 
> -- section 13
> 
> This looks sort of light, when compared with the template in 3688. I'm not exactly sure how to apply that to a namespace, since I guess there is no XML to include, but it probably at least needs a registrant contact for each URL.
> 
> -- Author's addresses:
> 
> Is Rohan's affiliation current?