draft-ietf-cbor-network-addresses-11.txt   draft-ietf-cbor-network-addresses-12.txt 
CBOR Working Group M. Richardson CBOR Working Group M. Richardson
Internet-Draft Sandelman Software Works Internet-Draft Sandelman Software Works
Intended status: Standards Track C. Bormann Intended status: Standards Track C. Bormann
Expires: 11 April 2022 Universit├Ąt Bremen TZI Expires: 23 April 2022 Universit├Ąt Bremen TZI
8 October 2021 20 October 2021
CBOR tags for IPv4 and IPv6 addresses and prefixes CBOR tags for IPv4 and IPv6 addresses and prefixes
draft-ietf-cbor-network-addresses-11 draft-ietf-cbor-network-addresses-12
Abstract Abstract
This specification defines two CBOR Tags for use with IPv6 and IPv4 This specification defines two CBOR Tags for use with IPv6 and IPv4
addresses and prefixes. addresses and prefixes.
// RFC-EDITOR-please-remove: This work is tracked at // RFC-EDITOR-please-remove: This work is tracked at
// https://github.com/cbor-wg/cbor-network-address // https://github.com/cbor-wg/cbor-network-address
Status of This Memo Status of This Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 11 April 2022. This Internet-Draft will expire on 23 April 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 49 skipping to change at page 2, line 49
Appendix A. Changelog . . . . . . . . . . . . . . . . . . . . . 11 Appendix A. Changelog . . . . . . . . . . . . . . . . . . . . . 11
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 12 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
[RFC8949] defines a number of CBOR Tags for common items. Tags 260 [RFC8949] defines a number of CBOR Tags for common items. Tags 260
and 261 were later defined in drafts listed with IANA and 261 were later defined in drafts listed with IANA
[IANA.cbor-tags]. These tags were intended to cover addresses (260) [IANA.cbor-tags]. These tags were intended to cover addresses (260)
and prefixes (261). Tag 260 distinguishes between IPv6, IPv4, and and prefixes (261). Tag 260 distinguishes between IPv6, IPv4, and
MAC [RFC7042] addresses only through the length of the byte string MAC [RFC7042] addresses only through the length of the byte string,
making it impossible, for example, to drop trailing zeros in the making it impossible, for example, to drop trailing zeros in the
encoding of IP addresses. Tag 261 was not documented well enough for encoding of IP addresses. Tag 261 was not documented well enough for
use. use.
This specification defines tags 54 and 52 achieving an explicit This specification defines tags 54 and 52 achieving an explicit
indication of IPv6 or IPv4 by the tag number. These new tags are indication of IPv6 or IPv4 by the tag number. These new tags are
intended to be used in preference to tags 260 and 261. They provide intended to be used in preference to tags 260 and 261. They provide
formats for IPv6 and IPv4 addresses, prefixes, and addresses with formats for IPv6 and IPv4 addresses, prefixes, and addresses with
prefixes, achieving an explicit indication of IPv6 or IPv4. The prefixes, achieving an explicit indication of IPv6 or IPv4. The
prefix format omits trailing zeroes in the address part. (Due to the prefix format omits trailing zeroes in the address part. (Due to the
complexity of testing, the value of omitting trailing zeros for the complexity of testing, the value of omitting trailing zeros for the
pure address format was considered non-essential and support for that pure address format was considered non-essential and support for that
is not provided in this specification.) This specification does not is not provided in this specification.) This specification does not
deal with 6- or 8-byte Ethernet addresses. deal with MAC addresses (Section 2 of [RFC7042]) such as they are
used for Ethernet.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
3. Protocol 3. Protocol
skipping to change at page 11, line 14 skipping to change at page 11, line 14
[RFC8949] Bormann, C. and P. Hoffman, "Concise Binary Object [RFC8949] Bormann, C. and P. Hoffman, "Concise Binary Object
Representation (CBOR)", STD 94, RFC 8949, Representation (CBOR)", STD 94, RFC 8949,
DOI 10.17487/RFC8949, December 2020, DOI 10.17487/RFC8949, December 2020,
<https://www.rfc-editor.org/info/rfc8949>. <https://www.rfc-editor.org/info/rfc8949>.
8.2. Informative References 8.2. Informative References
[IANA.cbor-tags] [IANA.cbor-tags]
IANA, "Concise Binary Object Representation (CBOR) Tags", IANA, "Concise Binary Object Representation (CBOR) Tags",
<http://www.iana.org/assignments/cbor-tags>. <https://www.iana.org/assignments/cbor-tags>.
[RFC3542] Stevens, W., Thomas, M., Nordmark, E., and T. Jinmei, [RFC3542] Stevens, W., Thomas, M., Nordmark, E., and T. Jinmei,
"Advanced Sockets Application Program Interface (API) for "Advanced Sockets Application Program Interface (API) for
IPv6", RFC 3542, DOI 10.17487/RFC3542, May 2003, IPv6", RFC 3542, DOI 10.17487/RFC3542, May 2003,
<https://www.rfc-editor.org/info/rfc3542>. <https://www.rfc-editor.org/info/rfc3542>.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, DOI 10.17487/RFC4001, February 2005, Addresses", RFC 4001, DOI 10.17487/RFC4001, February 2005,
<https://www.rfc-editor.org/info/rfc4001>. <https://www.rfc-editor.org/info/rfc4001>.
 End of changes. 6 change blocks. 
7 lines changed or deleted 8 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/