[Cbor] RFC 9164 on Concise Binary Object Representation (CBOR) Tags for IPv4 and IPv6 Addresses and Prefixes

rfc-editor@rfc-editor.org Mon, 13 December 2021 23:36 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 454183A0CA0; Mon, 13 Dec 2021 15:36:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kpshgmFR1vJD; Mon, 13 Dec 2021 15:36:10 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EBDC3A0C49; Mon, 13 Dec 2021 15:36:08 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 499) id 5AD9F1DE0; Mon, 13 Dec 2021 15:36:07 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, cbor@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20211213233607.5AD9F1DE0@rfc-editor.org>
Date: Mon, 13 Dec 2021 15:36:07 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/snHTDWxOoesZ8Vs1Igdwt2lHYiw>
Subject: [Cbor] RFC 9164 on Concise Binary Object Representation (CBOR) Tags for IPv4 and IPv6 Addresses and Prefixes
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Dec 2021 23:36:20 -0000

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

        
        RFC 9164

        Title:      Concise Binary Object Representation (CBOR) 
                    Tags for IPv4 and IPv6 Addresses 
                    and Prefixes 
        Author:     M. Richardson,
                    C. Bormann
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2021
        Mailbox:    mcr+ietf@sandelman.ca,
                    cabo@tzi.org
        Pages:      10
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-cbor-network-addresses-13.txt

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

        DOI:        10.17487/RFC9164

This specification defines two Concise Binary Object Representation
(CBOR) tags for use with IPv6 and IPv4 addresses and prefixes.

This document is a product of the Concise Binary Object Representation Maintenance and Extensions 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
Association Management Solutions, LLC