idnits 2.17.1 draft-ietf-eppext-tmch-smd-01.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 (February 26, 2015) is 3337 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO3166-2' ** Obsolete normative reference: RFC 6982 (Obsoleted by RFC 7942) -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '2' Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force G. Lozano 3 Internet-Draft ICANN 4 Intended status: Standards Track February 26, 2015 5 Expires: August 30, 2015 7 Mark and Signed Mark Objects Mapping 8 draft-ietf-eppext-tmch-smd-01 10 Abstract 12 This document describes the format of a mark and a digitally signed 13 mark, referred to as a signed mark and the Signed Mark Data (SMD) 14 file as defined by the ICANN Trademark Clearinghouse. 16 Status of this Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on August 30, 2015. 33 Copyright Notice 35 Copyright (c) 2015 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 52 2. Object Description . . . . . . . . . . . . . . . . . . . . . . 3 53 2.1. Holder and Contacts objects . . . . . . . . . . . . . . . 3 54 2.2. Mark . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 55 2.3. Signed Mark . . . . . . . . . . . . . . . . . . . . . . . 9 56 2.4. Encoded Signed Mark . . . . . . . . . . . . . . . . . . . 12 57 2.5. Appendix A. base64 encoded signedMark . . . . . . . . . . 13 58 3. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 15 59 3.1. Signed Mark Schema . . . . . . . . . . . . . . . . . . . . 15 60 3.2. Mark Schema . . . . . . . . . . . . . . . . . . . . . . . 18 61 4. Implementation Status . . . . . . . . . . . . . . . . . . . . 23 62 4.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . . 24 63 4.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 24 64 4.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . . 25 65 4.4. REngin v3.7 . . . . . . . . . . . . . . . . . . . . . . . 25 66 4.5. Uniregistry Corp. Shared Registry System (uSRS) . . . . . 26 67 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 26 68 6. Change History . . . . . . . . . . . . . . . . . . . . . . . . 26 69 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 70 8. Security Considerations . . . . . . . . . . . . . . . . . . . 28 71 9. Normative References . . . . . . . . . . . . . . . . . . . . . 28 72 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 29 74 1. Introduction 76 This document describes the format of a mark and a digitally signed 77 mark, referred to as a signed mark and the Signed Mark Data (SMD) 78 file as defined by the ICANN Trademark Clearinghouse. This document 79 provides a framework that can be referenced by application protocols 80 like the Extensible Provisioning Protocol (EPP), defined in 81 [RFC5730]. 83 1.1. Terminology 85 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 86 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 87 document are to be interpreted as described in RFC 2119 [RFC2119]. 89 XML is case sensitive. Unless stated otherwise, XML specifications 90 and examples provided in this document MUST be interpreted in the 91 character case presented in order to develop a conforming 92 implementation. 94 "signedMark-1.0" is used as an abbreviation for 95 "urn:ietf:params:xml:ns:signedMark-1.0". The XML namespace prefix 96 "smd" is used, but implementations MUST NOT depend on it and instead 97 employ a proper namespace-aware XML parser and serializer to 98 interpret and output the XML documents. 100 "mark-1.0" is used as an abbreviation for 101 "urn:ietf:params:xml:ns:mark-1.0". The XML namespace prefix "mark" 102 is used, but implementations MUST NOT depend on it and instead employ 103 a proper namespace-aware XML parser and serializer to interpret and 104 output the XML documents. 106 2. Object Description 108 This section defines the objects associated with marks and signed 109 marks. Empty complex element types and abstract elements are defined 110 to support additional mark and signed mark definition using XSD 111 substitution groups. Support for replacement through the XSD 112 substitution groups is included in the descriptions of the objects. 114 2.1. Holder and Contacts objects 116 Marks are linked to Holder objects and optionally linked to Contacts 117 objects. This section defines the and 118 objects. 120 o The child elements of include: 122 * An OPTIONAL element that contains the name of the 123 holder. A MUST be specified in case is 124 not specified. 126 * An OPTIONAL element that contains the name of the 127 organization holder of the mark. A MUST be 128 specified in case is not specified. 130 * A element that contains the address information of 131 the holder of a mark. A contains the following 132 child elements: 134 + One, two or three OPTIONAL elements that 135 contains the organization's street address. 137 + A element that contains the organization's city. 139 + An OPTIONAL element that contains the 140 organization's state or province. 142 + An OPTIONAL element that contains the 143 organization's postal code. 145 + A element that contains the organization's country 146 code. This a two-character code from [ISO3166-2]. 148 * An OPTIONAL element that contains the 149 organization's voice telephone number. 151 * An OPTIONAL element that contains the organization's 152 facsimile telephone number. 154 * An OPTIONAL element that contains the email 155 address of the holder. 157 o The child elements of include: 159 * A element that contains name of the responsible 160 person. 162 * An OPTIONAL element that contains the name of the 163 organization of the contact. 165 * A element that contains the address information of 166 the contact. A contains the following child 167 elements: 169 + One, two or three OPTIONAL elements that 170 contains the contact's street address. 172 + A element that contains the contact's city. 174 + An OPTIONAL element that contains the contact's 175 state or province. 177 + An OPTIONAL element that contains the contact's 178 postal code. 180 + A element that contains the contact's country 181 code. This a two-character code from [ISO3166-2]. 183 * A element that contains the contact's voice 184 telephone number. 186 * An OPTIONAL element that contains the contact's 187 facsimile telephone number. 189 * A element that contains the contact's email 190 address. 192 2.2. Mark 194 A element that describes an applicant's prior right to a 195 given domain name. 197 A element substitutes for the 198 abstract element to define a concrete definition of a mark. The 199 element can be replaced by other mark definitions 200 using the XML schema substitution groups feature. 202 The child elements of the element include: 204 One or more , and 205 elements that contains the detailed information of marks. 207 o A element that contains the following child 208 elements. 210 * A element that contains an identifier of the mark. 211 The identifier MUST be globally unique in relation to the 212 repository of marks. A value is a concatenation of 213 the local identifier, followed by a hyphen ("-", ASCII value 214 0x002D), followed by the issuer identifier. 216 * A element that contains the mark text string. 218 * One or more elements that contains the 219 information of the holder of the mark. An "entitlement" 220 attribute is used to identify the entitlement of the holder, 221 possible values are: owner, assignee and licensee. 223 * Zero or more OPTIONAL elements that contains the 224 information of the representative of the mark registration. A 225 "type" attribute is used to identify the type of contact, 226 possible values are: owner, agent or thirdparty. 228 * A element that contains the two-character 229 code of the jurisdiction where the trademark was registered. 230 This is a two-character code from [WIPO.ST3]. 232 * Zero or more OPTIONAL elements that contain the 233 Nice Classification class numbers of the mark as defined in the 234 Nice List of Classes [1]. 236 * Zero or more OPTIONAL elements that contain the 237 A-label form of the label that correspond to the . 240 * A element that contains the full 241 description of the goods and services mentioned in the mark 242 registration document. 244 * An OPTIONAL element that contains the trademark 245 application ID registered in the trademark office. 247 * An OPTIONAL element that contains the date the 248 trademark was applied for. 250 * A element that contains the trademark 251 registration number registered in the trademark office. 253 * A element that contains the date the trademark 254 was registered. 256 * An OPTIONAL element that contains the expiration 257 date of the trademark. 259 o A element that contains the following child 260 elements. 262 * A element that contains an identifier of the mark. 263 The identifier MUST be globally unique in relation to the 264 repository of marks. A value is a concatenation of 265 the local identifier, followed by a hyphen ("-", ASCII value 266 0x002D), followed by the issuer identifier. 268 * A element that contains the mark text string. 270 * One or more elements that contains the 271 information of the holder of the mark. An "entitlement" 272 attribute is used to identify the entitlement of the holder, 273 possible values are: owner, assignee and licensee. 275 * Zero or more OPTIONAL elements that contains the 276 information of the representative of the mark registration. A 277 "type" attribute is used to identify the type of contact, 278 possible values are: owner, agent or thirdparty. 280 * One or more elements that contain the 281 countries and region of the country where the mark is 282 protected. The element contains the 283 following child elements: 285 + A element that contains the two-character code of 286 the country in which the mark is protected. This is a two- 287 character code from [ISO3166-2]. 289 + An OPTIONAL element that contains the name of 290 a city, state, province or other geographic region of in which the mark is protected. 293 + Zero or more OPTIONAL elements that contains 294 the two-character code of the countries of the ruling. This 295 is a two-character code from [ISO3166-2]. 297 * Zero or more OPTIONAL elements that contain the 298 A-label form of the label that correspond to the . 301 * A element that contains the full 302 description of the goods and services mentioned in the mark 303 registration document. 305 * A element that contains the number of the mark of 306 the treaty or statute. 308 * A element that contains the date of protection 309 of the mark. 311 * A element that contains the title of the treaty or 312 statute. 314 * A element that contains the execution date of 315 the treaty or statute. 317 o A element that contains the following child elements. 319 * A element that contains an identifier of the mark. 320 The identifier MUST be globally unique in relation to the 321 repository of marks. A value is a concatenation of 322 the local identifier, followed by a hyphen ("-", ASCII value 323 0x002D), followed by the issuer identifier. 325 * A element that contains the mark text string. 327 * One or more elements that contains the 328 information of the holder of the mark. An "entitlement" 329 attribute is used to identify the entitlement of the holder, 330 possible values are: owner, assignee and licensee. 332 * Zero or more OPTIONAL elements that contains the 333 information of the representative of the mark registration. A 334 "type" attribute is used to identify the type of contact, 335 possible values are: owner, agent or thirdparty. 337 * Zero or more OPTIONAL elements that contain the 338 A-label form of the label that correspond to the . 341 * A element that contains the full 342 description of the goods and services mentioned in the mark 343 registration document. 345 * A element that contains the reference number of 346 the court's opinion. 348 * A element that contains the date of protection 349 of the mark. 351 * A element that contains the two-character code of the 352 country where the court is located. This a two-character code 353 from [ISO3166-2]. 355 * Zero or more OPTIONAL elements that contains the 356 name of a city, state, province or other geographic region of 357 in which the mark is protected. In case is specified a default-deny approach MUST be assumed 359 regarding the regions of a country. 361 * A element that contains the name of the court. 363 2.3. Signed Mark 365 The is the fragment of XML that is digitally signed 366 using XML Signature [2]. The includes a required 367 "id" attribute of type XSD ID for use with an IDREF URI from the 368 Signature element. The certificate of the issuer MAY be issued by a 369 Certificate Authority (CA) that can be chained with the issuer's 370 certificate by the validating client. 372 A element substitutes for the abstract element to define a concrete definition 374 of a signed mark. The element can be 375 replaced by other signed mark definitions using the XML schema 376 substitution groups feature. 378 The child elements of the element include: 380 o The value is a concatenation of the local identifier, 381 followed by a hyphen ("-", ASCII value 0x002D), followed by the 382 issuer identifier. 384 o A element that contains the information of the 385 issuer of the mark registration. A "issuerID" attribute is used 386 to specify the issuer identifier. The child elements include: 388 * A element that contains the organization name of the 389 issuer. 391 * A element that contains the issuer customer support 392 email address. 394 * An OPTIONAL element that contains the HTTP URL of the 395 issuer's site. 397 * An OPTIONAL element that contains the issuer's 398 voice telephone number. 400 o A element that contains the creation date and time 401 of the signed mark. 403 o A element that contains the expiration date and 404 time of the signed mark. 406 o A element that contains the mark information as 407 defined in the Mark (Section 2.2) section. 409 o A XML Signature [2] for the . Use of 410 a namespace prefix, like "dsig", is recommended for the 411 "http://www.w3.org/TR/xmldsig-core/" elements. 413 The following is an example using the XML 414 Signature [2] to sign all of the elements of 415 element. 417 418 420 0000001751376056503931-65535 421 422 ICANN TMCH TESTING TMV 423 notavailable@example.com 424 http://www.example.com 425 +32.000000 426 427 2013-08-09T13:55:03.931Z 428 2017-07-23T22:00:00.000Z 429 430 431 00052013734689731373468973-65535 432 Test & Validate 433 434 Ag corporation 435 436 1305 Bright Avenue 437 Arcadia 438 CA 439 90028 440 US 441 442 443 444 Tony Holland 445 Ag corporation 446 447 1305 Bright Avenue 448 Arcadia 449 CA 450 90028 451 US 452 453 +1.2025562302 454 +1.2025562301 455 info@agcorporation.com 456 457 US 458 15 459 testandvalidate 460 test---validate 461 testand-validate 462 test-et-validate 463 test-validate 464 test--validate 465 test-etvalidate 466 testetvalidate 467 testvalidate 468 testet-validate 469 guitar 470 1234 471 2012-12-31T23:00:00.000Z 472 473 474 475 476 478 480 481 482 484 485 487 wgyW3nZPoEfpptlhRILKnOQnbdtU6ArM7ShrAfHgDFg= 488 489 490 491 jMu4PfyQGiJBF0GWSEPFCJjmywCEqR2h4LD+ge6XQ+JnmKFFCuCZS/3SLKAx0L1w 492 QDFO2e0Y69k2G7/LGE37X3vOflobFM1oGwja8+GMVraoto5xAd4/AF7eHukgAymD 493 o9toxoa2h0yV4A4PmXzsU6S86XtCcUE+S/WM72nyn47zoUCzzPKHZBRyeWehVFQ+ 494 jYRMIAMzM57HHQA+6eaXefRvtPETgUO4aVIVSugc4OUAZZwbYcZrC6wOaQqqqAZi 495 30aPOBYbAvHMSmWSS+hFkbshomJfHxb97TD2grlYNrQIzqXk7WbHWy2SYdA+sI/Z 496 ipJsXNa6osTUw1CzA7jfwA== 497 498 499 500 501 MIIESTCCAzGgAwIBAgIBAjANBgkqhkiG9w0BAQsFADBiMQswCQYDVQQGEwJVUzEL 502 MAkGA1UECBMCQ0ExFDASBgNVBAcTC0xvcyBBbmdlbGVzMRMwEQYDVQQKEwpJQ0FO 503 TiBUTUNIMRswGQYDVQQDExJJQ0FOTiBUTUNIIFRFU1QgQ0EwHhcNMTMwMjA4MDAw 504 MDAwWhcNMTgwMjA3MjM1OTU5WjBsMQswCQYDVQQGEwJVUzELMAkGA1UECBMCQ0Ex 505 FDASBgNVBAcTC0xvcyBBbmdlbGVzMRcwFQYDVQQKEw5WYWxpZGF0b3IgVE1DSDEh 506 MB8GA1UEAxMYVmFsaWRhdG9yIFRNQ0ggVEVTVCBDRVJUMIIBIjANBgkqhkiG9w0B 507 AQEFAAOCAQ8AMIIBCgKCAQEAo/cwvXhbVYl0RDWWvoyeZpETVZVVcMCovUVNg/sw 508 WinuMgEWgVQFrz0xA04pEhXCFVv4evbUpekJ5buqU1gmQyOsCKQlhOHTdPjvkC5u 509 pDqa51Flk0TMaMkIQjs7aUKCmA4RG4tTTGK/EjR1ix8/D0gHYVRldy1YPrMP+ou7 510 5bOVnIos+HifrAtrIv4qEqwLL4FTZAUpaCa2BmgXfy2CSRQbxD5Or1gcSa3vurh5 511 sPMCNxqaXmIXmQipS+DuEBqMM8tldaN7RYojUEKrGVsNk5i9y2/7sjn1zyyUPf7v 512 L4GgDYqhJYWV61DnXgx/Jd6CWxvsnDF6scscQzUTEl+hywIDAQABo4H/MIH8MAwG 513 A1UdEwEB/wQCMAAwHQYDVR0OBBYEFPZEcIQcD/Bj2IFz/LERuo2ADJviMIGMBgNV 514 HSMEgYQwgYGAFO0/7kEh3FuEKS+Q/kYHaD/W6wihoWakZDBiMQswCQYDVQQGEwJV 515 UzELMAkGA1UECBMCQ0ExFDASBgNVBAcTC0xvcyBBbmdlbGVzMRMwEQYDVQQKEwpJ 516 Q0FOTiBUTUNIMRswGQYDVQQDExJJQ0FOTiBUTUNIIFRFU1QgQ0GCAQEwDgYDVR0P 517 AQH/BAQDAgeAMC4GA1UdHwQnMCUwI6AhoB+GHWh0dHA6Ly9jcmwuaWNhbm4ub3Jn 518 L3RtY2guY3JsMA0GCSqGSIb3DQEBCwUAA4IBAQB2qSy7ui+43cebKUKwWPrzz9y/ 519 IkrMeJGKjo40n+9uekaw3DJ5EqiOf/qZ4pjBD++oR6BJCb6NQuQKwnoAz5lE4Ssu 520 y5+i93oT3HfyVc4gNMIoHm1PS19l7DBKrbwbzAea/0jKWVzrvmV7TBfjxD3AQo1R 521 bU5dBr6IjbdLFlnO5x0G0mrG7x5OUPuurihyiURpFDpwH8KAH1wMcCpXGXFRtGKk 522 wydgyVYAty7otkl/z3bZkCVT34gPvF70sR6+QxUy8u0LzF5A/beYaZpxSYG31amL 523 AdXitTWFipaIGea9lEGFM0L9+Bg7XzNn4nVLXokyEB3bgS4scG6QznX23FGk 524 525 526 527 528 530 NOTE: The example shown above includes white-spaces for indentation 531 purposes. It is RECOMMENDED that SMDs do not include white-spaces 532 between the XML elements, in order to mitigate risks of invalidating 533 the digital signature when transferring of SMDs between applications 534 takes place. 536 NOTE: Exclusive XML canonicalization SHOULD be used when generating 537 the SMD. SHA256/RSA-SHA256 SHOULD be used for digesting and signing. 538 The size of the RSA key SHOULD be at least 2048 bits. 540 2.4. Encoded Signed Mark 542 The element contains an encoded form of the 543 digitally signed element, described in Section 2.3, 544 with the encoding defined by the "encoding" attribute with the 545 default "encoding" value of "base64". The "base64" encoded text of 546 the element MUST conform to [RFC2045]. A 547 full example of a element is presented in 548 Appendix A. 550 2.5. Appendix A. base64 encoded signedMark 552 The following is an example of a element that 553 uses the default "base64" for encoding a element. 555 557 PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPHNtZDpzaWduZWRNYXJ 558 rIHhtbG5zOnNtZD0idXJuOmlldGY6cGFyYW1zOnhtbDpuczpzaWduZWRNYXJrLTEuMCIgaW 559 Q9Il84Yzk0ZjRmMS1jZTlmLTRjOTAtOTUzMS01MzE1ZDIzY2EzYmQiPgogIDxzbWQ6aWQ+M 560 DAwMDAwMTc1MTM3NjA1NjUwMzkzMS02NTUzNTwvc21kOmlkPgogIDxzbWQ6aXNzdWVySW5m 561 byBpc3N1ZXJJRD0iNjU1MzUiPgogICAgPHNtZDpvcmc+SUNBTk4gVE1DSCBURVNUSU5HIFR 562 NVjwvc21kOm9yZz4KICAgIDxzbWQ6ZW1haWw+bm90YXZhaWxhYmxlQGV4YW1wbGUuY29tPC 563 9zbWQ6ZW1haWw+CiAgICA8c21kOnVybD5odHRwOi8vd3d3LmV4YW1wbGUuY29tPC9zbWQ6d 564 XJsPgogICAgPHNtZDp2b2ljZT4rMzIuMDAwMDAwPC9zbWQ6dm9pY2U+CiAgPC9zbWQ6aXNz 565 dWVySW5mbz4KICA8c21kOm5vdEJlZm9yZT4yMDEzLTA4LTA5VDEzOjU1OjAzLjkzMVo8L3N 566 tZDpub3RCZWZvcmU+CiAgPHNtZDpub3RBZnRlcj4yMDE3LTA3LTIzVDIyOjAwOjAwLjAwMF 567 o8L3NtZDpub3RBZnRlcj4KICA8bWFyazptYXJrIHhtbG5zOm1hcms9InVybjppZXRmOnBhc 568 mFtczp4bWw6bnM6bWFyay0xLjAiPgogICAgPG1hcms6dHJhZGVtYXJrPgogICAgICA8bWFy 569 azppZD4wMDA1MjAxMzczNDY4OTczMTM3MzQ2ODk3My02NTUzNTwvbWFyazppZD4KICAgICA 570 gPG1hcms6bWFya05hbWU+VGVzdCAmYW1wOyBWYWxpZGF0ZTwvbWFyazptYXJrTmFtZT4KIC 571 AgICAgPG1hcms6aG9sZGVyIGVudGl0bGVtZW50PSJvd25lciI+CiAgICAgICAgPG1hcms6b 572 3JnPkFnIGNvcnBvcmF0aW9uPC9tYXJrOm9yZz4KICAgICAgICA8bWFyazphZGRyPgogICAg 573 ICAgICAgPG1hcms6c3RyZWV0PjEzMDUgQnJpZ2h0IEF2ZW51ZTwvbWFyazpzdHJlZXQ+CiA 574 gICAgICAgICA8bWFyazpjaXR5PkFyY2FkaWE8L21hcms6Y2l0eT4KICAgICAgICAgIDxtYX 575 JrOnNwPkNBPC9tYXJrOnNwPgogICAgICAgICAgPG1hcms6cGM+OTAwMjg8L21hcms6cGM+C 576 iAgICAgICAgICA8bWFyazpjYz5VUzwvbWFyazpjYz4KICAgICAgICA8L21hcms6YWRkcj4K 577 ICAgICAgPC9tYXJrOmhvbGRlcj4KICAgICAgPG1hcms6Y29udGFjdCB0eXBlPSJhZ2VudCI 578 +CiAgICAgICAgPG1hcms6bmFtZT5Ub255IEhvbGxhbmQ8L21hcms6bmFtZT4KICAgICAgIC 579 A8bWFyazpvcmc+QWcgY29ycG9yYXRpb248L21hcms6b3JnPgogICAgICAgIDxtYXJrOmFkZ 580 HI+CiAgICAgICAgICA8bWFyazpzdHJlZXQ+MTMwNSBCcmlnaHQgQXZlbnVlPC9tYXJrOnN0 581 cmVldD4KICAgICAgICAgIDxtYXJrOmNpdHk+QXJjYWRpYTwvbWFyazpjaXR5PgogICAgICA 582 gICAgPG1hcms6c3A+Q0E8L21hcms6c3A+CiAgICAgICAgICA8bWFyazpwYz45MDAyODwvbW 583 FyazpwYz4KICAgICAgICAgIDxtYXJrOmNjPlVTPC9tYXJrOmNjPgogICAgICAgIDwvbWFya 584 zphZGRyPgogICAgICAgIDxtYXJrOnZvaWNlPisxLjIwMjU1NjIzMDI8L21hcms6dm9pY2U+ 585 CiAgICAgICAgPG1hcms6ZmF4PisxLjIwMjU1NjIzMDE8L21hcms6ZmF4PgogICAgICAgIDx 586 tYXJrOmVtYWlsPmluZm9AYWdjb3Jwb3JhdGlvbi5jb208L21hcms6ZW1haWw+CiAgICAgID 587 wvbWFyazpjb250YWN0PgogICAgICA8bWFyazpqdXJpc2RpY3Rpb24+VVM8L21hcms6anVya 588 XNkaWN0aW9uPgogICAgICA8bWFyazpjbGFzcz4xNTwvbWFyazpjbGFzcz4KICAgICAgPG1h 589 cms6bGFiZWw+dGVzdGFuZHZhbGlkYXRlPC9tYXJrOmxhYmVsPgogICAgICA8bWFyazpsYWJ 590 lbD50ZXN0LS0tdmFsaWRhdGU8L21hcms6bGFiZWw+CiAgICAgIDxtYXJrOmxhYmVsPnRlc3 591 RhbmQtdmFsaWRhdGU8L21hcms6bGFiZWw+CiAgICAgIDxtYXJrOmxhYmVsPnRlc3QtZXQtd 592 mFsaWRhdGU8L21hcms6bGFiZWw+CiAgICAgIDxtYXJrOmxhYmVsPnRlc3QtdmFsaWRhdGU8 593 L21hcms6bGFiZWw+CiAgICAgIDxtYXJrOmxhYmVsPnRlc3QtLXZhbGlkYXRlPC9tYXJrOmx 594 hYmVsPgogICAgICA8bWFyazpsYWJlbD50ZXN0LWV0dmFsaWRhdGU8L21hcms6bGFiZWw+Ci 595 AgICAgIDxtYXJrOmxhYmVsPnRlc3RldHZhbGlkYXRlPC9tYXJrOmxhYmVsPgogICAgICA8b 596 WFyazpsYWJlbD50ZXN0dmFsaWRhdGU8L21hcms6bGFiZWw+CiAgICAgIDxtYXJrOmxhYmVs 597 PnRlc3RldC12YWxpZGF0ZTwvbWFyazpsYWJlbD4KICAgICAgPG1hcms6Z29vZHNBbmRTZXJ 598 2aWNlcz5ndWl0YXI8L21hcms6Z29vZHNBbmRTZXJ2aWNlcz4KICAgICAgPG1hcms6cmVnTn 599 VtPjEyMzQ8L21hcms6cmVnTnVtPgogICAgICA8bWFyazpyZWdEYXRlPjIwMTItMTItMzFUM 600 jM6MDA6MDAuMDAwWjwvbWFyazpyZWdEYXRlPgogICAgPC9tYXJrOnRyYWRlbWFyaz4KICA8 601 L21hcms6bWFyaz4KPGRzOlNpZ25hdHVyZSB4bWxuczpkcz0iaHR0cDovL3d3dy53My5vcmc 602 vMjAwMC8wOS94bWxkc2lnIyIgSWQ9Il81ODg5YzM5Zi1jMzM3LTQ0NzctOTU1Ni05NTNiZT 603 A5Y2NkMTgiPjxkczpTaWduZWRJbmZvPjxkczpDYW5vbmljYWxpemF0aW9uTWV0aG9kIEFsZ 604 29yaXRobT0iaHR0cDovL3d3dy53My5vcmcvMjAwMS8xMC94bWwtZXhjLWMxNG4jIi8+PGRz 605 OlNpZ25hdHVyZU1ldGhvZCBBbGdvcml0aG09Imh0dHA6Ly93d3cudzMub3JnLzIwMDEvMDQ 606 veG1sZHNpZy1tb3JlI3JzYS1zaGEyNTYiLz48ZHM6UmVmZXJlbmNlIFVSST0iI184Yzk0Zj 607 RmMS1jZTlmLTRjOTAtOTUzMS01MzE1ZDIzY2EzYmQiPjxkczpUcmFuc2Zvcm1zPjxkczpUc 608 mFuc2Zvcm0gQWxnb3JpdGhtPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwLzA5L3htbGRzaWcj 609 ZW52ZWxvcGVkLXNpZ25hdHVyZSIvPjxkczpUcmFuc2Zvcm0gQWxnb3JpdGhtPSJodHRwOi8 610 vd3d3LnczLm9yZy8yMDAxLzEwL3htbC1leGMtYzE0biMiLz48L2RzOlRyYW5zZm9ybXM+PG 611 RzOkRpZ2VzdE1ldGhvZCBBbGdvcml0aG09Imh0dHA6Ly93d3cudzMub3JnLzIwMDEvMDQve 612 G1sZW5jI3NoYTI1NiIvPjxkczpEaWdlc3RWYWx1ZT5IdUdKYlZCWkVaVGlFelB2d0NObVFs 613 NmFMZEExWHo1QzAzdnhDWFBIZW1BPTwvZHM6RGlnZXN0VmFsdWU+PC9kczpSZWZlcmVuY2U 614 +PGRzOlJlZmVyZW5jZSBVUkk9IiNfMWRlNTg5OGMtNmY3Ny00ZDViLTlkZDgtMzE4MWM5MT 615 E3Yzk3Ij48ZHM6VHJhbnNmb3Jtcz48ZHM6VHJhbnNmb3JtIEFsZ29yaXRobT0iaHR0cDovL 616 3d3dy53My5vcmcvMjAwMS8xMC94bWwtZXhjLWMxNG4jIi8+PC9kczpUcmFuc2Zvcm1zPjxk 617 czpEaWdlc3RNZXRob2QgQWxnb3JpdGhtPSJodHRwOi8vd3d3LnczLm9yZy8yMDAxLzA0L3h 618 tbGVuYyNzaGEyNTYiLz48ZHM6RGlnZXN0VmFsdWU+NHBiU0M2M2xObVBxelc3TDBNRDBxZ0 619 5GNHc5SUE3YXQ3OWxEVE5VZjBndz08L2RzOkRpZ2VzdFZhbHVlPjwvZHM6UmVmZXJlbmNlP 620 jwvZHM6U2lnbmVkSW5mbz48ZHM6U2lnbmF0dXJlVmFsdWUgSWQ9Il9hODAwZmIwNS02NjRh 621 LTQ2OTItYjM5MS04OTM4NTlhNTM0OGQiPlc5VHAxQ09HeEk4dlZQNkZONEdpYlhtc3RRM1Z 622 0bmpSZVN3VVdicFZCTEtmenZ1L1c1OGNoOUdxdnRQTm9HZTdXOXVvQUt0U1J0MUkKMzdPeD 623 IwQmVQb2xGdWZmekVVR3NGMHBETkRoWmNiRUdEMlVWRTBpYnhIRkVDUU13d0ppK1NVb2ora 624 3JIWmRXM0FybmNaZ0RkMkhXZgpudVJZSmVucnpCS2k2RG1YVlVRYlhXRFVkbGxzcjlDSmtB 625 THYrd0s2V2RweE9Na0NTc2E0WUU2bEVNTjVXNGhzUXFlZ2N6ZGkwdUZ0CnZxQ2JLVnM3RTJ 626 3c0VIZC94aUxzbldZNEUxNWdLNnI0UW9tWHJqdFI0ZkFyZ1lMTnRLK09NRCt6UktNeGNuNV 627 F2QzJVeHlzNUV6RHcKNmhlenYrdXBxTldkRjRYL2lCNW1JY25DMzAraVBpY3lDb2JHUlE9P 628 TwvZHM6U2lnbmF0dXJlVmFsdWU+PGRzOktleUluZm8gSWQ9Il8xZGU1ODk4Yy02Zjc3LTRk 629 NWItOWRkOC0zMTgxYzkxMTdjOTciPjxkczpYNTA5RGF0YT48ZHM6WDUwOUNlcnRpZmljYXR 630 lPk1JSUZMekNDQkJlZ0F3SUJBZ0lnTHJBYmV2b2FlNTJ5M2Y2QzJ0QjBTbjNwN1hKbTBUMD 631 JGb2d4S0NmTmhYb3dEUVlKS29aSWh2Y04KQVFFTEJRQXdmREVMTUFrR0ExVUVCaE1DVlZNe 632 FBEQTZCZ05WQkFvVE0wbHVkR1Z5Ym1WMElFTnZjbkJ2Y21GMGFXOXVJR1p2Y2lCQgpjM05w 633 WjI1bFpDQk9ZVzFsY3lCaGJtUWdUblZ0WW1WeWN6RXZNQzBHQTFVRUF4TW1TVU5CVGs0Z1Z 634 ISmhaR1Z0WVhKcklFTnNaV0Z5CmFXNW5hRzkxYzJVZ1VHbHNiM1FnUTBFd0hoY05NVE13Tm 635 pJMk1EQXdNREF3V2hjTk1UZ3dOakkxTWpNMU9UVTVXakNCanpFTE1Ba0cKQTFVRUJoTUNRa 636 1V4SURBZUJnTlZCQWdURjBKeWRYTnpaV3h6TFVOaGNHbDBZV3dnVW1WbmFXOXVNUkV3RHdZ 637 RFZRUUhFd2hDY25WegpjMlZzY3pFUk1BOEdBMVVFQ2hNSVJHVnNiMmwwZEdVeE9EQTJCZ05 638 WQkFNVEwwbERRVTVPSUZSTlEwZ2dRWFYwYUc5eWFYcGxaQ0JVCmNtRmtaVzFoY21zZ1VHbH 639 NiM1FnVm1Gc2FXUmhkRzl5TUlJQklqQU5CZ2txaGtpRzl3MEJBUUVGQUFPQ0FROEFNSUlCQ 640 2dLQ0FRRUEKeGxwM0twWUhYM1d5QXNGaFNrM0x3V2ZuR2x4blVERnFGWkEzVW91TVlqL1hp 641 Z2JNa05lRVhJamxrUk9LVDRPUEdmUngvTEF5UmxRUQpqQ012NHFoYmtjWDFwN2FyNjNmbHE 642 0U1pOVmNsMTVsN2gwdVQ1OEZ6U2ZubHowdTVya0hmSkltRDQzK21hUC84Z3YzNkZSMjdqVz 643 hSCjl3WTRoaytXczRJQjBpRlNkOFNYdjFLcjh3L0ptTVFTRGtpdUcrUmZJaXVid1EvZnk3R 644 WtqNVFXaFBadyttTXhOS25IVUx5M3hZejIKTHdWZmZ0andVdWVhY3ZxTlJDa01YbENsT0FE 645 cWZUOG9TWm9lRFhlaEh2bFBzTENlbUdCb1RLdXJza0lTNjlGMHlQRUg1Z3plMEgrZgo4RlJ 646 Pc0lvS1NzVlEzNEI0Uy9qb0U2N25wc0pQVGRLc05QSlR5UUlEQVFBQm80SUJoekNDQVlNd0 647 RBWURWUjBUQVFIL0JBSXdBREFkCkJnTlZIUTRFRmdRVW9GcFk3NnA1eW9ORFJHdFFwelZ1U 648 jgxVVdRMHdnY1lHQTFVZEl3U0J2akNCdTRBVXc2MCtwdFlSQUVXQVhEcFgKU29wdDNERU5u 649 bkdoZ1lDa2ZqQjhNUXN3Q1FZRFZRUUdFd0pWVXpFOE1Eb0dBMVVFQ2hNelNXNTBaWEp1Wlh 650 RZ1EyOXljRzl5WVhScApiMjRnWm05eUlFRnpjMmxuYm1Wa0lFNWhiV1Z6SUdGdVpDQk9kVz 651 FpWlhKek1TOHdMUVlEVlFRREV5WkpRMEZPVGlCVWNtRmtaVzFoCmNtc2dRMnhsWVhKcGJtZ 652 G9iM1Z6WlNCUWFXeHZkQ0JEUVlJZ0xyQWJldm9hZTUyeTNmNkMydEIwU24zcDdYSm0wVDAy 653 Rm9neEtDZk4KaFhrd0RnWURWUjBQQVFIL0JBUURBZ2VBTURRR0ExVWRId1F0TUNzd0thQW5 654 vQ1dHSTJoMGRIQTZMeTlqY213dWFXTmhibTR1YjNKbgpMM1J0WTJoZmNHbHNiM1F1WTNKc0 655 1FVUdBMVVkSUFRK01Ed3dPZ1lES2dNRU1ETXdNUVlJS3dZQkJRVUhBZ0VXSldoMGRIQTZMe 656 TkzCmQzY3VhV05oYm00dWIzSm5MM0JwYkc5MFgzSmxjRzl6YVhSdmNua3dEUVlKS29aSWh2 657 Y05BUUVMQlFBRGdnRUJBSWVEWVlKcjYwVzMKeTlRcyszelJWSTlrZWtLb201dmtIT2FsQjN 658 3SGFaSWFBRllwSTk4dFkwYVZOOWFHT04wdjZXUUYrbnZ6MUtSWlFiQXowMUJYdGFSSgo0bV 659 BrYXJoaHVMbjlOa0J4cDhIUjVxY2MrS0g3Z3Y2ci9jMGlHM2JDTkorUVNyN1FmKzVNbE1vN 660 npMNVVkZFUvVDJqaWJNWENqL2YyCjFRdzN4OVFnb3lYTEZKOW96YUxnUTlSTWtMbE9temtD 661 QWlYTjVBYjQzYUo5ZjdOMmdFMk5uUmpOS21tQzlBQlEwVFJ3RUtWTGhWbDEKVUdxQ0hKM0F 662 sQlhXSVhONXNqUFFjRC8rbkhlRVhNeFl2bEF5cXhYb0QzTVd0UVZqN2oyb3FsYWtPQk1nRz 663 grcTJxWWxtQnRzNEZOaQp3NzQ4SWw1ODZIS0JScXhIdFpkUktXMlZxYVE9PC9kczpYNTA5Q 664 2VydGlmaWNhdGU+PC9kczpYNTA5RGF0YT48L2RzOktleUluZm8+PC9kczpTaWduYXR1cmU+ 665 PC9zbWQ6c2lnbmVkTWFyaz4= 666 668 3. Formal Syntax 670 Two schemas are presented here. The first schema is the schema for 671 the Signed Mark. The second schema is the schema for the Mark. 673 The formal syntax presented here is a complete schema representation 674 of the object mapping suitable for automated validation of EPP XML 675 instances. The BEGIN and END tags are not part of the schema; they 676 are used to note the beginning and ending of the schema for URI 677 registration purposes. 679 3.1. Signed Mark Schema 681 Copyright (c) 2012 IETF Trust and the persons identified as authors 682 of the code. All rights reserved. 684 Redistribution and use in source and binary forms, with or without 685 modification, are permitted provided that the following conditions 686 are met: 688 o Redistributions of source code must retain the above copyright 689 notice, this list of conditions and the following disclaimer. 691 o Redistributions in binary form must reproduce the above copyright 692 notice, this list of conditions and the following disclaimer in 693 the documentation and/or other materials provided with the 694 distribution. 696 o Neither the name of Internet Society, IETF or IETF Trust, nor the 697 names of specific contributors, may be used to endorse or promote 698 products derived from this software without specific prior written 699 permission. 701 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 702 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 703 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 704 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 705 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 706 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 707 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 708 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 709 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 710 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 711 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 713 BEGIN 714 715 723 724 725 Schema for representing a Signed Trademark. 726 727 729 731 734 737 740 743 745 748 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 766 767 768 769 770 771 772 773 774 776 777 778 779 780 781 782 783 784 END 786 3.2. Mark Schema 788 Copyright (c) 2012 IETF Trust and the persons identified as authors 789 of the code. All rights reserved. 791 Redistribution and use in source and binary forms, with or without 792 modification, are permitted provided that the following conditions 793 are met: 795 o Redistributions of source code must retain the above copyright 796 notice, this list of conditions and the following disclaimer. 798 o Redistributions in binary form must reproduce the above copyright 799 notice, this list of conditions and the following disclaimer in 800 the documentation and/or other materials provided with the 801 distribution. 803 o Neither the name of Internet Society, IETF or IETF Trust, nor the 804 names of specific contributors, may be used to endorse or promote 805 products derived from this software without specific prior written 806 permission. 808 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 809 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 810 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 811 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 812 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 813 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 814 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 815 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 816 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 817 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 818 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 820 BEGIN 821 822 828 829 830 Schema for representing a Trademark, also referred to 831 as Mark. 832 833 834 837 840 843 846 849 851 854 855 856 857 858 860 863 865 866 867 868 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 893 894 895 896 897 899 901 902 904 906 907 908 909 910 911 912 913 915 916 917 918 919 921 923 925 927 928 929 930 931 932 933 935 936 937 938 939 941 943 945 946 947 948 949 951 952 953 955 958 959 960 961 962 963 964 965 966 968 971 972 973 974 975 978 979 981 984 985 986 987 988 990 993 994 995 996 997 999 1002 1003 1004 1005 1006 1007 1008 1010 1013 1014 1015 1016 1017 1018 1020 1023 1024 1025 1027 1028 1030 1033 1034 1035 1036 1037 1038 1039 1041 1044 1045 1046 1047 1048 1050 1051 1052 1053 1054 1055 1056 1058 1059 1060 1061 1062 1063 1064 1065 1066 END 1068 4. Implementation Status 1070 Note to RFC Editor: Please remove this section and the reference to 1071 RFC 6982 [RFC6982] before publication. 1073 This section records the status of known implementations of the 1074 format defined by this specification at the time of posting of this 1075 Internet-Draft, and is based on a proposal described in RFC 6982 1076 [RFC6982]. The description of implementations in this section is 1077 intended to assist the IETF in its decision processes in progressing 1078 drafts to RFCs. Please note that the listing of any individual 1079 implementation here does not imply endorsement by the IETF. 1080 Furthermore, no effort has been spent to verify the information 1081 presented here that was supplied by IETF contributors. This is not 1082 intended as, and must not be construed to be, a catalog of available 1083 implementations or their features. Readers are advised to note that 1084 other implementations may exist. 1086 According to RFC 6982 [RFC6982], "this will allow reviewers and 1087 working groups to assign due consideration to documents that have the 1088 benefit of running code, which may serve as evidence of valuable 1089 experimentation and feedback that have made the implemented protocols 1090 more mature. It is up to the individual working groups to use this 1091 information as they see fit". 1093 4.1. Verisign EPP SDK 1095 Organization: Verisign Inc. 1097 Name: Verisign EPP SDK 1099 Description: The Verisign EPP SDK includes both a full client 1100 implementation and a full server stub implementation of 1101 draft-ietf-eppext-tmch-smd. 1103 Level of maturity: Production 1105 Coverage: All aspects of the draft-ietf-eppext-tmch-smd are 1106 implemented. 1108 Licensing: GNU Lesser General Public License 1110 Contact: jgould@verisign.com 1112 URL: http://www.verisigninc.com/en_US/channel-resources/ 1113 domain-registry-products/epp-sdks 1115 4.2. Verisign Consolidated Top Level Domain (CTLD) SRS 1117 Organization: Verisign Inc. 1119 Name: Verisign Consolidated Top Level Domain (CTLD) Shared Registry 1120 System (SRS) 1121 Description: The Verisign Consolidated Top Level Domain (CTLD) Shared 1122 Registry System (SRS) implements the server-side of 1123 draft-ietf-eppext-tmch-smd for a variety of Top Level Domains 1124 (TLD's). 1126 Level of maturity: Production 1128 Coverage: Implements parsing and validation of all aspects of 1129 draft-ietf-eppext-tmch-smd including the Signed Mark, the Encoded 1130 Signed Mark, and the contained Mark. Implements the encoding of the 1131 Mark in supporting the response of draft-ietf-eppext-launchphase. 1133 Licensing: Proprietary 1135 Contact: jgould@verisign.com 1137 4.3. Verisign .COM / .NET SRS 1139 Organization: Verisign Inc. 1141 Name: Verisign .COM / .NET Shared Registry System (SRS) 1143 Description: The Verisign Shared Registry System (SRS) for .COM, .NET 1144 and other IDN TLD's implements the server-side of 1145 draft-ietf-eppext-tmch-smd. 1147 Level of maturity: Operational Test Environment (OTE) 1149 Coverage: Implements parsing and validation of all aspects of 1150 draft-ietf-eppext-tmch-smd including the Signed Mark, the Encoded 1151 Signed Mark, and the contained Mark. 1153 Licensing: Proprietary 1155 Contact: jgould@verisign.com 1157 4.4. REngin v3.7 1159 Organisation: Domain Name Services (Pty) Ltd 1161 Name: REngin v3.7 1163 Description: Server side implementation only 1165 Level of maturity: Production 1167 Coverage: All aspects of draft-ietf-eppext-tmch-smd have been 1168 implemented 1169 Licensing: Proprietary Licensing with Maintenance Contracts 1171 Contact: info@dnservices.co.za 1173 URL: http://domain-name.services 1175 4.5. Uniregistry Corp. Shared Registry System (uSRS) 1177 Organization: Uniregistry Corp. 1179 Name: Uniregistry Corp. Shared Registry System (uSRS) 1181 Description: Uniregistry's Shared Registry System implements the 1182 server-side of draft-ietf-eppext-tmch-smd for its TLD registry. 1184 Level of maturity: Production 1186 Coverage: Implements parsing and validation of all aspects of 1187 draft-ietf-eppext-tmch-smd including the Signed Mark, the Encoded 1188 Signed Mark, and the contained Mark. Implements the encoding of the 1189 Mark in supporting the response of draft-ietf-eppext-launchphase. 1191 Licensing: Proprietary 1193 Contact: fobispo@uniregistry.link 1195 5. Acknowledgements 1197 Special thanks to Chris Wright for creating the first prototype of a 1198 SMD; James Gould, Wil Tan and Gavin Brown for creating the mark and 1199 SMD definitions in their EPP draft launch extension on which this 1200 draft is based. 1202 6. Change History 1204 Version draft-ietf-eppext-tmch-smd-00 to version 1205 draft-ietf-eppext-tmch-smd-01 1207 Implementation Status section added. 1209 Added type to the enconding element. 1211 Version draft-lozano-tmch-smd-03 to version 1212 draft-ietf-eppext-tmch-smd-00 1213 Internet-Draft resubmitted. 1215 Version 02 to version 03 1217 example is now aligned with ICANN test SMDs. 1219 example is replaced with a public ICANN 1220 test SMD. 1222 Several recommendations where added. 1224 Version 01 to version 02 1226 Change apID and regNum of trademark validated mark to token. 1228 Change refNum of treatyOrStatute validated mark to token. 1230 Change refNum of court validated mark to token. 1232 Version 00 to version 01 1234 Add missing email element to holderType. 1236 Change ruling from an attribute to an element. 1238 Version preview-01 to version 00 1240 signedMarkType now ref mark:abstractMark. 1242 Security section completed. 1244 Version preview-00 to preview-01 1246 Full example of an encodedSignedMark added. 1248 signedMark example now fully validates with XSD. 1250 Fixed labelType to allow two-character labels. 1252 Missing mark:protectionType added in the XSD. 1254 Issuer email is now required. 1256 7. IANA Considerations 1258 This document uses URNs to describe XML namespaces and XML schemas 1259 conforming to a registry mechanism described in [RFC3688]. Three URI 1260 assignments have been registered by the IANA. 1262 Registration request for the Signed mark namespace: 1264 URI: urn:ietf:params:xml:ns:signedMark-1.0 1266 Registrant Contact: See the "Author's Address" section of this 1267 document. 1269 XML: None. Namespace URIs do not represent an XML specification. 1271 Registration request for the Mark namespace: 1273 URI: urn:ietf:params:xml:ns:mark-1.0 1275 Registrant Contact: See the "Author's Address" section of this 1276 document. 1278 XML: None. Namespace URIs do not represent an XML specification. 1280 8. Security Considerations 1282 The object mapping described in this document does not provide any 1283 security services or introduce any additional considerations. 1285 9. Normative References 1287 [ISO3166-2] 1288 ISO, "International Standard for country codes and codes 1289 for their subdivisions", 2006. 1291 [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 1292 Extensions (MIME) Part One: Format of Internet Message 1293 Bodies", RFC 2045, November 1996. 1295 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1296 Requirement Levels", BCP 14, RFC 2119, March 1997. 1298 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1299 January 2004. 1301 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 1302 STD 69, RFC 5730, August 2009. 1304 [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 1305 Code: The Implementation Status Section", RFC 6982, 1306 July 2013. 1308 [WIPO.ST3] 1309 WIPO, "Recommended standard on two-letter codes for the 1310 representation of states, other entities and 1311 intergovernmental organizations", March 2007. 1313 [1] 1315 [2] 1317 Author's Address 1319 Gustavo Lozano 1320 ICANN 1321 12025 Waterfront Drive, Suite 300 1322 Los Angeles 90292 1323 US 1325 Phone: +1.3103015800 1326 Email: gustavo.lozano@icann.org