Web Linking
RFC 8288

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: rfc-editor@rfc-editor.org, alexey.melnikov@isode.com, barryleiba@computer.org, draft-nottingham-rfc5988bis@ietf.org, The IESG <iesg@ietf.org>
Subject: Protocol Action: 'Web Linking' to Proposed Standard (draft-nottingham-rfc5988bis-08.txt)

The IESG has approved the following document:
- 'Web Linking'
  (draft-nottingham-rfc5988bis-08.txt) as Proposed Standard

This document has been reviewed in the IETF but is not the product of an IETF
Working Group.

The IESG contact person is Alexey Melnikov.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-nottingham-rfc5988bis/


Technical Summary

   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 document obsoletes RFC 5988.

Working Group Summary

  This is not a WG document, but it is based on experience running
  the Web Linking registry.

Document Quality

   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.

Personnel

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