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

["Eric Voit (evoit)" <[e-mail]>]

> From: Magnus Westerlund, April 30, 2019 4:32 AM
> 
> Hi,
> 
> I think it should be avoided if possible to add the pre-5378 boilerplate, it is better
> to get the rights. Especially in this situation where there has been many version
> published stating that the rights have been had. Is there a problem of getting the
> rights?

Hi Magnus,

Here is the current status...

There are no full sentences from RFC-5277 used in this document.  However there are a few sentence fragments in the terminology, as well as quite a few concepts adopted based on RFC5277.  On the basis of that Benjamin's DISCUSS however, it felt like we should err on the side of caution by adding his suggestion.  

Along with this, at the end of 2016 the original authors of RFC-5277 (Sharon & Hector) stated they no longer needed to be on this draft.  I haven't been in contact with them since.  So without a relationship here, it seemed like the including the "pre5378Trust200902" text was again erring on the side of caution.

Eric

> Cheers
> 
> Magnus
> 
> On 2019-04-29 21:31, Eric Voit (evoit) wrote:
> > 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 <[e-mail]>
> >>>> 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.
> >>>>
> >>>>
> >
> 
> --
> 
> Magnus Westerlund
> 
> ----------------------------------------------------------------------
> Network Architecture & Protocols, Ericsson Research
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  [phone]
> Torshamnsgatan 23           | Mobile [phone]
> SE-164 80 Stockholm, Sweden | mailto: [e-mail]
> ----------------------------------------------------------------------