Re: [netmod] Last Call: draft-schoenw-netmod-rfc6021-bis-01 (20130204)

Ladislav Lhotka <lhotka@nic.cz> Mon, 21 January 2013 13:29 UTC

Return-Path: <lhotka@nic.cz>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5338021F8749 for <netmod@ietfa.amsl.com>; Mon, 21 Jan 2013 05:29:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.764
X-Spam-Level:
X-Spam-Status: No, score=0.764 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HOST_EQ_CZ=0.904, J_CHICKENPOX_23=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QZUoMLjQVHxQ for <netmod@ietfa.amsl.com>; Mon, 21 Jan 2013 05:29:08 -0800 (PST)
Received: from trail.lhotka.name (nat-5.bravonet.cz [77.48.224.5]) by ietfa.amsl.com (Postfix) with ESMTP id A748221F8742 for <netmod@ietf.org>; Mon, 21 Jan 2013 05:29:08 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by trail.lhotka.name (Postfix) with ESMTP id 8E35D540706 for <netmod@ietf.org>; Mon, 21 Jan 2013 14:29:01 +0100 (CET)
Received: from trail.lhotka.name ([127.0.0.1]) by localhost (trail.lhotka.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id apSvvbB+b+22 for <netmod@ietf.org>; Mon, 21 Jan 2013 14:28:49 +0100 (CET)
Received: from localhost (unknown [172.29.2.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by trail.lhotka.name (Postfix) with ESMTPSA id 9B237540071 for <netmod@ietf.org>; Mon, 21 Jan 2013 14:28:44 +0100 (CET)
From: Ladislav Lhotka <lhotka@nic.cz>
To: netmod@ietf.org
In-Reply-To: <20130119011641.GK11206@nsn.com>
References: <20130119011641.GK11206@nsn.com>
User-Agent: Notmuch/0.14+243~g18d79d1 (http://notmuchmail.org) Emacs/23.3.50.1 (i386-apple-darwin9.8.0)
Mail-Followup-To: netmod@ietf.org
Date: Mon, 21 Jan 2013 14:28:43 +0100
Message-ID: <m2622qk6lw.fsf@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [netmod] Last Call: draft-schoenw-netmod-rfc6021-bis-01 (20130204)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netmod>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jan 2013 13:29:09 -0000

Hi,

I support moving this document forward, with two comments:

1. The second pattern for "yang-identifier" type can be slightly optimized:

OLD

    pattern '.|..|[^xX].*|.[^mM].*|..[^lL].*';

NEW

    pattern '..?|[^xX].*|.[^mM].*|..[^lL].*';

2. It would be safer to have types 'ipv[46]-address' (meaning no zone) and 'ipv[46]-address-with-zone' rather than 'ipv[46]-address' and 'ipv[46]-address-no-zone'. I know, it's an incompatible change, but I suspect that many implementers will not bother to look up the definition when seeing a type like 'ipv4-address' and assume a plain IPv4 address in that place. Such a mistake can easily create a security hole. The name 'ipv[46]-address-with-zone' makes the optional presence of a zone index explicit and eliminates this potential trap. Besides, it would also better fit the naming scheme of corresponding textual conventions in RFC 4001.

Lada
 
David Kessens <david.kessens@nsn.com> writes:

> Hi,
>
> I would hereby like to start a Last Call for:
>
> http://tools.ietf.org/id/draft-schoenw-netmod-rfc6021-bis-01 
>
-- 
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C