--- 1/draft-ietf-cbor-network-addresses-12.txt 2021-10-22 08:13:14.300317853 -0700 +++ 2/draft-ietf-cbor-network-addresses-13.txt 2021-10-22 08:13:14.324318452 -0700 @@ -1,19 +1,19 @@ CBOR Working Group M. Richardson Internet-Draft Sandelman Software Works Intended status: Standards Track C. Bormann -Expires: 23 April 2022 Universität Bremen TZI - 20 October 2021 +Expires: 25 April 2022 Universität Bremen TZI + 22 October 2021 CBOR tags for IPv4 and IPv6 addresses and prefixes - draft-ietf-cbor-network-addresses-12 + draft-ietf-cbor-network-addresses-13 Abstract This specification defines two CBOR Tags for use with IPv6 and IPv4 addresses and prefixes. // RFC-EDITOR-please-remove: This work is tracked at // https://github.com/cbor-wg/cbor-network-address Status of This Memo @@ -24,21 +24,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on 23 April 2022. + This Internet-Draft will expire on 25 April 2022. Copyright Notice Copyright (c) 2021 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights @@ -66,22 +66,22 @@ 5. CDDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 7.1. Tag 54 - IPv6 . . . . . . . . . . . . . . . . . . . . . . 10 7.2. Tag 52 - IPv4 . . . . . . . . . . . . . . . . . . . . . . 10 7.3. Tags 260 and 261 . . . . . . . . . . . . . . . . . . . . 10 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 8.1. Normative References . . . . . . . . . . . . . . . . . . 10 8.2. Informative References . . . . . . . . . . . . . . . . . 11 Appendix A. Changelog . . . . . . . . . . . . . . . . . . . . . 11 - Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 12 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 + Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 11 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 1. Introduction [RFC8949] defines a number of CBOR Tags for common items. Tags 260 and 261 were later defined in drafts listed with IANA [IANA.cbor-tags]. These tags were intended to cover addresses (260) and prefixes (261). Tag 260 distinguishes between IPv6, IPv4, and MAC [RFC7042] addresses only through the length of the byte string, making it impossible, for example, to drop trailing zeros in the encoding of IP addresses. Tag 261 was not documented well enough for @@ -138,25 +138,25 @@ they represent information that is commonly used to specify both the network prefix and the IP address of an interface. The length of the byte string is always 16 bytes (for IPv6) and 4 bytes (for IPv4). This form is called the Interface Format. Interface Format definitions support an optional third element to the array, which is to be used as the IPv6 Link-Local zone identifier - from Section 4 of [RFC3542] and Section 6 of [RFC4007]; for symmetry - this is also provided for IPv4 as in [RFC4001] and [RFC6991]. The - zone identifier may be an integer, in which case it is to be - interpreted as the interface index. It may be a text string, in - which case it is to be interpreted as an interface name. + from Section 6 of [RFC4007]; for symmetry this is also provided for + IPv4 as in [RFC4001] and [RFC6991]. The zone identifier may be an + integer, in which case it is to be interpreted as the interface + index. It may be a text string, in which case it is to be + interpreted as an interface name. As explained in [RFC4007] the zone identifiers are strictly local to the node. They are useful for communications within a node about connected addresses (for instance, where a link-local peer is discovered by one daemon, and another daemon needs to be informed). They may also have utility in some management protocols. In the cases where the Interface Format is being used to represent only an address with a zone identifier, and no interface prefix information, then the prefix length may be replaced with the CBOR @@ -438,25 +438,20 @@ Representation (CBOR)", STD 94, RFC 8949, DOI 10.17487/RFC8949, December 2020, . 8.2. Informative References [IANA.cbor-tags] IANA, "Concise Binary Object Representation (CBOR) Tags", . - [RFC3542] Stevens, W., Thomas, M., Nordmark, E., and T. Jinmei, - "Advanced Sockets Application Program Interface (API) for - IPv6", RFC 3542, DOI 10.17487/RFC3542, May 2003, - . - [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 4001, DOI 10.17487/RFC4001, February 2005, . [RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and B. Zill, "IPv6 Scoped Address Architecture", RFC 4007, DOI 10.17487/RFC4007, March 2005, .