Dave: Also, when change control is fully given the the IETF, we have seen the original work published as an Informational RFC that includes a statement that any future versions will be published by the IETF. RFC 8018 is an example. It says: This document represents a republication of PKCS #5 v2.1 from RSA Laboratories' Public-Key Cryptography Standards (PKCS) series. By publishing this RFC, change control is transferred to the IETF. Since full change control was transferred, that is there are no constraints, the statement in the RFC was considered sufficient. Russ > On Sep 7, 2017, at 10:43 AM, Dave Crocker <dhc@xxxxxxxxxxxx> wrote: > > G'day, > > When outside work is brought into the IETF, it is typical to make a formal agreement. between the IETF and the originating organization. > > It makes the hand-off explicit, sets any constraints on the handoff, and sets any constraints on the efforts of the initial working group. (The constraints can range from 'only bug fixes' to 'use the existing work merely as conceptual input'.) > > The first such IETF agreement was for the underpinnings of NFS: > > An Agreement between the Internet Society and Sun Microsystems, Inc. > in the Matter of ONC RPC and XDR Protocols > > https://www.rfc-editor.org/rfc/rfc1790.txt > > Another one, 3 years later, was for NFS itself. > > I cannot find the set of such agreements on the IETF web site, nor as other RFCs. > > Does anyone have a pointer to the set of these agreements? > > Thanks. > > d/ > > > ps. my initial focus was to find the agreement for vcard/vcalendar, but the search produced the larger question. > > -- > Dave Crocker > Brandenburg InternetWorking > bbiw.net >