idnits 2.17.1 draft-durand-doa-over-dns-02.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 (July 25, 2017) is 2467 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 3548 (Obsoleted by RFC 4648) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Independent Submission A. Durand 3 Internet-Draft ICANN 4 Intended status: Experimental R. Bellis 5 Expires: January 26, 2018 ISC 6 July 25, 2017 8 DOA over DNS 9 draft-durand-doa-over-dns-02 11 Abstract 13 Abstract 15 This document defines a DOA RR type to implement the Digital Object 16 Architecture over DNS. 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 http://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 January 26, 2018. 35 Copyright Notice 37 Copyright (c) 2017 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 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 54 3. The DOA Resource Record . . . . . . . . . . . . . . . . . . . 2 55 3.1. Description . . . . . . . . . . . . . . . . . . . . . . . 2 56 3.1.1. Enterprise and Type fields . . . . . . . . . . . . . 3 57 3.1.2. Location field . . . . . . . . . . . . . . . . . . . 3 58 3.1.3. Media Type . . . . . . . . . . . . . . . . . . . . . 4 59 3.1.4. Data . . . . . . . . . . . . . . . . . . . . . . . . 4 60 3.2. DOA RDATA Wire Format . . . . . . . . . . . . . . . . . . 4 61 3.3. DOA RDATA Presentation Format . . . . . . . . . . . . . . 5 62 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 63 5. Privacy Considerations . . . . . . . . . . . . . . . . . . . 5 64 6. Operational consideration . . . . . . . . . . . . . . . . . . 5 65 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 66 7.1. DOA Type Registry . . . . . . . . . . . . . . . . . . . . 5 67 7.2. DOA Location Type Registry . . . . . . . . . . . . . . . 6 68 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7 69 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 70 9.1. Normative References . . . . . . . . . . . . . . . . . . 7 71 9.2. Informative References . . . . . . . . . . . . . . . . . 7 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 74 1. Introduction 76 This document defines an RR type to implement an architecture similar 77 to the Digital Object Architecture [ITU-X.1255] within the DNS. Each 78 DOA RR contains an object type that might be opaque and private to 79 the producer and the consumer of the data and either the data (if 80 small enough to fit in the RR) or a pointer on how to retrieve the 81 actual data. 83 2. Terminology 85 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 86 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 87 "OPTIONAL" in this document are to be interpreted as described in BCP 88 14 [RFC2119] [RFC8174] when, and only when, they appear in all 89 capitals, as shown here. 91 3. The DOA Resource Record 93 3.1. Description 95 The Type value for the DOA RR is TBD. The DOA RR is class 96 independent. No special processing is required within DNS servers or 97 libraries. 99 The RDATA of the resource record comprises of five fields: DOA- 100 ENTERPRISE, DOA-TYPE, DOA-MEDIA-TYPE, DOA-LOCATION and DOA-DATA. 102 3.1.1. Enterprise and Type fields 104 The DOA-ENTERPRISE and DOA-TYPE fields are combined to indicate the 105 semantic type of the DOA record being represented by the RR. That 106 semantic is private to the producer of data hosted on an 107 authoritative DNS server and the application software using a DNS 108 stub resolver to retrieve it. 110 The DOA-ENTERPRISE field uses values as specified in the IANA SMI 111 Network Management Private Enterprise Codes Registry 112 [IANA-ENTERPRISE]. An exception to that is that the reserved value 113 of zero (0) is used to indicate that the the DOA-ENTERPRISE is not 114 set. 116 Some commonly used values of DOA-TYPE are registered in the IANA DOA 117 Type Registry Section 7.1, others are privately defined. As those 118 private types might be used in cross-organization systems, use of the 119 DOA-ENTERPRISE field is RECOMMENDED to disambiguate types. 121 3.1.2. Location field 123 The DOA-LOCATION signals how the DOA-DATA field should be interpreted 124 using the values specified in the DOA Location Type Registry 125 Section 7.2. 127 The value 0 is reserved. 129 For the value 1 ("Local"), the DOA-DATA contains the actual DOA 130 object. 132 For the value 2 ("URI") the DOA-DATA contains a UTF-8 encoded string 133 representing the URI from which the DOA object can be obtained. 135 For the value 3 ("HDL") the DOA-DATA contains a UTF-8 encoded string 136 representing the handle from the Handle System [RFC3650] from which 137 the DOA object can be obtained. 139 Other values might be defined in the future, for example for NFS, 140 LDAP, etc... 142 DNS software implementing the DOA RR type MUST NOT drop or otherwise 143 refuse to handle the DOA RRs containing an unknown or unsupported 144 DOA-location and MUST treat the DOA-DATA portion of the RR as an 145 abstract opaque field. 147 3.1.3. Media Type 149 The DOA-MEDIA-TYPE field contains the Internet media type [RFC6838] 150 for the DOA object represented by this record. 152 If a non-Local object is retrieved over a protocol that supports 153 inclusion of a media type value (e.g. an HTTP Content-Type header) 154 then the client MUST use that value (if supplied) in preference to 155 any value specified inside this resource record. In such case, the 156 DOA-MEDIA-TYPE MAY be set to NULL, length 0. 158 3.1.4. Data 160 The DOA-DATA field contains either the object's data, or some form of 161 reference specifying from where the data can be obtained, per the 162 DOA-LOCATION field above. 164 3.2. DOA RDATA Wire Format 166 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ 167 0: | | 168 | DOA-ENTERPRISE | 169 | | 170 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ 171 4: | | 172 | DOA-TYPE | 173 | | 174 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ 175 8: | DOA-LOCATION | DOA-MEDIA-TYPE / 176 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ 177 10: / / 178 / DOA-MEDIA-TYPE (continued) / 179 / / 180 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ 181 / / 182 / DOA-DATA / 183 / / 184 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ 186 DOA-ENTERPRISE: a 32-bit unsigned integer in network order. 188 DOA-TYPE: a 32-bit unsigned integer in network order. 190 DOA-LOCATION: an 8-bit unsigned integer. 192 DOA-MEDIA-TYPE: A (see [RFC1035]). The first 193 octet of the contains the number of characters to 194 follow. 196 DOA-DATA: A variable length blob of binary data. The length of the 197 DOA-DATA is not contained within the wire format of the RR and has to 198 be computed from the RDLENGTH of the entire RR once other fields have 199 been taken into account. 201 3.3. DOA RDATA Presentation Format 203 The DOA-ENTERPRISE field is presented as an unsigned 32-bit decimal 204 integer with range 0 - 4,294,967,295. 206 The DOA-TYPE field is presented as an unsigned 32-bit decimal integer 207 with range 0 - 4,294,967,295. 209 The DOA-LOCATION field is presented as an unsigned 8-bit decimal 210 integer with range 0 - 255. 212 The DOA-MEDIA-TYPE field is presented as a single . 214 The DOA-DATA is presented as Base64 encoded data [RFC3548]. White 215 space is permitted within the Base64 data. 217 4. Security Considerations 219 The use of DNSSEC is encouraged to protect the integrity of the data 220 contained in the DOA RR type. 222 5. Privacy Considerations 224 Personally identifiable information (PII) data appearing in the DOA- 225 DATA field SHOULD be encrypted. 227 6. Operational consideration 229 Some DOA records might contain large data that is only of interest to 230 a single party, as such, caching those records does not provide much 231 benefits and could be considered a denial of service attack on the 232 caching resolver infrastructure. It is thus RECOMMENDED that the TTL 233 associated with large DOA RRs be set as small as possible to avoid 234 caching. 236 7. IANA Considerations 238 7.1. DOA Type Registry 240 IANA are requested to create the DOA Type Registry with initial 241 contents as follows: 243 +--------------+-------------------------------+---------------+ 244 | Value | Name | Specification | 245 +--------------+-------------------------------+---------------+ 246 | 0 | Reserved - cannot be assigned | RFC-TBD1 | 247 | | | | 248 | 1 | contact email | RFC-TBD1 | 249 | | | | 250 | 2 | contact website | RFC-TBD1 | 251 | | | | 252 | 3 | contact telephone | RFC-TBD1 | 253 | | | | 254 | 4 - 99 | Unassigned | | 255 | | | | 256 | 100 | public key | RFC-TBD1 | 257 | | | | 258 | 101 - 99,999 | Unassigned | | 259 | | | | 260 | 100000 - | Reserved for Private Use | RFC-TBD1 | 261 +--------------+-------------------------------+---------------+ 263 Assignments in the 1-99,999 range in this registry require Expert 264 Review. 266 7.2. DOA Location Type Registry 268 IANA are requested to create the DOA Location Type Registry with 269 initial contents as follows: 271 +-----------+-------------------------------+---------------+ 272 | Value | Location | Specification | 273 +-----------+-------------------------------+---------------+ 274 | 0 | Reserved - cannot be assigned | RFC-TBD1 | 275 | | | | 276 | 1 | Local | RFC-TBD1 | 277 | | | | 278 | 2 | URI | RFC-TBD1 | 279 | | | | 280 | 3 | HDL | RFC-TBD1 | 281 | | | | 282 | 4 - 199 | Unassigned | | 283 | | | | 284 | 200 - 254 | Reserved for Private Use | RFC-TBD1 | 285 | | | | 286 | 255 | Reserved - cannot be assigned | RFC-TBD1 | 287 +-----------+-------------------------------+---------------+ 289 Assignments in the 4-199 range in this registry require Expert 290 Review. 292 8. Acknowledgments 294 9. References 296 9.1. Normative References 298 [IANA-ENTERPRISE] 299 IANA, "SMI Network Management Private Enterprise Codes 300 Registry", n.d., . 303 [RFC1035] Mockapetris, P., "Domain names - implementation and 304 specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, 305 November 1987, . 307 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 308 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 309 RFC2119, March 1997, 310 . 312 [RFC3548] Josefsson, S., Ed., "The Base16, Base32, and Base64 Data 313 Encodings", RFC 3548, DOI 10.17487/RFC3548, July 2003, 314 . 316 [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type 317 Specifications and Registration Procedures", BCP 13, RFC 318 6838, DOI 10.17487/RFC6838, January 2013, 319 . 321 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 322 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 323 May 2017, . 325 9.2. Informative References 327 [ITU-X.1255] 328 ITU, "Framework for discovery of identity management 329 information", n.d., 330 . 332 [RFC3650] Sun, S., Lannom, L., and B. Boesch, "Handle System 333 Overview", RFC 3650, DOI 10.17487/RFC3650, November 2003, 334 . 336 Authors' Addresses 338 Alain Durand 339 Internet Corporation for Assigned Names and Numbers 340 801 17th St NW Suite 400 341 Washington DC 20006 342 USA 344 Email: Alain.Durand@icann.org 346 Ray Bellis 347 Internet Systems Consortium, Inc. 348 950 Charter Street 349 Redwood City CA 94063 350 USA 352 Phone: +1 650 423 1200 353 Email: ray@isc.org