idnits 2.17.1 draft-ietf-eppext-tmch-smd-05.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 18, 2016) is 2983 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. 'ICANN-TMCH' -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO3166-2' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.E164.2005' ** Obsolete normative reference: RFC 4051 (Obsoleted by RFC 6931) -- Possible downref: Non-RFC (?) normative reference: ref. 'WIPO-NICE-CLASSES' -- Possible downref: Non-RFC (?) normative reference: ref. 'XMLC14N' -- Possible downref: Non-RFC (?) normative reference: ref. 'XMLDSIG' -- Obsolete informational reference (is this intentional?): RFC 6982 (Obsoleted by RFC 7942) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 8 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 18, 2016 5 Expires: August 21, 2016 7 Mark and Signed Mark Objects Mapping 8 draft-ietf-eppext-tmch-smd-05 10 Abstract 12 Domain Name Registries (DNRs) may operate in special modes for 13 certain periods of time enabling trademark holders to protect their 14 rights during the introduction of a Top Level Domain (TLD). 16 One of those special modes of operation is the Sunrise Period. The 17 Sunrise Period allows trademark holders an advance opportunity to 18 register domain names corresponding to their trademarks before names 19 are generally available to the public. 21 This document describes the format of a mark and a digitally signed 22 mark used by trademark holders for registering domain names during 23 the sunrise phase of generic Top Level Domains (gTLDs). Three types 24 of mark objects are defined in this specification: registered 25 trademarks, court-validated marks, and marks protected by statue or 26 treaty. 28 Status of This Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at http://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on August 21, 2016. 45 Copyright Notice 47 Copyright (c) 2016 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 63 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 64 2. Object Description . . . . . . . . . . . . . . . . . . . . . 4 65 2.1. Holder and Contacts objects . . . . . . . . . . . . . . . 4 66 2.2. Mark . . . . . . . . . . . . . . . . . . . . . . . . . . 6 67 2.3. Signed Mark . . . . . . . . . . . . . . . . . . . . . . . 9 68 2.4. Encoded Signed Mark . . . . . . . . . . . . . . . . . . . 13 69 3. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 13 70 3.1. Signed Mark Schema . . . . . . . . . . . . . . . . . . . 13 71 3.2. Mark Schema . . . . . . . . . . . . . . . . . . . . . . . 15 72 4. Implementation Status . . . . . . . . . . . . . . . . . . . . 21 73 4.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 21 74 4.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 22 75 4.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 22 76 4.4. REngin v3.7 . . . . . . . . . . . . . . . . . . . . . . . 22 77 4.5. Uniregistry Corp. Shared Registry System (uSRS) . . . . . 23 78 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 23 79 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23 80 7. Security Considerations . . . . . . . . . . . . . . . . . . . 24 81 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 82 8.1. Normative References . . . . . . . . . . . . . . . . . . 25 83 8.2. Informative References . . . . . . . . . . . . . . . . . 26 84 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 26 86 1. Introduction 88 Domain Name Registries (DNRs) may operate in special modes for 89 certain periods of time enabling trademark holders to protect their 90 rights during the introduction of a Top Level Domain (TLD). 92 One of those special modes of operation is the Sunrise Period. The 93 Sunrise Period allows trademark holders an advance opportunity to 94 register domain names corresponding to their trademarks before names 95 are generally available to the public. 97 This specification was defined as part of the development of the 98 ICANN Trademark Clearinghouse (TMCH). The ICANN TMCH is a global 99 repository for trademark data used by DNRs, registrars and trademark 100 holders during the registration process of domain names. 102 This document describes a mapping of the common elements found in 103 trademark data. A digitally signed mark format is defined in order 104 to support digital signatures on the mark. Finally a mapping for 105 encoding the signed mark document is defined. 107 Three types of mark objects are defined in this specification: 108 registered trademarks, court-validated marks, and marks protected by 109 statue or treaty. 111 This specification is intended to be used in the gTLD space, but 112 nothing precludes the use of this format by other entities. 114 The detailed requirements regarding the public key infrastructure, 115 authorized validators, and other architectural details must be 116 defined based on the local policy of the entities using this 117 specification. In the case of gTLDs, the detailed architectural 118 requirements regarding the use of this specification are defined in 119 the Rights Protection Mechanism Requirements document ([ICANN-TMCH]). 121 The objects specified in this document can be referenced by 122 application protocols like the Extensible Provisioning Protocol 123 (EPP), defined in [RFC5730]. 125 1.1. Terminology 127 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 128 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 129 document are to be interpreted as described in RFC 2119 [RFC2119]. 131 XML (EXtensible Markup Language) is case sensitive. Unless stated 132 otherwise, XML specifications and examples provided in this document 133 MUST be interpreted in the character case presented in order to 134 develop a conforming implementation. 136 "signedMark-1.0" is used as an abbreviation for 137 "urn:ietf:params:xml:ns:signedMark-1.0". The XML namespace prefix 138 "smd" is used, but implementations MUST NOT depend on it and instead 139 employ a proper namespace-aware XML parser and serializer to 140 interpret and output the XML documents. 142 "mark-1.0" is used as an abbreviation for 143 "urn:ietf:params:xml:ns:mark-1.0". The XML namespace prefix "mark" 144 is used, but implementations MUST NOT depend on it and instead employ 145 a proper namespace-aware XML parser and serializer to interpret and 146 output the XML documents. 148 2. Object Description 150 This section defines the Mark and Signed Mark objects. Empty complex 151 element types and abstract elements are defined to support additional 152 Mark and Signed Mark definitions using XML schema substitution 153 groups. Support for replacement through the XML schema substitution 154 groups is included in the description of the objects. 156 This section defines some elements as OPTIONAL. If an elements is 157 not defined as OPTIONAL, then it MUST be included in the object. 159 The following elements are defined as telephone numbers: 160 , and . The representation of 161 telephone numbers in this specification is derived from structures 162 defined in [ITU.E164.2005]. Telephone numbers described in this 163 mapping are character strings that MUST begin with a plus sign ("+", 164 ASCII value 0x002B), followed by a country code defined in 165 [ITU.E164.2005], followed by a dot (".", ASCII value 0x002E), 166 followed by a sequence of digits representing the telephone number. 167 An optional "x" attribute is provided to note telephone extension 168 information. 170 The following elements are defined as email addresses: 171 and . Email address syntax is defined in [RFC5322]. 173 2.1. Holder and Contacts objects 175 Marks are linked to Holder objects and optionally linked to Contact 176 objects. This section defines the and 177 objects. 179 o The child elements of include: 181 * A element that contains the name of the individual 182 holder of the mark. At least one of and 183 MUST be specified, and is OPTIONAL if is 184 specified. 186 * A element that contains the name of the organization 187 holder of the mark. At least one of and 188 MUST be specified, and is OPTIONAL if is 189 specified. 191 * A element that contains the address information of 192 the holder of a mark. A contains the following 193 child elements: 195 + One, two or three OPTIONAL elements that 196 contains the holder's street address. 198 + A element that contains the holder's city. 200 + An OPTIONAL element that contains the holder's 201 state or province. 203 + An OPTIONAL element that contains the holder's 204 postal code. 206 + A element that contains the holder's country code. 207 This a two-character code from [ISO3166-2]. 209 * An OPTIONAL element that contains the holder's 210 voice telephone number. 212 * An OPTIONAL element that contains the holder's 213 facsimile telephone number. 215 * An OPTIONAL element that contains the email 216 address of the holder. 218 o The child elements of include: 220 * A element that contains name of the responsible 221 person. 223 * An OPTIONAL element that contains the name of the 224 organization of the contact. 226 * A element that contains the address information of 227 the contact. A contains the following child 228 elements: 230 + One, two or three OPTIONAL elements that 231 contains the contact's street address. 233 + A element that contains the contact's city. 235 + An OPTIONAL element that contains the contact's 236 state or province. 238 + An OPTIONAL element that contains the contact's 239 postal code. 241 + A element that contains the contact's country 242 code. This a two-character code from [ISO3166-2]. 244 * A element that contains the contact's voice 245 telephone number. 247 * An OPTIONAL element that contains the contact's 248 facsimile telephone number. 250 * A element that contains the contact's email 251 address. 253 2.2. Mark 255 A element that describes an applicant's prior right to a 256 given domain name. 258 A element substitutes for the 259 abstract element to define a concrete definition of a mark. The 260 element can be replaced by other mark definitions 261 using the XML schema substitution groups feature. 263 The child elements of the element include: 265 One or more , and 266 elements that contains the detailed information of marks. 268 o A element that contains the following child 269 elements: 271 * A that uniquely identifies a mark in relation to a 272 repository of marks potentially maintained by more than one 273 issuer. A value is a concatenation of the local 274 identifier, followed by a hyphen ("-", ASCII value 0x002D), 275 followed by the issuer identifier. 277 * A element that contains the mark text string. 279 * One or more elements that contains the 280 information of the holder of the mark. An "entitlement" 281 attribute is used to identify the entitlement of the holder, 282 possible values are: owner, assignee and licensee. 284 * Zero or more OPTIONAL elements that contains the 285 information of the representative of the mark registration. A 286 "type" attribute is used to identify the type of contact, 287 possible values are: owner, agent or thirdparty. 289 * A element that contains the two-character 290 code of the jurisdiction where the trademark was registered. 291 This is a two-character code from [WIPO.ST3]. 293 * Zero or more OPTIONAL elements that contain the 294 WIPO Nice Classification class numbers of the mark as defined 295 in the WIPO Nice Classification [WIPO-NICE-CLASSES]. 297 * Zero or more OPTIONAL elements that contain the 298 A-label form (as defined in [RFC5890]) of the label that 299 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 * An OPTIONAL element that contains the trademark 306 application ID registered in the trademark office. 308 * An OPTIONAL element that contains the date the 309 trademark was applied for. 311 * A element that contains the trademark 312 registration number registered in the trademark office. 314 * A element that contains the date the trademark 315 was registered. 317 * An OPTIONAL element that contains the expiration 318 date of the trademark. 320 o A element that contains the following child 321 elements: 323 * A , see definition in the section 324 above. 326 * A , see definition in the 327 section above. 329 * One or more , see definition in the 330 section above. 332 * Zero or more OPTIONAL , see definition in the 333 section above. 335 * One or more elements that contain the 336 countries and region of the country where the mark is 337 protected. The element contains the 338 following child elements: 340 + A element that contains the two-character code of 341 the country in which the mark is protected. This is a two- 342 character code from [ISO3166-2]. 344 + An OPTIONAL element that contains the name of 345 a city, state, province or other geographic region of 346 in which the mark is protected. 348 + Zero or more OPTIONAL elements that contains 349 the two-character code of the national territory in which 350 the statute or treaty is applicable. This is a two- 351 character code from [ISO3166-2]. 353 + Zero or more OPTIONAL , see definition in the 354 section above. 356 * A , see definition in the 357 section above. 359 * A element that contains the serial number of the 360 mark. 362 * A element that contains the date of protection 363 of the mark. 365 * A element that contains the title of the treaty or 366 statute. 368 * A element that contains the execution date of 369 the treaty or statute. 371 o A element that contains the following child elements: 373 * A , see definition in the section 374 above. 376 * A , see definition in the 377 section above. 379 * One or more , see definition in the 380 section above. 382 * Zero or more OPTIONAL , see definition in the 383 section above. 385 * Zero or more OPTIONAL , see definition in the 386 section above. 388 * A , see definition in the 389 section above. 391 * A element that contains the reference number of 392 the court's opinion. 394 * A element that contains the date of protection 395 of the mark. 397 * A element that contains the two-character code of the 398 country where the court is located. This a two-character code 399 from [ISO3166-2]. 401 * Zero or more OPTIONAL elements that contains the 402 name of a city, state, province or other geographic region of 403 in which the mark is protected. In case 404 is specified a default-deny approach MUST be 405 assumed regarding the regions of a country. 407 * A element that contains the name of the court. 409 2.3. Signed Mark 411 The is a digitally signed XML document using XML 412 Signature [XMLDSIG]. The XML document (SMD) 413 includes a required "id" attribute of type XSD ID for use with an 414 IDREF URI from the Signature element. The SMD might be transmitted 415 as part of an already XML based protocol, therefore exclusive XML 416 canonicalization as defined in [XMLC14N] MUST be used. 418 A element substitutes for the 419 abstract element to define a concrete 420 definition of a signed mark. The element 421 can be replaced by other signed mark definitions using the XML schema 422 substitution groups feature. 424 The child elements of the element include: 426 o The that uniquely identifies an SMD in relation to a 427 repository of SMDs potentially maintained by more than one issuer. 428 The value is a concatenation of the local identifier, 429 followed by a hyphen ("-", ASCII value 0x002D), followed by the 430 issuer identifier. 432 o A element that contains the information of the 433 issuer of the mark registration. A "issuerID" attribute is used 434 to specify the issuer identifier. The child elements include: 436 * A element that contains the organization name of the 437 issuer. 439 * A element that contains the issuer customer support 440 email address. 442 * An OPTIONAL element that contains the HTTP or HTTPS 443 URL of the issuer's site. 445 * An OPTIONAL element that contains the issuer's 446 voice telephone number. 448 o A element that contains the creation date and time 449 of the SMD. 451 o A element that contains the expiration date and 452 time of the SMD. 454 o A element that contains the mark information as 455 defined in the Mark (Section 2.2) section. 457 The following is an example of an SMD: 459 460 462 0000001751376056503931-65535 463 464 ICANN TMCH TESTING TMV 465 notavailable@example.com 466 https://www.example.com 467 +32.000000 468 469 2013-08-09T13:55:03.931Z 470 2017-07-23T22:00:00.000Z 471 472 473 00052013734689731373468973-65535 474 Test & Validate 475 476 Ag corporation 477 478 1305 Bright Avenue 479 Arcadia 480 CA 481 90028 482 US 483 484 485 486 Tony Holland 487 Ag corporation 488 489 1305 Bright Avenue 490 Arcadia 491 CA 492 90028 493 US 494 495 +1.2025562302 496 +1.2025562301 497 info@agcorporation.com 498 499 US 500 15 501 testandvalidate 502 test---validate 503 testand-validate 504 test-et-validate 505 test-validate 506 test--validate 507 test-etvalidate 508 testetvalidate 509 testvalidate 510 testet-validate 511 guitar 512 1234 513 2012-12-31T23:00:00.000Z 514 515 516 517 518 520 522 523 524 526 527 529 wgyW3nZPoEfpptlhRILKnOQnbdtU6ArM7ShrAfHgDFg= 530 531 532 533 jMu4PfyQGiJBF0GWSEPFCJjmywCEqR2h4LD+ge6XQ+JnmKFFCuCZS/3SLKAx0L1w 534 QDFO2e0Y69k2G7/LGE37X3vOflobFM1oGwja8+GMVraoto5xAd4/AF7eHukgAymD 535 o9toxoa2h0yV4A4PmXzsU6S86XtCcUE+S/WM72nyn47zoUCzzPKHZBRyeWehVFQ+ 536 jYRMIAMzM57HHQA+6eaXefRvtPETgUO4aVIVSugc4OUAZZwbYcZrC6wOaQqqqAZi 537 30aPOBYbAvHMSmWSS+hFkbshomJfHxb97TD2grlYNrQIzqXk7WbHWy2SYdA+sI/Z 538 ipJsXNa6osTUw1CzA7jfwA== 539 540 541 542 543 MIIESTCCAzGgAwIBAgIBAjANBgkqhkiG9w0BAQsFADBiMQswCQYDVQQGEwJVUzEL 544 MAkGA1UECBMCQ0ExFDASBgNVBAcTC0xvcyBBbmdlbGVzMRMwEQYDVQQKEwpJQ0FO 545 TiBUTUNIMRswGQYDVQQDExJJQ0FOTiBUTUNIIFRFU1QgQ0EwHhcNMTMwMjA4MDAw 546 MDAwWhcNMTgwMjA3MjM1OTU5WjBsMQswCQYDVQQGEwJVUzELMAkGA1UECBMCQ0Ex 547 FDASBgNVBAcTC0xvcyBBbmdlbGVzMRcwFQYDVQQKEw5WYWxpZGF0b3IgVE1DSDEh 548 MB8GA1UEAxMYVmFsaWRhdG9yIFRNQ0ggVEVTVCBDRVJUMIIBIjANBgkqhkiG9w0B 549 AQEFAAOCAQ8AMIIBCgKCAQEAo/cwvXhbVYl0RDWWvoyeZpETVZVVcMCovUVNg/sw 550 WinuMgEWgVQFrz0xA04pEhXCFVv4evbUpekJ5buqU1gmQyOsCKQlhOHTdPjvkC5u 551 pDqa51Flk0TMaMkIQjs7aUKCmA4RG4tTTGK/EjR1ix8/D0gHYVRldy1YPrMP+ou7 552 5bOVnIos+HifrAtrIv4qEqwLL4FTZAUpaCa2BmgXfy2CSRQbxD5Or1gcSa3vurh5 553 sPMCNxqaXmIXmQipS+DuEBqMM8tldaN7RYojUEKrGVsNk5i9y2/7sjn1zyyUPf7v 554 L4GgDYqhJYWV61DnXgx/Jd6CWxvsnDF6scscQzUTEl+hywIDAQABo4H/MIH8MAwG 555 A1UdEwEB/wQCMAAwHQYDVR0OBBYEFPZEcIQcD/Bj2IFz/LERuo2ADJviMIGMBgNV 556 HSMEgYQwgYGAFO0/7kEh3FuEKS+Q/kYHaD/W6wihoWakZDBiMQswCQYDVQQGEwJV 557 UzELMAkGA1UECBMCQ0ExFDASBgNVBAcTC0xvcyBBbmdlbGVzMRMwEQYDVQQKEwpJ 558 Q0FOTiBUTUNIMRswGQYDVQQDExJJQ0FOTiBUTUNIIFRFU1QgQ0GCAQEwDgYDVR0P 559 AQH/BAQDAgeAMC4GA1UdHwQnMCUwI6AhoB+GHWh0dHA6Ly9jcmwuaWNhbm4ub3Jn 560 L3RtY2guY3JsMA0GCSqGSIb3DQEBCwUAA4IBAQB2qSy7ui+43cebKUKwWPrzz9y/ 561 IkrMeJGKjo40n+9uekaw3DJ5EqiOf/qZ4pjBD++oR6BJCb6NQuQKwnoAz5lE4Ssu 562 y5+i93oT3HfyVc4gNMIoHm1PS19l7DBKrbwbzAea/0jKWVzrvmV7TBfjxD3AQo1R 563 bU5dBr6IjbdLFlnO5x0G0mrG7x5OUPuurihyiURpFDpwH8KAH1wMcCpXGXFRtGKk 564 wydgyVYAty7otkl/z3bZkCVT34gPvF70sR6+QxUy8u0LzF5A/beYaZpxSYG31amL 565 AdXitTWFipaIGea9lEGFM0L9+Bg7XzNn4nVLXokyEB3bgS4scG6QznX23FGk 566 567 568 569 571 573 NOTE: The example shown above includes white-spaces for indentation 574 purposes. It is RECOMMENDED that SMDs do not include white-spaces 575 between the XML elements, in order to mitigate risks of invalidating 576 the digital signature when transferring of SMDs between applications 577 takes place. 579 2.4. Encoded Signed Mark 581 The element contains an encoded form of an 582 SMD (described in Section 2.3), with the encoding defined by the 583 "encoding" attribute with the default "encoding" value of "base64" 584 [RFC4648]. 586 The following is an example of a element that 587 uses the default "base64" for encoding a element. 589 591 PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPHNtZDpzaWduZWRNYXJ 592 rIHhtbG5zOnNtZD0idXJuOmlldGY6cGFyYW1zOnhtbDpuczpzaWduZWRNYXJrLTEuMCIgaW 593 ... (base64 data elided for brevity) ... 594 PC9zbWQ6c2lnbmVkTWFyaz4= 595 597 3. Formal Syntax 599 Two schemas are presented here. The first schema is the schema for 600 the signed mark. The second schema is the schema for the mark. 602 The formal syntax presented here is a complete schema representation 603 of the object mapping suitable for automated validation of EPP XML 604 instances. The BEGIN and END tags are not part of the schema; they 605 are used to note the beginning and ending of the schema for URI 606 registration purposes. 608 3.1. Signed Mark Schema 610 Copyright (c) 2016 IETF Trust and the persons identified as authors 611 of the code. All rights reserved. 613 Redistribution and use in source and binary forms, with or without 614 modification, is permitted pursuant to, and subject to the license 615 terms contained in, the Simplified BSD License set forth in 616 Section 4.c of the IETF Trust's Legal Provisions Relating to IETF 617 Documents (http://trustee.ietf.org/license-info). 619 BEGIN 620 621 629 630 631 Schema for representing a Signed Trademark. 632 633 635 636 638 641 644 647 649 652 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 670 671 672 673 674 675 676 677 678 680 681 682 683 684 685 686 687 688 END 690 3.2. Mark Schema 692 Copyright (c) 2016 IETF Trust and the persons identified as authors 693 of the code. All rights reserved. 695 Redistribution and use in source and binary forms, with or without 696 modification, is permitted pursuant to, and subject to the license 697 terms contained in, the Simplified BSD License set forth in 698 Section 4.c of the IETF Trust's Legal Provisions Relating to IETF 699 Documents (http://trustee.ietf.org/license-info). 701 BEGIN 702 703 709 710 711 Schema for representing a Trademark, also referred to 712 as Mark. 713 714 716 719 722 725 728 731 733 736 737 738 739 740 742 745 747 748 749 750 752 753 754 755 756 757 758 759 761 762 763 765 766 767 768 769 770 771 772 773 774 775 777 778 779 780 781 783 785 786 788 790 791 792 793 794 795 796 797 799 800 801 802 803 805 807 810 812 813 814 815 816 817 818 820 821 822 823 824 826 828 830 831 832 833 834 836 837 838 840 843 844 845 846 847 848 849 850 851 853 856 857 858 859 860 862 863 865 868 869 870 871 872 874 877 878 879 880 881 883 886 887 888 889 890 891 892 894 897 898 899 900 901 902 904 907 908 909 910 911 913 916 917 918 919 920 921 922 924 927 928 929 930 931 933 934 935 936 937 938 939 941 942 943 944 945 946 947 948 949 END 951 4. Implementation Status 953 Note to RFC Editor: Please remove this section and the reference to 954 RFC 6982 [RFC6982] before publication. 956 This section records the status of known implementations of the 957 format defined by this specification at the time of posting of this 958 Internet-Draft, and is based on a proposal described in RFC 6982 959 [RFC6982]. The description of implementations in this section is 960 intended to assist the IETF in its decision processes in progressing 961 drafts to RFCs. Please note that the listing of any individual 962 implementation here does not imply endorsement by the IETF. 963 Furthermore, no effort has been spent to verify the information 964 presented here that was supplied by IETF contributors. This is not 965 intended as, and must not be construed to be, a catalog of available 966 implementations or their features. Readers are advised to note that 967 other implementations may exist. 969 According to RFC 6982 [RFC6982], "this will allow reviewers and 970 working groups to assign due consideration to documents that have the 971 benefit of running code, which may serve as evidence of valuable 972 experimentation and feedback that have made the implemented protocols 973 more mature. It is up to the individual working groups to use this 974 information as they see fit". 976 4.1. Verisign EPP SDK 978 Organization: Verisign Inc. 980 Name: Verisign EPP SDK 982 Description: The Verisign EPP SDK includes both a full client 983 implementation and a full server stub implementation of draft-ietf- 984 eppext-tmch-smd. 986 Level of maturity: Production 988 Coverage: All aspects of the draft-ietf-eppext-tmch-smd are 989 implemented. 991 Licensing: GNU Lesser General Public License 993 Contact: jgould@verisign.com 995 URL: http://www.verisigninc.com/en_US/channel-resources/domain- 996 registry-products/epp-sdks 998 4.2. Verisign Consolidated Top Level Domain (CTLD) SRS 1000 Organization: Verisign Inc. 1002 Name: Verisign Consolidated Top Level Domain (CTLD) Shared Registry 1003 System (SRS) 1005 Description: The Verisign Consolidated Top Level Domain (CTLD) Shared 1006 Registry System (SRS) implements the server-side of draft-ietf- 1007 eppext-tmch-smd for a variety of Top Level Domains (TLD's). 1009 Level of maturity: Production 1011 Coverage: Implements parsing and validation of all aspects of draft- 1012 ietf-eppext-tmch-smd including the Signed Mark, the Encoded Signed 1013 Mark, and the contained Mark. Implements the encoding of the Mark in 1014 supporting the response of draft-ietf-eppext-launchphase. 1016 Licensing: Proprietary 1018 Contact: jgould@verisign.com 1020 4.3. Verisign .COM / .NET SRS 1022 Organization: Verisign Inc. 1024 Name: Verisign .COM / .NET Shared Registry System (SRS) 1026 Description: The Verisign Shared Registry System (SRS) for .COM, .NET 1027 and other IDN TLD's implements the server-side of draft-ietf-eppext- 1028 tmch-smd. 1030 Level of maturity: Operational Test Environment (OTE) 1032 Coverage: Implements parsing and validation of all aspects of draft- 1033 ietf-eppext-tmch-smd including the Signed Mark, the Encoded Signed 1034 Mark, and the contained Mark. 1036 Licensing: Proprietary 1038 Contact: jgould@verisign.com 1040 4.4. REngin v3.7 1042 Organisation: Domain Name Services (Pty) Ltd 1044 Name: REngin v3.7 1045 Description: Server side implementation only 1047 Level of maturity: Production 1049 Coverage: All aspects of draft-ietf-eppext-tmch-smd have been 1050 implemented 1052 Licensing: Proprietary Licensing with Maintenance Contracts 1054 Contact: info@dnservices.co.za 1056 URL: http://domain-name.services 1058 4.5. Uniregistry Corp. Shared Registry System (uSRS) 1060 Organization: Uniregistry Corp. 1062 Name: Uniregistry Corp. Shared Registry System (uSRS) 1064 Description: Uniregistry's Shared Registry System implements the 1065 server-side of draft-ietf-eppext-tmch-smd for its TLD registry. 1067 Level of maturity: Production 1069 Coverage: Implements parsing and validation of all aspects of draft- 1070 ietf-eppext-tmch-smd including the Signed Mark, the Encoded Signed 1071 Mark, and the contained Mark. Implements the encoding of the Mark in 1072 supporting the response of draft-ietf-eppext-launchphase. 1074 Licensing: Proprietary 1076 Contact: fobispo@uniregistry.link 1078 5. Acknowledgements 1080 Special thanks to Chris Wright for creating the first prototype of a 1081 SMD; James Gould, Wil Tan and Gavin Brown for creating the mark and 1082 SMD definitions in their EPP draft launch extension on which this 1083 draft is based. Portions of the security section were shamefully 1084 copied from RFC5105. The author would like to acknowledge the 1085 following individuals for their contributions to this document: Scott 1086 Hollenbeck and Jan Jansen. 1088 6. IANA Considerations 1090 This document uses URNs to describe XML namespaces and XML schemas 1091 conforming to a registry mechanism described in [RFC3688]. Two URI 1092 assignments have been registered by the IANA. 1094 Registration request for the signed mark namespace: 1096 URI: urn:ietf:params:xml:ns:signedMark-1.0 1098 Registrant Contact: IESG 1100 XML: None. Namespace URIs do not represent an XML specification. 1102 Registration request for the signed mark schema: 1104 URI: urn:ietf:params:xml:schema:signedMark-1.0 1106 Registrant Contact: IESG 1108 XML: See the "Formal Syntax" section of this document. 1110 Registration request for the mark namespace: 1112 URI: urn:ietf:params:xml:ns:mark-1.0 1114 Registrant Contact: IESG 1116 XML: None. Namespace URIs do not represent an XML specification. 1118 Registration request for the mark schema: 1120 URI: urn:ietf:params:xml:schema:mark-1.0 1122 Registrant Contact: IESG 1124 XML: See the "Formal Syntax" section of this document. 1126 7. Security Considerations 1128 The security of a Signed Mark object depends on the security of the 1129 underlying XML DSIG algorithms. As such, all the security 1130 considerations from [XMLDSIG] apply here as well. 1132 The digital signature algorithm used in Signed Mark objects SHOULD be 1133 RSA-SHA256 [RFC4051]. The size of the RSA key SHOULD be at least 1134 2048 bits. A valid reason for choosing something else would be if 1135 RSA-SHA256 would be deemed to not provide sufficient security. 1137 In the case of the ICANN Trademark Clearinghouse (TMCH), Signed Mark 1138 objects use the algorithms for digesting and signing recommended in 1139 this document. 1141 Signed Marks are used primarily for sunrise domain name registrations 1142 in gTLDs, but other third-parties might be using them. A party using 1143 Signed Marks should verify that the digital signature is valid based 1144 on local policy. In the case of gTLDs, the RPM Requirements document 1145 [ICANN-TMCH] defines such policy. 1147 8. References 1149 8.1. Normative References 1151 [ICANN-TMCH] 1152 ICANN, "ICANN Trademark Clearinghouse, Rights Protection 1153 Mechanism Requirements", 2013, 1154 . 1157 [ISO3166-2] 1158 ISO, "International Standard for country codes and codes 1159 for their subdivisions", 2006, 1160 . 1162 [ITU.E164.2005] 1163 International Telecommunication Union, "The international 1164 public telecommunication numbering plan", 2010, 1165 . 1167 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1168 Requirement Levels", BCP 14, RFC 2119, 1169 DOI 10.17487/RFC2119, March 1997, 1170 . 1172 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1173 DOI 10.17487/RFC3688, January 2004, 1174 . 1176 [RFC4051] Eastlake 3rd, D., "Additional XML Security Uniform 1177 Resource Identifiers (URIs)", RFC 4051, 1178 DOI 10.17487/RFC4051, April 2005, 1179 . 1181 [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data 1182 Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006, 1183 . 1185 [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, 1186 DOI 10.17487/RFC5322, October 2008, 1187 . 1189 [RFC5890] Klensin, J., "Internationalized Domain Names for 1190 Applications (IDNA): Definitions and Document Framework", 1191 RFC 5890, DOI 10.17487/RFC5890, August 2010, 1192 . 1194 [WIPO-NICE-CLASSES] 1195 WIPO, "WIPO Nice Classification", 2015, 1196 . 1198 [WIPO.ST3] 1199 WIPO, "Recommended standard on two-letter codes for the 1200 representation of states, other entities and 1201 intergovernmental organizations", March 2007, 1202 . 1204 [XMLC14N] W3C Recommendation, "Exclusive XML Canonicalization 1205 Version 1.0", 2002, 1206 . 1208 [XMLDSIG] W3C Recommendation, "XML Signature Syntax and Processing 1209 (Second Edition)", 2013, 1210 . 1212 8.2. Informative References 1214 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 1215 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 1216 . 1218 [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 1219 Code: The Implementation Status Section", RFC 6982, 1220 DOI 10.17487/RFC6982, July 2013, 1221 . 1223 Author's Address 1225 Gustavo Lozano 1226 ICANN 1227 12025 Waterfront Drive, Suite 300 1228 Los Angeles 90292 1229 US 1231 Phone: +1.3103015800 1232 Email: gustavo.lozano@icann.org