RFC 9512 on YAML Media Type

rfc-editor@rfc-editor.org Wed, 14 February 2024 22:01 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D3D3C15108B; Wed, 14 Feb 2024 14:01:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.959
X-Spam-Level:
X-Spam-Status: No, score=-3.959 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4tpF7bhp1djD; Wed, 14 Feb 2024 14:01:04 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40F0EC151084; Wed, 14 Feb 2024 14:01:04 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 2BF101957AE5; Wed, 14 Feb 2024 14:01:04 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9512 on YAML Media Type
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, httpapi@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240214220104.2BF101957AE5@rfcpa.amsl.com>
Date: Wed, 14 Feb 2024 14:01:04 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/jPkhXFFQKVPjvfr9zUwKdZ-vqOY>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Feb 2024 22:01:08 -0000

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

        
        RFC 9512

        Title:      YAML Media Type 
        Author:     R. Polli,
                    E. Wilde,
                    E. Aro
        Status:     Informational
        Stream:     IETF
        Date:       February 2024
        Mailbox:    robipolli@gmail.com,
                    erik.wilde@dret.net,
                    eemeli@gmail.com
        Pages:      13
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-httpapi-yaml-mediatypes-10.txt

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

        DOI:        10.17487/RFC9512

This document registers the application/yaml media type and the +yaml
structured syntax suffix with IANA.  Both identify document
components that are serialized according to the YAML specification.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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
Association Management Solutions, LLC