Shepherd writeup
rfc8288-08

1. Summary

Barry Leiba is the document shepherd; Alexey Melnikov is the responsible AD.

This specification defines a model for the relationships between
resources on the Web ("links") and the type of those relationships
("link relation types").  It also defines the serialisation of such
links in HTTP headers with the Link header field.  This is a revision of
RFC 5988, and obsoletes that document.

2. Review and Consensus

This is mostly a piece of work that needed to get done but that no one
had much interest in doing.  Mark took it on and got feedback, but the
document shepherd can't find any record of discussion in any mailing
list archives.  Mark brought it to DISPATCH, which raised no interest
either.

There was a good amount of discussion on the github issues list, which
had good representation from the community:
  https://github.com/mnot/I-D/issues?q=is:issue label:rfc5988bis

The bottom line is that the document is ready to go, and any last-call
discussion will be adequate.  This is a good example of a document for
which silence  is a reasonable measure of consensus.  The only tricky
bit is that Section 4.2 is proposing a different model for maintaining
the registry, and we need to make sure there's good communication with
IANA on that.

3. Intellectual Property

The author is in full compliance with BCPs 78 and 79.  There are no IPR
statements related to RFC 5988 nor to this replacement.

4. Other Points

This document depends upon 5987bis, which is in the RFC Editor queue.

This document inherits the pre-5378 disclaimer from RFC 5988.

As mentioned in section 2 above, the Section 4.2 of the document
proposes a significant difference to normal registry management.  The
proposed change makes sense for the community the registry is intended
for, and it will be important to check the IANA reviews and to discuss
the requested changes with IANA during last call.
Back