Skip to main content

Linkset: Media Types and a Link Relation Type for Link Sets
draft-ietf-httpapi-linkset-10

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-httpapi-linkset@ietf.org, francesca.palombini@ericsson.com, httpapi-chairs@ietf.org, httpapi@ietf.org, rfc-editor@rfc-editor.org, rsalz@akamai.com
Subject: Protocol Action: 'Linkset: Media Types and a Link Relation Type for Link Sets' to Proposed Standard (draft-ietf-httpapi-linkset-10.txt)

The IESG has approved the following document:
- 'Linkset: Media Types and a Link Relation Type for Link Sets'
  (draft-ietf-httpapi-linkset-10.txt) as Proposed Standard

This document is the product of the Building Blocks for HTTP APIs Working
Group.

The IESG contact persons are Murray Kucherawy and Francesca Palombini.

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


Ballot Text

Technical Summary

This specification defines two formats and respective media types for
representing sets of links as stand-alone documents.  One format is
JSON-based, the other aligned with the format for representing links
in the HTTP "Link" header field.  This specification also introduces
a link relation type to support discovery of sets of links. This is intended
to be used when RFC 8288 links are not usable, and delivering a set of links
as a stand-alone document is preferable.

Working Group Summary

This is a product of the HTTPAPI working group.

The document had detailed review from many WG members and while there
was some discussion, there was nothing especially controversial, nor rough
points in any consensus issues.

This was originally set to be Informational, but following a question
from one of the Directorate reviews, confirmation on the wg mailing
list, and IETF Last Call this document was changed to Proposed Standard.

Document Quality

There are several implementations existing and planned. These are noted in
Appendix B of the draft, which will be removed before publication as an RFC.

Personnel

The shepherd for this document was Rich Salz; the responsible AD is Francesca
Palombini.


RFC Editor Note