RFC 9727 on api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs

rfc-editor@rfc-editor.org Fri, 13 June 2025 21:18 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 418EF34C59FF; Fri, 13 Jun 2025 14:18:03 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 054512673A2; Fri, 13 Jun 2025 14:18:03 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9727 on api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20250613211803.054512673A2@rfcpa.rfc-editor.org>
Date: Fri, 13 Jun 2025 14:18:03 -0700
Message-ID-Hash: ZPELRROIP3S4O5KI7HNG76VZAROGIXOR
X-Message-ID-Hash: ZPELRROIP3S4O5KI7HNG76VZAROGIXOR
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, httpapi@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/tJ0JlP3hYZt1FHF_qQGRWBFuKUo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9727

        Title:      api-catalog: A Well-Known URI and 
                    Link Relation to Help Discovery of APIs 
        Author:     K. Smith
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2025
        Mailbox:    kevin.smith@vodafone.com
        Pages:      17
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-httpapi-api-catalog-08.txt

        URL:        https://www.rfc-editor.org/info/rfc9727

        DOI:        10.17487/RFC9727

This document defines the "api-catalog" well-known URI and link
relation. It is intended to facilitate automated discovery and usage
of published Application Programming Interfaces (APIs). A request to
the api-catalog resource will return a document providing information
about, and links to, the Publisher's APIs.

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team