[netmod] Are multiple revisions with the same date allowed?

Robert Wilton <rwilton@cisco.com> Mon, 30 January 2017 11:50 UTC

Return-Path: <rwilton@cisco.com>
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 1026F129458 for <netmod@ietfa.amsl.com>; Mon, 30 Jan 2017 03:50:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.721
X-Spam-Level:
X-Spam-Status: No, score=-17.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 w5GpK70dLA8l for <netmod@ietfa.amsl.com>; Mon, 30 Jan 2017 03:50:26 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D93412945A for <netmod@ietf.org>; Mon, 30 Jan 2017 03:50:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=736; q=dns/txt; s=iport; t=1485777022; x=1486986622; h=to:from:subject:message-id:date:mime-version: content-transfer-encoding; bh=LG+QFXYWofUaKkannKBO8N6ah2aB1L8jpgDMZsuMz70=; b=FDVy255POAA4tTJxLblOl/W1yVTkxX8IWUXhv8hPGaLCzliGZVjbWMBw WW5wkCiTjz5gTd9p72QuyEOHkWTMs/kHINRmc8dUu5z8RUlocPZJHaE+l i/i0xOE8kQf4wX6pWaUcfGXXS6+Vgm/FyAshWSaynKOwrb8ACW+g/abX2 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CqAgALKI9Y/xbLJq1dGwEBAQMBAQEJAQEBhF6ENIoJcqZBggyIcxgBAgEBAQEBAQFiHQuFExV2AiYCXw0IAQGJYJsVkAGCJYpwAQEIAiaBC4VAggWKOYJfBZtUgU2QLoFhiFeGP4sAh38fOIEbEwgVFYZ0QIhnAQEB
X-IronPort-AV: E=Sophos;i="5.33,311,1477958400"; d="scan'208";a="649240835"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Jan 2017 11:50:20 +0000
Received: from [10.63.23.109] (dhcp-ensft1-uk-vla370-10-63-23-109.cisco.com [10.63.23.109]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v0UBoK9L015017 for <netmod@ietf.org>; Mon, 30 Jan 2017 11:50:20 GMT
To: "netmod@ietf.org" <netmod@ietf.org>
From: Robert Wilton <rwilton@cisco.com>
Message-ID: <7b87a0ee-0c10-5f40-418e-4c125901e336@cisco.com>
Date: Mon, 30 Jan 2017 11:50:20 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/K-yIMHg555TaeAtUrEeOz9Fg1Us>
Subject: [netmod] Are multiple revisions with the same date allowed?
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 30 Jan 2017 11:50:28 -0000

RFC 7950 doesn't state that the date associated with revision statements 
in a YANG module must be unique.

Hence, I presume that it is intentionally allowed to have multiple 
revision statements with the same date.  E.g. the following module is 
allowed (and passes pyang --lint):

module rev-example {
   namespace
     "urn:example";

   prefix ex;

   organization "";

   contact "";

   description "'";
   reference "IEEE 802.3-2015, unless dated explicitly";

   revision 2017-01-30 {
     description
       "A revision description";
     reference "";
   }

   revision 2017-01-30 {
     description
       "A different revision with the same date";
     reference "";
   }

}

Thanks,
Rob