idnits 2.17.1 draft-ietf-enum-iris-ereg-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 14. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2391. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2368. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2375. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2381. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (September 9, 2005) is 6803 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. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '2' -- Possible downref: Non-RFC (?) normative reference: ref. '3' -- Possible downref: Non-RFC (?) normative reference: ref. '4' ** Obsolete normative reference: RFC 3513 (ref. '7') (Obsoleted by RFC 4291) -- Possible downref: Non-RFC (?) normative reference: ref. '11' -- Possible downref: Non-RFC (?) normative reference: ref. '13' -- Possible downref: Non-RFC (?) normative reference: ref. '14' ** Obsolete normative reference: RFC 3490 (ref. '15') (Obsoleted by RFC 5890, RFC 5891) ** Obsolete normative reference: RFC 3491 (ref. '16') (Obsoleted by RFC 5891) ** Obsolete normative reference: RFC 3761 (ref. '18') (Obsoleted by RFC 6116, RFC 6117) Summary: 7 errors (**), 0 flaws (~~), 2 warnings (==), 14 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Newton 3 Internet-Draft VeriSign, Inc. 4 Expires: March 13, 2006 September 9, 2005 6 An ENUM Registry Type for the Internet Registry Information Service 7 draft-ietf-enum-iris-ereg-02 9 Status of this Memo 11 By submitting this Internet-Draft, each author represents that any 12 applicable patent or other IPR claims of which he or she is aware 13 have been or will be disclosed, and any of which he or she becomes 14 aware will be disclosed, in accordance with Section 6 of BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on March 13, 2006. 34 Copyright Notice 36 Copyright (C) The Internet Society (2005). 38 Abstract 40 This document describes an IRIS registry schema for registered ENUM 41 information. The schema extends the necessary query and result 42 operations of IRIS to provide the functional information service 43 needs for syntaxes and results used by ENUM registries. 45 Table of Contents 47 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 48 2. Document Terminology . . . . . . . . . . . . . . . . . . . . . 4 49 3. Schema Description . . . . . . . . . . . . . . . . . . . . . . 5 50 3.1 Query Derivatives . . . . . . . . . . . . . . . . . . . . 5 51 3.1.1 Query . . . . . . . . . . . . . . . 5 52 3.1.2 Query . . . . . . . . . . . . . . 5 53 3.1.3 Query . . . . . . . . . . . . . . . . . 6 54 3.1.4 Query . . . . . . . . . . . . . . . 6 55 3.1.5 Contact Search Group . . . . . . . . . . . . . . . . . 6 56 3.2 Result Derivatives . . . . . . . . . . . . . . . . . . . . 7 57 3.2.1 Privacy Labels . . . . . . . . . . . . . . . . . . . . 7 58 3.2.2 Contact Group . . . . . . . . . . . . . . . . . . . . 9 59 3.2.3 Result . . . . . . . . . . . . . . . . . . . . 9 60 3.2.4 Result . . . . . . . . . . . . . . . . . . . . 14 61 3.2.5 Result . . . . . . . . . . . . . . . . . . . 15 62 3.2.6 Result . . . . . . . . . . . . 17 63 3.2.7 Result . . . . . . . . . . . . . . 18 64 3.2.8 Result . . . . . . . . 19 65 3.2.9 Result . . . . . . . . . . . . . . . 20 66 3.3 Generic Code Derivatives . . . . . . . . . . . . . . . . . 21 67 3.3.1 . . . . . . . . . . . . . . . . . . . 21 68 3.3.2 . . . . . . . . . . . . . . . . 21 69 3.4 Support for . . . . . . . . . . . . . 21 70 4. Formal XML Syntax . . . . . . . . . . . . . . . . . . . . . . 23 71 5. BEEP Transport Compliance . . . . . . . . . . . . . . . . . . 49 72 5.1 Message Pattern . . . . . . . . . . . . . . . . . . . . . 49 73 5.2 Server Authentication . . . . . . . . . . . . . . . . . . 49 74 6. URI Resolution . . . . . . . . . . . . . . . . . . . . . . . . 50 75 6.1 Application Service Label . . . . . . . . . . . . . . . . 50 76 7. Internationalization Considerations . . . . . . . . . . . . . 51 77 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 52 78 8.1 XML Namespace URN Registration . . . . . . . . . . . . . . 52 79 8.2 S-NAPTR Registration . . . . . . . . . . . . . . . . . . . 52 80 8.3 BEEP Registration . . . . . . . . . . . . . . . . . . . . 52 81 9. Security Considerations . . . . . . . . . . . . . . . . . . . 54 82 10. Normative References . . . . . . . . . . . . . . . . . . . . 54 83 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 55 84 A. Contributions and Acknowledgements . . . . . . . . . . . . . . 56 85 Intellectual Property and Copyright Statements . . . . . . . . 57 87 1. Introduction 89 This document describes an IRIS registry schema for registries of 90 ENUM data using an XML Schema [4] derived from and using the IRIS [5] 91 schema. 93 The schema given is this document is specified using the Extensible 94 Markup Language (XML) 1.0 as described in XML [1], XML Schema 95 notation as described in XML_SD [3] and XML_SS [4], and XML 96 Namespaces as described in XML_NS [2]. 98 2. Document Terminology 100 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 101 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 102 document are to be interpreted as described in RFC2119 [10]. 104 This document uses the term "ENUM" as the fully qualified domain name 105 following the conventions of ENUM [18]. 107 3. Schema Description 109 IRIS requires the derivation of both query and result elements by a 110 registry schemas. These descriptions follow. 112 References to XML elements with no namespace qualifier are from the 113 schema defined in Section 4. References to elements and attributes 114 with the "iris" XML namespace qualifier are from the schema defined 115 in IRIS [5]. 117 The descriptions contained within this section refer to XML elements 118 and attributes and their relation to the exchange of data within the 119 protocol. These descriptions also contain specifications outside the 120 scope of the formal XML syntax. Therefore, this section will use 121 terms defined by RFC 2119 [10] to describe the specification outside 122 the scope of the formal XML syntax. While reading this section, 123 please reference Section 4 for needed details on the formal XML 124 syntax. 126 3.1 Query Derivatives 128 3.1.1 Query 130 finds ENUM domains by searching on prefixes of 131 E.164 numbers and returns (Section 3.2.3) results. 133 The E.164 prefix is specified using the child of 134 . An optional child element of , 135 , can narrow the search to ENUM domains associated with 136 E.164 numbers that are either more specific or less specific. If the 137 element is present and has the content 'less', then the 138 search is to be narrowed to E.164 numbers that are less specific 139 (i.e. have fewer digits). If the element is present 140 and has the content 'more', then the search is to be narrowed to 141 E.164 numbers that are more specific (i.e. have more digits). 143 3.1.2 Query 145 finds ENUM domains by searches on fields 146 associated with an ENUM domain's contact. 148 The allowable search fields are handled with either the 149 element or one of the elements in the 150 "contactSearchGroup" (see Section 3.1.5). The 151 element allows for the ENUM domains to be selected based on the 152 contact having the specified contact handle. 154 The query MAY also be constrained further using the optional 155 element. The contents of this element signify the role the contact 156 has with the ENUM domain. 158 This query also provides optional elements containing 159 language tags. Clients MAY use these elements to give a hint about 160 the natural language(s) of the affected element. Servers MAY use 161 this information in processing the query, such as tailoring 162 normalization routines to aid in more effective searches. 164 3.1.3 Query 166 searches for contacts given search constraints. 168 The allowable search fields are handled by one of the elements in the 169 "contactSearchGroup" (see Section 3.1.5). 171 This query also provides optional elements containing 172 language tags. Clients MAY use these elements to give a hint about 173 the natural language(s) of the affected element. Servers MAY use 174 this information in processing the query, such as tailoring 175 normalization routines to aid in more effective searches. 177 3.1.4 Query 179 This query does a simple search for the ENUM domainss being hosted by 180 a name server. The search is constrained using either the host name 181 [12], host handle, IPv4 address, or IPv6 address of the name server. 183 3.1.5 Contact Search Group 185 Some of the queries above have similar query constraints for 186 searching on contacts. This section describes those common 187 parameters. 189 allows the query to be constrained based on the common 190 name of the contact. The constraint can either constrain the query 191 by an exact match using the element, or it may constrain 192 the query by a subset of the common name using the and 193 elements. 195 allows the query to be constrained based on the 196 organization name of the contact. It has the same semantics as the 197 element. 199 constrains the query based on the e-mail address of the 200 contact. This may be done by an exact e-mail address using the 201 element or by any e-mail address in a domain using the 202 element. The MUST only contain a valid domain 203 name (i.e. no '@' symbol), and the matching SHOULD take place only on 204 the domain given (i.e. no partial matches with respect to substrings 205 or parent domains). If either the contents of the element 206 or domain part of the contents of the element contain a 207 name with non-ASCII characters, they MUST be normalized according to 208 the processes of RFC 3491 [16]. 210 The , , and elements restrict the scope of 211 the query based on the city, region, or postal code of the contact, 212 respectively. Each one must only contain an element 213 containing the exact city, region, or postal code (i.e. no substring 214 searches). 216 3.2 Result Derivatives 218 3.2.1 Privacy Labels 220 Several of the results in this registry type have values that cannot 221 be given but must be specified as present or must be flagged so that 222 clients do not divulge them. In order to achieve this, some of the 223 results use the following element types: 225 o "dateTimePrivacyType" - contains the XML Schema [3] data type 226 "dateTime". The contents of this element MUST be specified using 227 the 'Z' indicator for Coordinated Universal Time (UTC). 229 o "stringPrivacyType" - contains the XML Schema [3] data type 230 "string". 232 o "normalizedStringPrivacyType" - contains the XML Schema [3] data 233 type "normalizedString". 235 o "tokenPrivacyType" - contains the XML Schema [3] data type 236 "token". 238 o "enumStatusType" - describes a state for an ENUM domain. This 239 element has the following optional attributes: 241 * 'scope' - Indicates the scope or origin of the status value. 243 * 'disposition' - Contains either the value "pending", meaning 244 that initial processing for this status has begun and is not 245 yet complete, or the value "prohibited", meaning this ENUM 246 domain cannot achieve this status according to either the 247 registry or registrar of this ENUM domain. 249 * 'actor' - Contains either the value "registry", meaning this 250 status value has been associated with this ENUM domain by the 251 registry, or the value "registrar", meaning this status value 252 has been associated with this ENUM domain by the registrar. 254 This element has the following optional child elements: 256 * - Indicates the date and time the status was 257 applied. 259 * - Provides a textual description of the status. 260 This element has a required 'language' attribute. 262 * - Indicates a jurisdictional-dependent reason for 263 this status value. This element has a required 'authority' 264 attribute to indicate the jurisdicational authority associated 265 with this sub-status. 267 o "contactTypeType" - contains an optional child 268 elements. Each child element requires a 'language' 269 attribute. 271 As specified, they are nillable and therefore may be present with 272 empty content or present with their specified content. The use of 273 these elements is also optional. 275 If present without content, each of these element types MUST have one 276 or more of the following boolean attributes: 278 o 'private' - if true, this specifies that the content is absent 279 because it may never be published. 281 o 'denied' - if true, this specifies that the content is absent 282 because policy does not allow it to be given under the current 283 level of access. 285 If present with content, each of these element types MAY have one or 286 more of the following boolean attributes: 288 o 'doNotRedistribute' - if true, this specifies that the content is 289 not to be redistributed. 291 o 'specialAccess' - if true, this specifies that the content has 292 been provided due to special access rights. 294 These boolean attributes SHOULD be used in accordance with the level 295 of access being granted the recepient of the data. For example, 296 marking data as 'private' or 'denied' is to be expected if the user 297 is anonymous or has some other low level of access that does not 298 warrant viewing of that particular data. Likewise, data marked with 299 'doNotRedistribute' or 'specialAccess' is to be expected if the user 300 is authenticated and has a high level of access. 302 3.2.2 Contact Group 304 Many of the results share a set of references to contacts regarding 305 an associated role. These are represented by the following elements: 307 o 309 o 311 o 313 o 315 o 317 o 319 o 321 o 323 Each of these elements contain an entity reference. The referent of 324 each MUST be a (Section 3.2.5). 326 3.2.3 Result 328 An example of a result: 330 334 +1 7035 555 1212 336 340 345 349 350 Bill Eckels 351 352 354 358 359 Mark Kosters 360 361 363 364 365 366 369 371 AUTO-LOCK 372 373 374 377 379 AUTO-LOCK 380 381 382 385 387 AUTO-LOCK 388 389 390 393 395 STANDARD RGP 396 397 398 400 402 The result represents an instance of an ENUM domain 403 assignment. The children of the element are as follows: 405 o - the E.164 number for this ENUM domain as defined by 406 [13]. It is RECOMMENDED that only space characters be used 407 between the digits of these E.164 numbers, as of the international 408 number format defined in [14]. 410 o - a registry unique assigned identifier to an ENUM 411 domain. 413 o - MUST contain an entity reference to a referent of 414 type (Section 3.2.4). 416 o - elements containing an entity reference to the 417 registrant of this ENUM domain. The referent MUST be a 418 (Section 3.2.5) result. 420 o ENUM domain contacts - see Section 3.2.2. 422 o - may contain at least one of the following elements of 423 type 'enumStatusType' (see Section 3.2.1). 425 * - this ENUM domain falls outside the normal 426 registration rules and/or processes for registration 428 * - assigned to a registrant 430 * - available via DNS (either via delegation or direct 431 publication) 433 * - unavailable via DNS 435 * - registrant assignment is in dispute 437 * - registrant assignment removed 439 * - change of authority 441 * - modification of this ENUM domain 442 * - renewal of ENUM domain registration 444 * - period at the creation or activation of this ENUM 445 domain (see RFC 3915 [19]) 447 * - period at the renewal of this ENUM domain (see 448 RFC 3915 [19]) 450 * - period at the automatic renewal of this 451 ENUM domain (see RFC 3915 [19]) 453 * - period at the transfer of this ENUM domain 454 (see RFC 3915 [19]) 456 * - period at the redemption of this ENUM 457 domain (see RFC 3915 [19]) 459 * - change to previous status of this ENUM domain 461 * - a status only defined by its child 462 element 464 As stated in Section 3.2.1, each status value may have flags to 465 indicate the entity responsible for assigning the status (e.g. 466 actor='registrar') and the nature of the status (e.g. 467 disposition="prohibited"). Any one status value MUST NOT imply 468 other status values. For instance, is just an 469 indicatation that the ENUM domain is given special reserved 470 status; the status value must 471 also be present to indicate that the ENUM domain cannot be 472 registrered. 474 o - an element containing an entity 475 reference, the referent of which MUST be an 476 (Section 3.2.3). The intention of this element is to point to the 477 downstream registration reference. Therefore, if this is a result 478 given back by an ENUM domain registry, it should point to the ENUM 479 domain in the ENUM domain registrar or registrant service. 481 o - contains an entity reference specifying the ENUM 482 domain registry operator for this ENUM domain which MUST be a 483 (Section 3.2.6). 485 o - contains an entity reference specifying the ENUM 486 domain registrar operator for this ENUM domain which MUST be a 487 (Section 3.2.6). 489 o - contains an entity reference specifying the 490 validation entity for this ENUM domain which MUST be a 491 (Section 3.2.7). 493 o communication service providers - the following elements contain 494 an entity reference with a relationship to the ENUM domain. The 495 referent of each MUST be a 496 (Section 3.2.8). 498 * 500 * 502 * 504 * 506 * 508 o -- elements containing an entity reference to 509 validation events related to this ENUM domain. The referent MUST 510 be a (Section 3.2.9). 512 o - an element containing the date and 513 time of the initial delegation of this ENUM domain. 515 o - an element containing the date and time of 516 last renewal of this ENUM domain. 518 o - an element containing the date and time of 519 the expiration of this ENUM domain. 521 o - specifies the last time a 522 contact for the ENUM domain was added or removed. 524 o - an element containing an entity 525 reference. The referent MUST be a (Section 3.2.5) 526 responsible for the last addition or removal of a contact for this 527 ENUM domain. 529 o - an element containing the 530 date and time of the last time one of the nameservers was added or 531 removed for the delegation of this ENUM domain. 533 o - an element containing an entity 534 reference. The referent MUST be a (Section 3.2.5) 535 result and be responsible for the last addition or removal of a 536 nameserver for this ENUM domain. 538 o - an element containing the date and 539 time of the last time the data for this domain was verified by the 540 responsible registration authority. 542 o - an element containing an entity reference 543 specifying a referent that is indirectly associated with this 544 domain. 546 3.2.4 Result 548 An example of a result: 550 553 nsol184 554 a.iana-servers.net 555 192.0.2.43 556 560 562 The element represents an instance of a host registration. 563 The children of the element are as follows: 565 o - a registry unique assigned identifier for the host. 567 o - the fully qualified domain name of the host. The 568 contents of this element are a domain name and MUST conform to RFC 569 1035 [9]. 571 o - the content of which MUST conform to the a valid 572 IP version 4 host address as specified by RFC 791 [8]. 574 o - the content of which MUST conform to the a valid 575 IP version 6 host address as specified by RFC 3513 [7]. 577 o - an element containing an entity reference 578 specifying a contact associated with this host. The referent MUST 579 be (Section 3.2.5) results. 581 o - an element containing the date and time this 582 host was created. 584 o - an element containing the date and 585 time this host was last modified. 587 o - an element containing the date and 588 time this data for this host was last verified to be correct by 589 the appropriate registration authority. 591 o - an element containing an entity reference 592 specifying a referent that is indirectly associated with this 593 host. 595 3.2.5 Result 597 An example of a result: 599 602 example-admin 603 Example.Org Manager 604 Internet Assigned Numbers Authority 605 res-dom@example.org 606 607
123 Mocking Bird Lane
608 Some City 609 CA 610 00000 611 US 612 613 +1234567890 614 616 The element represents an instance of a contact 617 registration. The children of the element are as follows: 619 o - a registry unique assigned identifier for this 620 contact. 622 o - the name of the contact. 624 o - a specification of the language code to use to 625 localize the data in this result. 627 o - contains one of the following child elements: , 628 , , or . Each of these elements is a 629 "contactTypeType" as defined in Section 3.2.1. 631 o - an element containing the organization name of 632 the contact. 634 o The child element contains jurisdictional identifier of 635 this contact (an example of such an identifier is a national 636 taxation ID or a commercial registry number). 638 o - elements containing an e-mail address for this contact. 640 o - elements containing an e-mail address within an 641 internationalized domain name [15]. 643 o - elements containing a SIP URI for this contact. 645 o - elements containing children representing a 646 postal address. has the following children: 648 *
- an element containing the street address for this 649 contact. 651 * - an element containing the city for this contact. 653 * - an element containing the national region for this 654 contact. 656 * - an element containing the postal code for this 657 contact. 659 * - an element containing the country for this contact. 660 This SHOULD be a 2-letter country code compliant with ISO 3166 661 [11]. 663 o - elements containing a voice phone number for this 664 contact. If it begins with a '+' (plus) character, it MUST be a 665 number defined by E164 [13]. The format number defined in E164 666 [13] is RECOMMENDED. 668 o - elements containing a facsimile phone number for this 669 contact. If it begins with a '+' (plus) character, it MUST be a 670 number defined by E164 [13]. The format number defined in E164 671 [13] is RECOMMENDED. 673 o - an element containing the date and time this 674 contact was created. 676 o - an element containing the date and 677 time this contact was last modified. 679 o - an element containing the date and 680 time this data for this contact was last verified to be correct by 681 the appropriate registration authority. 683 o - an element containing an entity reference 684 specifying equivalents of this contact that have been translated 685 into other languages. The referent MUST be 686 (Section 3.2.5) results. 688 o - an element containing an entity reference 689 specifying a referent that is indirectly associated with this 690 contact. 692 3.2.6 Result 694 An example of a result: 696 699 703 704 Internet Assigned Numbers Authority 705 706 707 709 The result represents an entity capable of 710 registering domains. 712 The child element of 713 contains an entity reference pointing to the entity "id" in the 714 entity class "iris". 716 The child element contains the name of the 717 registration authority. 719 The child element contains an identifier of this 720 registration authority (an example of such an identifier is a 721 national taxation ID or a commercial registry number). 723 The registration authority type child elements, , 724 , and , determine the role in which this 725 registration authority plays in the process of registering ENUM 726 domains. The intent of this element is to explain the various roles 727 a registration authority may have with regards to the authority areas 728 pointed to by the element. A client MAY understand 729 the relationship of a registration authority with respect to an ENUM 730 domain by the placement of the reference in the domain (e.g. 731 or ). 733 contacts - see Section 3.2.2. 735 - an element containing an entity reference specifying 736 a referent that is indirectly associated with this registration 737 authority. 739 3.2.7 Result 741 An example of a result: 743 746 750 751 Some Government Authority 752 753 757 761 763 The result represents an entity responsible for 764 validating ENUM domains against E.164 [13] registrations. 766 The child element of contains an 767 entity reference pointing to the entity "id" in the entity class 768 "iris". 770 The child element contains the name of the 771 validation authority. 773 The child element contains an identifier of this validation 774 authority (an example of such an identifier is a national taxation ID 775 or a commercial registry number). 777 contacts - see Section 3.2.2. 779 - an element containing an entity reference specifying 780 a referent that is indirectly associated with this validation 781 authority. 783 3.2.8 Result 785 An example of a result: 787 790 794 795 Big Phone Co. 796 797 798 800 The result represents an entity 801 providing ENUM domain service. 803 The child element of 804 contains an entity reference pointing to the entity "id" in the 805 entity class "iris". 807 The child element contains the name of the 808 registration authority. 810 The child element contains an identifier of this 811 communication service provider (an example of such an identifier is a 812 national taxation ID or a commercial registry number). 814 The child element contains an identifier unique to this 815 communication service provider and identifies this communication 816 service provider with regard to its operating jurisdiction. 818 The child elements, , , , and , 819 details the capabilities of this communication service provider. The 820 capabilities this communication service provider provide to a 821 specific ENUM domain are a subset of these capabilities and are 822 expressed in the result using the , , 823 , , and entity references. 825 contacts - see Section 3.2.2. 827 - an element containing an entity reference specifying 828 a referent that is indirectly associated with this communication 829 service provider. 831 3.2.9 Result 833 An example of a result: 835 838 xyz-0123 839 843 845 The result represents a record of validation for an 846 ENUM domain. 848 The child element contains an identifier identifying this 849 validation event between an validation entity and a registrar. 851 The child element contains an identifier describing the 852 method used for validation. 854 - contains an entity reference specifying the ENUM domain 855 registrar operator for this validation event which MUST be a 856 (Section 3.2.6). 858 - contains an entity reference specifying the 859 validation entity for this validation event which MUST be a 860 (Section 3.2.7). 862 - an element containing the date and time of the 863 creation of this validation event. 865 - an element containing the date and time of the 866 expiration of this validation event. 868 - an element containing an entity reference specifying 869 a referent that is indirectly associated with this validation event. 871 3.3 Generic Code Derivatives 873 3.3.1 875 Servers MAY use the error code when a query must be 876 narrowed to yield a result set acceptable to the policies of the 877 server operator. 879 3.3.2 881 The queries , and support optional 882 language tags that allow a client to suggest to a server the 883 languages in which to scope the queries. If a client passes to the 884 server a language which the server does not support, the server MAY 885 use this error code to indicate that one of the languages is not 886 supported. 888 This element contains child elements named . 889 Each of these child elements specify a language not supported by the 890 server. When a server returns this error, it MUST give the languages 891 from the query which are not supported. 893 3.4 Support for 895 The following types of entity classes are recognized by the 896 query of IRIS for this registry: 898 o host-name - the fully qualified domain name of a nameserver. It 899 yields a (Section 3.2.4) in the response. 901 o host-handle - the registry unique identifier given a nameserver. 902 It yields a (Section 3.2.4) in the response. 904 o e164 - an E.164 number as specified by [13]. It yields a 905 (Section 3.2.3) in the response. Clients SHOULD remove all non- 906 digit characters between the digits of an E.164 number, and 907 servers MUST ignore any non-digit characters between the digits of 908 an E.164 number. (e.g. "+1 703 555 1212" is to be interpretted as 909 "+17035551212"). 911 o enum - the fully qualified name of an ENUM domain. This is a 912 domain name as specified by RFC 1035 [9]. It yields a 913 (Section 3.2.3) in the response. 915 o enum-handle - the registry unique identifier given a ENUM domain. 916 It yields a (Section 3.2.3) in the response. 918 o contact-handle - the registry unique identifier given a contact. 919 It yields a (Section 3.2.5) in the response. 921 o ipv4-address - the IPv4 address of a nameserver. It yields a 922 (Section 3.2.4) in the response. 924 o ipv6-address - the IPv6 address of a nameserver. It yields a 925 (Section 3.2.4) in the response. 927 o registration-authority - the name of a registration authority. It 928 yields a (Section 3.2.6) in the response. 930 o validation-entity - the name of an validation entity. It yields a 931 (Section 3.2.7) 933 o csp - the identifier of a communication service provider. Yields 934 a (Section 3.2.8). 936 o validation-event - the identifier for a validation event. It 937 yields a (Section 3.2.9). 939 o All names in these entity classes are case insensitive. 941 4. Formal XML Syntax 943 This registry schema is specified in the XML Schema notation. The 944 formal syntax presented here is a complete schema representation 945 suitable for automated validation of an XML instance when combined 946 with the formal schema syntax of IRIS. 948 949 955 957 958 959 ENUM registry schema 960 derived from IRIS schema 961 962 964 965 966 967 968 970 971 972 974 976 977 979 980 983 986 987 989 991 993 994 995 996 997 998 999 1001 1006 1007 1008 1010 1012 1013 1015 1016 1017 1019 1022 1023 1027 1028 1030 1032 1034 1037 1039 1041 1043 1045 1047 1049 1050 1051 1052 1057 1058 1059 1060 1062 1067 1068 1069 1071 1073 1074 1076 1077 1079 1084 1086 1087 1088 1090 1095 1096 1097 1099 1101 1102 1104 1105 1106 1109 1112 1115 1118 1119 1120 1121 1122 1124 1129 1130 1131 1133 1135 1136 1139 1142 1145 1148 1151 1154 1157 1158 1160 1162 1163 1165 1167 1168 1170 1172 1174 1176 1178 1179 1181 1183 1185 1187 1188 1190 1193 1194 1196 1198 1199 1200 1202 1203 1205 1207 1208 1209 1210 1214 1215 1218 1219 1221 1223 1225 1227 1228 1230 1232 1233 1236 1237 1239 1240 1241 1242 1243 1245 1246 1247 1249 1251 1252 1254 1255 1258 1264 1269 1274 1275 1281 1286 1290 1291 1294 1297 1300 1303 1306 1309 1312 1315 1318 1321 1324 1328 1331 1334 1337 1340 1343 1344 1345 1346 1351 1356 1361 1366 1371 1377 1382 1387 1392 1397 1403 1409 1415 1421 1426 1432 1436 1437 1438 1439 1441 1446 1447 1448 1450 1452 1453 1455 1456 1462 1465 1470 1475 1480 1486 1492 1498 1502 1503 1504 1505 1507 1512 1513 1514 1516 1518 1519 1521 1522 1528 1534 1539 1543 1544 1545 1548 1551 1554 1557 1558 1559 1560 1566 1572 1578 1584 1590 1594 1595 1596 1602 1608 1614 1620 1626 1627 1628 1629 1635 1641 1647 1653 1659 1664 1668 1669 1670 1671 1673 1678 1679 1680 1682 1684 1685 1687 1688 1693 1698 1703 1706 1708 1709 1710 1712 1714 1715 1717 1718 1719 1720 1721 1725 1726 1727 1728 1730 1735 1736 1737 1739 1741 1742 1744 1745 1750 1755 1760 1761 1765 1766 1767 1768 1770 1775 1776 1777 1779 1781 1782 1784 1785 1790 1795 1800 1805 1808 1812 1813 1814 1818 1819 1820 1824 1825 1826 1830 1831 1832 1836 1837 1838 1839 1840 1844 1845 1846 1847 1849 1854 1855 1856 1857 1859 1860 1862 1863 1868 1873 1878 1883 1889 1895 1899 1900 1901 1902 1904 1909 1910 1911 1913 1914 1915 1920 1925 1930 1935 1940 1945 1950 1955 1956 1958 1959 1960 1962 1964 1967 1970 1973 1976 1978 1980 1981 1983 1985 1986 1987 1989 1991 1992 1994 1996 1997 1998 2000 2002 2003 2005 2007 2008 2009 2011 2013 2014 2016 2018 2019 2020 2022 2024 2025 2030 2034 2035 2036 2038 2042 2043 2044 2045 2046 2050 2051 2052 2054 2058 2059 2060 2061 2062 2063 2065 2067 2068 2070 2072 2074 2075 2076 2077 2079 2080 2082 2084 2086 2087 2088 2089 2092 2094 2096 2097 2101 2102 2103 2105 2109 2110 2111 2112 2113 2114 2116 2118 2119 2120 2121 2122 2124 2125 2126 2128 2133 2134 2135 2137 2139 2140 2142 2143 2148 2149 2150 2151 2153 2158 2160 Figure 8: ereg.xsd 2162 5. BEEP Transport Compliance 2164 IRIS allows several extensions of the core capabilities. This 2165 section outlines those extensions allowable by IRIS-BEEP [6]. 2167 5.1 Message Pattern 2169 This registry type uses the default message pattern as described in 2170 IRIS-BEEP [6]. 2172 5.2 Server Authentication 2174 This registry type only uses the basic TLS server authentication 2175 method as described in IRIS-BEEP [6]. 2177 6. URI Resolution 2179 6.1 Application Service Label 2181 The application service label associated with this registry type MUST 2182 be "EREG1". This is the abbreviated form of the URN for this 2183 registry type, urn:ietf:params:xml:ns:ereg1. 2185 7. Internationalization Considerations 2187 Implementers should be aware of considerations for 2188 internationalization in IRIS [5]. 2190 The social data associated with contacts may be non-ASCII, and could 2191 contain virtually any Unicode character. The element is 2192 provided in queries that have potential to traverse such data. 2193 Clients should use these elements to indicate to the server of the 2194 target languages desired, and servers should use these elements to 2195 better enable normalization and search processes (see 2196 ). 2198 Clients needing to localize the data tags in this protocol should 2199 take note that localization is only needed on the names of XML 2200 elements and attributes with the exception of elements containing 2201 date and time information. The schema for this registry has been 2202 designed so that clients need not interpret the content of elements 2203 or attributes for localization, other than those elements containing 2204 date and time information. 2206 Clients should also make use of the elements provided in 2207 many of the results. Results containing data that may be in Unicode 2208 are accompanied by these elements in order to aid better presentation 2209 of the data to the user. 2211 The "dateTimePrivacyType" element content conforms to the XML Schema 2212 [3] data type "dateTime". The contents of this element MUST be 2213 specified using the 'Z' indicator for Coordinated Universal Time 2214 (UTC). 2216 8. IANA Considerations 2218 8.1 XML Namespace URN Registration 2220 This document makes use of a proposed XML namespace and schema 2221 registry specified in XML_URN [17]. Accordingly, the following 2222 registration information is provided for the IANA: 2224 o URN/URI: 2226 * urn:ietf:params:xml:schema:ereg1 2228 o Contact: 2230 * Andrew Newton 2232 o XML: 2234 * The XML Schema specified in Section 4 2236 o URN/URI: 2238 * urn:ietf:params:xml:ns:ereg1 2240 o Contact: 2242 * Andrew Newton 2244 o XML: 2246 * None. 2248 8.2 S-NAPTR Registration 2250 The following S-NAPTR application service label will need to be 2251 registered with IANA according to the IANA considerations defined in 2252 IRIS [5]: 2254 EREG1 2256 8.3 BEEP Registration 2258 The following BEEP Profile URI is to be registeried with IANA, in 2259 addition to the registration provided in IRIS-BEEP [6]. 2261 http://iana.org/beep/iris1/ereg1 2263 9. Security Considerations 2265 This document lays out no new considerations for security precautions 2266 beyond that specified in IRIS [5]. 2268 10. Normative References 2270 [1] World Wide Web Consortium, "Extensible Markup Language (XML) 2271 1.0", W3C XML, February 1998, 2272 . 2274 [2] World Wide Web Consortium, "Namespaces in XML", W3C XML 2275 Namespaces, January 1999, 2276 . 2278 [3] World Wide Web Consortium, "XML Schema Part 2: Datatypes", 2279 W3C XML Schema, October 2000, 2280 . 2282 [4] World Wide Web Consortium, "XML Schema Part 1: Structures", 2283 W3C XML Schema, October 2000, 2284 . 2286 [5] Newton, A. and M. Sanz, "Internet Registry Information 2287 Service", RFC 3981, January 2005. 2289 [6] Newton, A. and M. Sanz, "Internet Registry Information Service 2290 (IRIS) over Blocks Extensible Exchange Protocol (BEEP)", 2291 RFC 3983, January 2005. 2293 [7] Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6) 2294 Addressing Architecture", RFC 3513, April 2003. 2296 [8] Postel, J., "Internet Protocol", STD 5, RFC 791, 2297 September 1981. 2299 [9] Mockapetris, P., "Domain names - implementation and 2300 specification", STD 13, RFC 1035, November 1987. 2302 [10] Bradner, S., "Key words for use in RFCs to Indicate Requirement 2303 Levels", RFC 2119, BCP 14, March 1997. 2305 [11] International Organization for Standardization, "Codes for the 2306 representation of names of countries, 3rd edition", 2307 ISO Standard 3166, August 1988. 2309 [12] Braden, R., "Requirements for Internet Hosts - Application and 2310 Support", STD 3, RFC 1123, October 1989. 2312 [13] International Telecommunications Union, "The International 2313 Public Telecommunication Numbering Plan", ITU-T Recommendation 2314 E.164, February 2005. 2316 [14] International Telecommunications Union, "Notation for national 2317 and international telephone numbers, e-mail addresses and Web 2318 addresses", ITU-T Recommendation E.123, February 2001. 2320 [15] Faltstrom, P., Hoffman, P., and A. Costello, 2321 "Internationalizing Domain Names in Applications (IDNA)", 2322 RFC 3490, March 2003. 2324 [16] Hoffman, P. and M. Blanchet, "Nameprep: A Stringprep Profile 2325 for Internationalized Domain Names (IDN)", RFC 3491, 2326 March 2003. 2328 [17] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2329 January 2004. 2331 [18] Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource 2332 Identifiers (URI) Dynamic Delegation Discovery System (DDDS) 2333 Application (ENUM)", RFC 3761, April 2004. 2335 [19] Hollenbeck, S., "Domain Registry Grace Period Mapping for the 2336 Extensible Provisioning Protocol (EPP)", RFC 3915, 2337 September 2004. 2339 Author's Address 2341 Andrew L. Newton 2342 VeriSign, Inc. 2343 21345 Ridgetop Circle 2344 Sterling, VA 20166 2345 USA 2347 Phone: +1.7039483382 2348 Email: anewton@verisignlabs.com; andy@hxr.us 2349 URI: http://www.verisignlabs.com/ 2351 Appendix A. Contributions and Acknowledgements 2353 This document is a derivative of the specification used to define 2354 forward domain registries for IRIS. Marcos Sanz was a major 2355 contributor to that specification and many of his words and ideas are 2356 present in this document. Other contributors include Alexander 2357 Mayrhofer, Bernie Hoeneisen, Otmar Lendl, and Scott Hollenbeck. 2359 Intellectual Property Statement 2361 The IETF takes no position regarding the validity or scope of any 2362 Intellectual Property Rights or other rights that might be claimed to 2363 pertain to the implementation or use of the technology described in 2364 this document or the extent to which any license under such rights 2365 might or might not be available; nor does it represent that it has 2366 made any independent effort to identify any such rights. Information 2367 on the procedures with respect to rights in RFC documents can be 2368 found in BCP 78 and BCP 79. 2370 Copies of IPR disclosures made to the IETF Secretariat and any 2371 assurances of licenses to be made available, or the result of an 2372 attempt made to obtain a general license or permission for the use of 2373 such proprietary rights by implementers or users of this 2374 specification can be obtained from the IETF on-line IPR repository at 2375 http://www.ietf.org/ipr. 2377 The IETF invites any interested party to bring to its attention any 2378 copyrights, patents or patent applications, or other proprietary 2379 rights that may cover technology that may be required to implement 2380 this standard. Please address the information to the IETF at 2381 ietf-ipr@ietf.org. 2383 Disclaimer of Validity 2385 This document and the information contained herein are provided on an 2386 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2387 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 2388 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2389 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2390 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2391 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2393 Copyright Statement 2395 Copyright (C) The Internet Society (2005). This document is subject 2396 to the rights, licenses and restrictions contained in BCP 78, and 2397 except as set forth therein, the authors retain all their rights. 2399 Acknowledgment 2401 Funding for the RFC Editor function is currently provided by the 2402 Internet Society.