Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents
draft-ietf-iasa2-rfc5377bis-03

Received changes through RFC Editor sync (created alias RFC 8721, changed abstract to 'Contributors grant intellectual property rights to the IETF.  The IETF Trust holds and manages those rights on behalf of the IETF.  The Trustees of the IETF Trust are responsible for that management.  This management includes granting the licenses to copy, implement, and otherwise use IETF Contributions, among them Internet-Drafts and RFCs.  The Trustees of the IETF Trust accept direction from the IETF regarding the rights to be granted.  This document describes the desires of the IETF regarding outbound rights to be granted in IETF Contributions.  This document obsoletes RFC 5377 solely for the purpose of removing references to the IETF Administrative Oversight Committee (IAOC), which was part of the IETF Administrative Support Activity (IASA).', changed standardization level to Informational, changed state to RFC, added RFC published event at 2020-02-27, changed IESG state to RFC Published, created obsoletes relation between draft-ietf-iasa2-rfc5377bis and RFC 5377)

[Ballot comment]
Two nits in the Abstract (and, yes, I know the first one was there in the original):

  The Trustees of the IETF Trust accepts direction from the IETF
  regarding the rights to be granted.

As “The Trustees” is plural, the verb needs to be so as well: “accept”.

There’s a missing space before the last sentence.

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Functions Operator has reviewed draft-ietf-iasa2-rfc5377bis-02, which is currently in Last Call, and has the following comments:

We understand that this document doesn't require any registry actions.

While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, we do not object.

If this assessment is not accurate, please respond as soon as possible.

Thank you,

Sabrina Tanamal
Senior IANA Services Specialist

The following Last Call announcement was sent out (ends 2019-08-14):

From: The IESG
To: IETF-Announce
CC: iasa20@ietf.org, alissa@cooperw.in, Jon Peterson , iasa2-chairs@ietf.org, draft-ietf-iasa2-rfc5377bis@ietf.org, jon.peterson@team.neustar
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents) to Informational RFC


The IESG has received a request from the IETF Administrative Support Activity
2 WG (iasa2) to consider the following document: - 'Advice to the Trustees of
the IETF Trust on Rights to Be Granted in
  IETF Documents'
  as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2019-08-14. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


  Contributors grant intellectual property rights to the IETF.  The
  IETF Trust holds and manages those rights on behalf of the IETF.  The
  Trustees of the IETF Trust are responsible for that management.  This
  management includes granting the licenses to copy, implement, and
  otherwise use IETF Contributions, among them Internet-Drafts and
  RFCs.  The Trustees of the IETF Trust accepts direction from the IETF
  regarding the rights to be granted.  This document describes the
  desires of the IETF regarding outbound rights to be granted in IETF
  Contributions.This document obsoletes RFC 5377 solely for the purpose
  of removing references to the IASA.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc5377bis/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc5377bis/ballot/


No IPR declarations have been submitted directly on this I-D.

1. Summary

This specification is a straightforward update to RFC 5377 to reflect the changes to the IETF Administrative Support Activities resulting from the IASA 2.0 effort. These are very minor changes, as the original RFC 5377 made little reference to the connection of the IETF Trust to the former IAOC. Those references have been removed, along with references to RFC 4371.

2. Review and Consensus

This document was reviewed by the IASA2.0 WG, and received a good amount of comment. A few bugs were caught after working group last call, and it took a bit of time to get a revision out. There is a consensus to advance this specification.

3. Intellectual Property

This document is not a protocol specification and it contains no technical solutions that might require a disclosure.

4. Other Points

Passed I-D nits, should be a simple fix.

1. Summary

This specification is a straightforward update to RFC 5377 to reflect the changes to the IETF Administrative Support Activities resulting from the IASA 2.0 effort. These are very minor changes, as the original RFC 5377 made little reference to the connection of the IETF Trust to the former IAOC. Those references have been removed, along with references to RFC 4371.

2. Review and Consensus

This document was reviewed by the IASA2.0 WG, and received a good amount of comment. A few bugs were caught after working group last call, and it took a bit of time to get a revision out. There is a consensus to advance this specification.

3. Intellectual Property

This document is not a protocol specification and it contains no technical solutions that might require a disclosure.

4. Other Points

Passed I-D nits, should be a simple fix.