IETF Logo Mail Archive

Re: [netmod] AD review of draft-ietf-netmod-rfc6087bis-16 Part 1

Benoit Claise <bclaise@cisco.com> Thu, 25 January 2018 12:20 UTC

Return-Path: <bclaise@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 9447C1242F7 for <netmod@ietfa.amsl.com>; Thu, 25 Jan 2018 04:20:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 q2_6_eo6LlBU for <netmod@ietfa.amsl.com>; Thu, 25 Jan 2018 04:20:33 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1A2E12025C for <netmod@ietf.org>; Thu, 25 Jan 2018 04:20:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=669; q=dns/txt; s=iport; t=1516882832; x=1518092432; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=OIoqFNZYn1vdodspCCzXZL5DVf0QYifxorM+h/yas/k=; b=VEV6GxjO3o1nV9SCrdSB2DfAx/WjX1aAxXxX5obxYILXN9GqZ+t1emOm v1Hsc8I7dbVXJuq7u7sHcJVAxEAGhmdic4zh92dEE+JYATO92bGRtzmhk Fe9uj94mDtHvaFnW3I0d2o4qWJnFbwrNL8JFBB5iAZz7CMOPVr6SZzLE4 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B0AQCqomla/xbLJq1dGQEBAQEBAQEBAQEBAQcBAQEBAYQodCeDXYsYj08nmVoKI4UYAoU1FAEBAQEBAQEBAmsohSQBBSMPAQVRCxgCAiYCAlcGDQgBAYoxELUggieKYAEBAQEBAQEBAgEBAQEBAQEcBYEPg0KDbIFoKQyCeYMvAQECAYUFgmUFpAmIFY1NggKKKYd6jVqBa4gTgTw2IoFQMxoIGxWCaIRXQDcBjkoBAQE
X-IronPort-AV: E=Sophos;i="5.46,411,1511827200"; d="scan'208";a="1594226"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Jan 2018 12:20:30 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id w0PCKU7N020406 for <netmod@ietf.org>; Thu, 25 Jan 2018 12:20:30 GMT
To: NETMOD Working Group <netmod@ietf.org>
References: <e1f4f27a-d982-b248-f0e1-7093dc2f63e8@cisco.com> <6f96ec70-1532-5d99-97d1-5d5531e7865e@cisco.com> <20180125115941.tmfquapklprdw2d3@elstar.local>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <73ced326-63fa-2305-f425-d7bd919c58df@cisco.com>
Date: Thu, 25 Jan 2018 13:20:30 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <20180125115941.tmfquapklprdw2d3@elstar.local>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/w7M59PHb7sVYxOGamO6tJqY0MKU>
Subject: Re: [netmod] AD review of draft-ietf-netmod-rfc6087bis-16 Part 1
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 25 Jan 2018 12:20:35 -0000

On 1/25/2018 12:59 PM, Juergen Schoenwaelder wrote:
> On Thu, Jan 25, 2018 at 12:20:11PM +0100, Benoit Claise wrote:
>   
>> PROPOSAL (replacing the previous paragraph)
>>
>>         If YANG tree diagrams are used, then a normative reference to the
>>         YANG tree diagrams specification MUST be provided. As an example guideline
>>         (from https://tools.ietf.org/html/draft-ietf-netmod-rfc7223bis-03#section-1.3),
>>         here is a subsection in the terminology section
> The current practice is that the tree diagrams reference is an
> informative reference and not a normative reference.
Good catch Jürgen.

Regards, Benoit
>
> /js
>

v2.23.0 | Report a Bug | By Email