Re: [netconf] Benjamin Kaduk's Discuss on draft-ietf-netconf-subscribed-notifications-23: (with DISCUSS)

Benjamin Kaduk <kaduk@mit.edu> Mon, 29 April 2019 18:25 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91528120628; Mon, 29 Apr 2019 11:25:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 jUS1KKEt12qw; Mon, 29 Apr 2019 11:25:09 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 910481205E1; Mon, 29 Apr 2019 11:25:09 -0700 (PDT)
Received: from kduck.mit.edu (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x3TIP4PN005662 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 29 Apr 2019 14:25:06 -0400
Date: Mon, 29 Apr 2019 13:25:03 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: "Eric Voit (evoit)" <evoit@cisco.com>
Cc: The IESG <iesg@ietf.org>, "draft-ietf-netconf-subscribed-notifications@ietf.org" <draft-ietf-netconf-subscribed-notifications@ietf.org>, Kent Watsen <kent+ietf@watsen.net>, "netconf-chairs@ietf.org" <netconf-chairs@ietf.org>, "netconf@ietf.org" <netconf@ietf.org>
Message-ID: <20190429182503.GC60332@kduck.mit.edu>
References: <155655963180.15870.3650019434718355043.idtracker@ietfa.amsl.com> <717530026d2d4af0a92c318ecbdbb4bd@XCH-RTP-013.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <717530026d2d4af0a92c318ecbdbb4bd@XCH-RTP-013.cisco.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/YFc5UVd5E-i2BGmyj3SQJ8CE0Hk>
Subject: Re: [netconf] Benjamin Kaduk's Discuss on draft-ietf-netconf-subscribed-notifications-23: (with DISCUSS)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2019 18:25:12 -0000

On Mon, Apr 29, 2019 at 05:58:19PM +0000, Eric Voit (evoit) wrote:
> Hi Benjamin,
> 
> I think you are asking why the following boilerplate text wasn't included...
> 
>    This document may contain material from IETF Documents or IETF
>    Contributions published or made publicly available before November
>    10, 2008.  The person(s) controlling the copyright in some of this
>    material may not have granted the IETF Trust the right to allow
>    modifications of such material outside the IETF Standards Process.
>    Without obtaining an adequate license from the person(s) controlling
>    the copyright in such materials, this document may not be modified
>    outside the IETF Standards Process, and derivative works of it may
>    not be created outside the IETF Standards Process, except to format
>    it for publication as an RFC or to translate it into languages other
>    than English.

Exactly so.

> 
> This was likely an oversight during the initial author's submission.  If this text was included and uploaded as a -24 update, would that cover your concern?

Definitely.
(Note that there's an XML keyword for this; IIRC, <rfc [...]
ipr="pre5378Trust200902">.)

> BTW: the same boilerplate update should also be made to 
> draft-ietf-netconf-netconf-event-notification  and draft-ietf-netconf-restconf-notif

Thanks for spotting those early!

-Ben

> 
> 
> > -----Original Message-----
> > From: Benjamin Kaduk via Datatracker <noreply@ietf.org>;
> > Subject: Benjamin Kaduk's Discuss on draft-ietf-netconf-subscribed-
> > notifications-23: (with DISCUSS)
> > 
> > ----------------------------------------------------------------------
> > DISCUSS:
> > ----------------------------------------------------------------------
> > 
> > [putting this out early in the hopes it can be resolved quickly; I'm just starting to
> > review the document.]
> > 
> > This document started life as a rfc5277bis, published in July 2008, before RFC
> > 5378 (BCP 78) was published in November of 2008.  If we are using any text from
> > RFC 5277 and did not gain the additional rights declaration from the authors of
> > that document, this document needs to use a different boilerplate text (the "pre-
> > 2008" text).  I look at the sibling document draft-ietf-netfonf-yang-push of this
> > document, which does use the pre-2008 boilerplate, and am having a hard time
> > understanding why this document does not also have the pre-2008 boilerplate.
> > 
> > 
> > 
>