Re: [CCAMP] Mirja Kühlewind's No Objection on draft-ietf-ccamp-mw-yang-10: (with COMMENT)

"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Fri, 26 October 2018 08:26 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3D85127AC2; Fri, 26 Oct 2018 01:26:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 d6Ij92lRAxxt; Fri, 26 Oct 2018 01:26:06 -0700 (PDT)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9A0E130DFF; Fri, 26 Oct 2018 01:26:05 -0700 (PDT)
Received: from 200116b82c76150024b91ee8039d57fd.dip.versatel-1u1.de ([2001:16b8:2c76:1500:24b9:1ee8:39d:57fd]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1gFxRS-0001PS-8M; Fri, 26 Oct 2018 10:26:02 +0200
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <9C5FD3EFA72E1740A3D41BADDE0B461FCFA6DE38@DGGEMM528-MBX.china.huawei.com>
Date: Fri, 26 Oct 2018 10:26:00 +0200
Cc: The IESG <iesg@ietf.org>, "ccamp-chairs@ietf.org" <ccamp-chairs@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, Fatai Zhang <zhangfatai@huawei.com>, "draft-ietf-ccamp-mw-yang@ietf.org" <draft-ietf-ccamp-mw-yang@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C10611EF-0E6C-47D0-AD27-7FDA2DE58147@kuehlewind.net>
References: <154047368042.16350.848149558496752916.idtracker@ietfa.amsl.com> <9C5FD3EFA72E1740A3D41BADDE0B461FCFA6DE38@DGGEMM528-MBX.china.huawei.com>
To: "Yemin (Amy)" <amy.yemin@huawei.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1540542365;d3d9f9f5;
X-HE-SMSGID: 1gFxRS-0001PS-8M
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/vmL9gmYF5pvNj9Q3Fb4Of7ETMho>
Subject: Re: [CCAMP] Mirja Kühlewind's No Objection on draft-ietf-ccamp-mw-yang-10: (with COMMENT)
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2018 08:26:10 -0000

Hi Amy,

not sure which part of the statement below you are relying you decision on but the document says:

"Normative references specify documents that must be read to understand or implement the technology in the new RFC“

So, as you say below, as these reference are needed to implement it correctly, they must be normative.

It is possible for non-IETF document to be normative as long as the reference are stable and open.

Mirja



> Am 26.10.2018 um 03:28 schrieb Yemin (Amy) <amy.yemin@huawei.com>:
> 
> Hi Mirja, 
>  
> Thanks for your comment. 
> Yes, these on-IETF specs are to be understood when correctly implement this YANG model.
> They are not completed removed from the draft. After shepherd write-up, those documents are moved to informative reference section according to thehttps://www.ietf.org/blog/iesg-statement-normative-and-informative-references/. I hope we understand the rules correctly.
>  
> BR,
> Amy, on behalf of co-authors 
>  
> -----Original Message-----
> From: Mirja Kühlewind [mailto:ietf@kuehlewind.net] 
> Sent: Thursday, October 25, 2018 9:21 PM
> To: The IESG <iesg@ietf.org>
> Cc: draft-ietf-ccamp-mw-yang@ietf.org; Fatai Zhang <zhangfatai@huawei.com>; ccamp-chairs@ietf.org; Fatai Zhang <zhangfatai@huawei.com>; ccamp@ietf.org
> Subject: Mirja Kühlewind's No Objection on draft-ietf-ccamp-mw-yang-10: (with COMMENT)
>  
> Mirja Kühlewind has entered the following ballot position for
> draft-ietf-ccamp-mw-yang-10: No Objection
>  
> When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.)
>  
>  
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>  
>  
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-ccamp-mw-yang/
>  
>  
>  
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>  
> The shepherd write-up says that there have been normative references to non-IETF docs which seem to have been removed now. I wondering is that is correct. I'm by far not an expert and didn't have time to review this doc in detail but I would think that you would need to know some details of these on-IETF specs in-order to fully understand and correctly implement this YANG model, no?