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

"Eric Voit (evoit)" <evoit@cisco.com> Mon, 29 April 2019 19:31 UTC

Return-Path: <evoit@cisco.com>
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 04ABE1206D8; Mon, 29 Apr 2019 12:31:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, 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 sOrOKfL3TaCH; Mon, 29 Apr 2019 12:31:43 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36C051206E2; Mon, 29 Apr 2019 12:31:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2823; q=dns/txt; s=iport; t=1556566303; x=1557775903; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=KMku+PBZIYQWkF54gzrx0z1rPG4BMnmcCct1vaGaBmg=; b=f2CLWfwGCT7wUDWiG0uV4vgs3soNHDNTDk/BffbLb6jeuSwOtg5V15XJ NDjT8blpWttpCkHwYZ7cDY+cIgYvqov0aZnS8695qlhhcphUcyx/4qzQz mmaAllaswKd1eSykKgPw2Q2MWg7/MP1R8kFKsCK6pDCVwmru5qgeRJK09 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AEAAB7UMdc/5xdJa1mDgwBAQEBAQI?= =?us-ascii?q?BAQEBBwIBAQEBgVEFAQEBAQsBgWYqgWwoCowijRSYUBSBZw4BAYRtAoYyIzQ?= =?us-ascii?q?JDgEDAQEEAQECAQJtKIVKAQEBAwE6MgoBAgUHBAIBCBUCAR4QMh0IAgQOBQg?= =?us-ascii?q?Rgj6CRQ+vfIozgTIBi0kXgUA/gRGDEj6ECYYdBIsBm3YJAoIJjmqDQSOCDZM?= =?us-ascii?q?ajSuTLwIRFYEwHziBVnAVgyeCGxcUbQEJjFk7QTGTH4EhAQE?=
X-IronPort-AV: E=Sophos;i="5.60,410,1549929600"; d="scan'208";a="541645701"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 29 Apr 2019 19:31:41 +0000
Received: from XCH-RTP-014.cisco.com (xch-rtp-014.cisco.com [64.101.220.154]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id x3TJVf0e004563 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 29 Apr 2019 19:31:41 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-014.cisco.com (64.101.220.154) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 29 Apr 2019 15:31:40 -0400
Received: from xch-rtp-013.cisco.com ([64.101.220.153]) by XCH-RTP-013.cisco.com ([64.101.220.153]) with mapi id 15.00.1473.003; Mon, 29 Apr 2019 15:31:40 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Benjamin Kaduk <kaduk@mit.edu>
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>
Thread-Topic: Benjamin Kaduk's Discuss on draft-ietf-netconf-subscribed-notifications-23: (with DISCUSS)
Thread-Index: AQHU/rKoAXBzztdqKUKWeXbDQMBk+KZTatEwgABMkYD//88ZAA==
Date: Mon, 29 Apr 2019 19:31:40 +0000
Message-ID: <94d0b3e325ee46e283d84204243bdf69@XCH-RTP-013.cisco.com>
References: <155655963180.15870.3650019434718355043.idtracker@ietfa.amsl.com> <717530026d2d4af0a92c318ecbdbb4bd@XCH-RTP-013.cisco.com> <20190429182503.GC60332@kduck.mit.edu>
In-Reply-To: <20190429182503.GC60332@kduck.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.56.233]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.154, xch-rtp-014.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/GQ_3_lgvp1_Ew10EjVqjxTkAjpc>
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 19:31:45 -0000

ipr="pre5378Trust200902"

change made and uploaded as v24

Eric

> From: Benjamin Kaduk, April 29, 2019 2:25 PM
> 
> 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.
> > >
> > >
> > >
> >