idnits 2.17.1 draft-ietf-cbor-network-addresses-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (6 March 2021) is 1148 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'BCP14' is defined on line 142, but no explicit reference was found in the text Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CBOR Working Group M. Richardson 3 Internet-Draft Sandelman Software Works 4 Intended status: Standards Track 6 March 2021 5 Expires: 7 September 2021 7 CBOR tags for IPv4 and IPv6 addresses and prefixes 8 draft-ietf-cbor-network-addresses-00 10 Abstract 12 This document describes two CBOR Tags to be used with IPv4 and IPv6 13 addresses and prefixes. 15 RFC-EDITOR-please remove: This work is tracked at 16 https://github.com/mcr/cbor-network-address.git 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on 7 September 2021. 35 Copyright Notice 37 Copyright (c) 2021 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 42 license-info) in effect on the date of publication of this document. 43 Please review these documents carefully, as they describe your rights 44 and restrictions with respect to this document. Code Components 45 extracted from this document must include Simplified BSD License text 46 as described in Section 4.e of the Trust Legal Provisions and are 47 provided without warranty as described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 2. Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2.1. IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2.2. IPv4 . . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 56 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 57 4.1. TBD1 - IPv6 . . . . . . . . . . . . . . . . . . . . . . . 3 58 4.2. TBD2 - IPv4 . . . . . . . . . . . . . . . . . . . . . . . 3 59 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 60 6. Changelog . . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 7. Normative References . . . . . . . . . . . . . . . . . . . . 3 62 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 64 1. Introduction 66 [RFC8949] defines a number of CBOR Tags for common items. 68 Not included are ones to indicate if the item is an IPv4 or IPv6 69 address, or if it is an address plus prefix length. This document 70 defines them. 72 2. Protocol 74 These tags can applied to byte strings to represent a single address. 76 When applied to an array, the represent a CIDR-style prefix. When a 77 byte string (without prefix) appears in a context where a prefix is 78 expected, then it is to be assumed that all bits are relevant. That 79 is, for IPv4, a /32 is implied, and for IPv6, a /128 is implied. 81 2.1. IPv6 83 IANA has allocated tag TBD1 for IPv6 uses. 85 An IPv6 address is to be encoded as up to sixteen-byte bytestring 86 ([RFC8949] section, 3.1, major type 2), prefixed with tag TBD1. 87 Trailing zero octets may be omitted. 89 An IPv6 prefix, such as 2001:db8:1234::/48 is to be encoded as a two 90 element array, with the length of the prefix first: 92 TBD1([ 48, h'20010db81234']) 94 2.2. IPv4 96 IANA has allocated tag TBD2 for IPv4 uses. 98 An IPv4 address is to be encoded as a four-byte bytestring ([RFC8949] 99 section, 3.1, major type 2), prefixed with tag TBD2. Trailing zero 100 octets may be omitted. 102 An IPv4 prefix, such as 192.0.2.1/24 is to be encoded as a two 103 element array, with the length of the prefix first: 105 TBD2([ 24, h'C0000201']) 107 3. Security Considerations 109 Identifying which byte sequences in a protocol are addresses may 110 allow an attacker or eavesdropper to better understand what parts of 111 a packet to attack. 113 Reading the relevant RFC may provide more information, so it would 114 seem that any additional security that was provided by not being able 115 to identify what are IP addresses falls into the security by 116 obscurity category. 118 4. IANA Considerations 120 IANA is asked to allocate two tags from the Specification Required 121 area of the Concise Binary Object Representation (CBOR) Tags, in the 122 ("1+1") area. 124 4.1. TBD1 - IPv6 126 Data Item: byte-string and array 127 Semantics: IPv6 or [IPv6,prefixlen] 129 4.2. TBD2 - IPv4 131 Data Item: byte-string and array 132 Semantics: IPv4 or [IPv4,prefixlen] 134 5. Acknowledgements 136 none yet 138 6. Changelog 140 7. Normative References 142 [BCP14] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 143 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 144 May 2017, . 146 [RFC8949] Bormann, C. and P. Hoffman, "Concise Binary Object 147 Representation (CBOR)", STD 94, RFC 8949, 148 DOI 10.17487/RFC8949, December 2020, 149 . 151 Author's Address 153 Michael Richardson 154 Sandelman Software Works 156 Email: mcr+ietf@sandelman.ca