RFC4414 日本語訳

4414 An ENUM Registry Type for the Internet Registry InformationService (IRIS). A. Newton. February 2006. (Format: TXT=89985 bytes) (Status: PROPOSED STANDARD)
プログラムでの自動翻訳です。
英語原文

Network Working Group                                          A. Newton
Request for Comments: 4414                                VeriSign, Inc.
Category: Standards Track                                  February 2006

コメントを求めるワーキンググループA.ニュートンの要求をネットワークでつないでください: 4414年のベリサインInc.カテゴリ: 標準化過程2006年2月

                         An ENUM Registry Type
          for the Internet Registry Information Service (IRIS)

インターネット登録情報サービスのためのENUM登録タイプ(虹彩)

Status of This Memo

このメモの状態

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

このドキュメントは、インターネットコミュニティにインターネット標準化過程プロトコルを指定して、改良のために議論と提案を要求します。このプロトコルの標準化状態と状態への「インターネット公式プロトコル標準」(STD1)の現行版を参照してください。このメモの分配は無制限です。

Copyright Notice

版権情報

   Copyright (C) The Internet Society (2006).

Abstract

要約

   This document describes an Internet Registry Information Service
   (IRIS) registry schema for registered ENUM information.  The schema
   extends the necessary query and result operations of IRIS to provide
   the functional information service needs for syntaxes and results
   used by ENUM registries.

このドキュメントは登録されたENUM情報のためにインターネットRegistry情報Service(IRIS)登録図式について説明します。図式は、サービスが構文に必要とする機能情報とENUM登録によって使用される結果を提供するためにIRISの必要な質問と結果操作を広げています。

Newton                      Standards Track                     [Page 1]

RFC 4414              ENUM Registry Type for IRIS          February 2006

ニュートンStandardsは虹彩2006年2月にRFC4414ENUM登録タイプを追跡します[1ページ]。

Table of Contents

   1. Introduction ....................................................3
   2. Document Terminology ............................................3
   3. Schema Description ..............................................3
      3.1. Query Derivatives ..........................................3
           3.1.1. <findEnumsByE164> Query .............................3
           3.1.2. <findEnumsByContact> Query ..........................4
           3.1.3. <findContacts> Query ................................4
           3.1.4. <findEnumsByHost> Query .............................4
           3.1.5. Contact Search Group ................................5
      3.2. Result Derivatives .........................................5
           3.2.1. Privacy Labels ......................................5
           3.2.2. Contact Group .......................................7
           3.2.3. <enum> Result .......................................8
           3.2.4. <host> Result ......................................12
           3.2.5. <contact> Result ...................................13
           3.2.6. <registrationAuthority> Result .....................15
           3.2.7. <validationEntity> Result ..........................16
           3.2.8. <communicationServiceProvider> Result ..............17
           3.2.9. <validationEvent> Result ...........................18
      3.3. Generic Code Derivatives ..................................19
           3.3.1. <searchTooWide> ....................................19
           3.3.2. <languageNotSupported> .............................19
      3.4. Support for <iris:lookupEntity> ...........................19
   4. Formal XML Syntax ..............................................21
   5. Blocks Extensible Exchange Protocol (BEEP) Transport
      Compliance .....................................................46
      5.1. Message Pattern ...........................................46
      5.2. Server Authentication .....................................46
   6. URI Resolution .................................................46
      6.1. Application Service Label .................................46
   7. Internationalization Considerations ............................46
   8. IANA Considerations ............................................47
      8.1. XML Namespace URN Registration ............................47
      8.2. S-NAPTR Registration ......................................48
      8.3. BEEP Registration .........................................48
   9. Security Considerations ........................................48
   10. Normative References ..........................................48
   A.  Contributions and Acknowledgements ............................50

1. 序論…3 2. 用語を記録してください…3 3. 図式記述…3 3.1. 派生物について質問してください…3 3.1.1. <findEnumsByE164>質問…3 3.1.2. <findEnumsByContact>質問…4 3.1.3. <findContacts>質問…4 3.1.4. <findEnumsByHost>質問…4 3.1.5. 調査班に連絡してください…5 3.2. 結果派生物…5 3.2.1. プライバシーラベル…5 3.2.2. グループに連絡してください…7 3.2.3. <enum>結果…8 3.2.4. <ホスト>結果…12 3.2.5. <接触>結果…13 3.2.6. <registrationAuthority>結果…15 3.2.7. <validationEntity>結果…16 3.2.8. <communicationServiceProvider>結果…17 3.2.9. <validationEvent>結果…18 3.3. ジェネリックコード派生物…19 3.3.1. <searchTooWide>…19 3.3.2. <languageNotSupported>…19 3.4. <には、虹彩: lookupEntityが>であるとサポートしてください…19 4. 正式なXML構文…21 5. 広げることができるブロックはプロトコル(ビープ音)輸送コンプライアンスを交換します…46 5.1. メッセージパターン…46 5.2. サーバー証明…46 6. URI解決…46 6.1. アプリケーション・サービスラベル…46 7. 国際化問題…46 8. IANA問題…47 8.1. XML名前空間つぼの登録…47 8.2. S-NAPTR登録…48 8.3. 登録を鳴らしてください…48 9. セキュリティ問題…48 10. 標準の参照…48のA.貢献と承認…50

Newton                      Standards Track                     [Page 2]

RFC 4414              ENUM Registry Type for IRIS          February 2006

ニュートンStandardsは虹彩2006年2月にRFC4414ENUM登録タイプを追跡します[2ページ]。

1.  Introduction

1. 序論

   This document describes an IRIS registry schema for registries of
   ENUM data using an XML Schema [4] derived from and using the IRIS [5]
   schema.

このドキュメントは、[4] IRIS[5]図式を引き出されて、使用して、XML Schemaを使用することでIRIS登録図式についてENUMデータの登録に説明します。

   The schema given is this document is specified using the Extensible
   Markup Language (XML) 1.0 as described in XML [1], XML Schema
   notation as described in XML_SD [3] and XML_SS [4], and XML
   Namespaces as described in XML_NS [2].

与えられた図式はこのドキュメントがXML[1](XML_サウスダコタ[3]、XML_SS[4]、およびXML_NS[2]で説明されるXML Namespacesで説明されるXML Schema記法)で説明されるようにExtensible Markup Language(XML)1.0を使用することで指定されるということです。

2.  Document Terminology

2. ドキュメント用語

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [10].

キーワード“MUST"、「必須NOT」が「必要です」、“SHALL"、「」、“SHOULD"、「「推薦され」て、「5月」の、そして、「任意」のNOTはRFC2119[10]で説明されるように本書では解釈されることであるべきですか?

   This document uses the term "ENUM" as the fully qualified domain name
   following the conventions of ENUM [17].

ENUM[17]のコンベンションに続いて、このドキュメントは完全修飾ドメイン名として"ENUM"という用語を使用します。

3.  Schema Description

3. スキーマ記述

   IRIS requires the derivation of both query and result elements by a
   registry schema.  These descriptions follow.

IRISは登録図式で質問と結果要素の両方の派生を必要とします。これらの記述は続きます。

   References to XML elements with no namespace qualifier are from the
   schema defined in Section 4.  References to elements and attributes
   with the "iris" XML namespace qualifier are from the schema defined
   in IRIS [5].

名前空間資格を与える人のいないXML要素の参照はセクション4で定義された図式から来ています。「虹彩」XML名前空間資格を与える人がいる要素と属性の参照はIRIS[5]で定義された図式から来ています。

   The descriptions contained within this section refer to XML elements
   and attributes and their relation to the exchange of data within the
   protocol.  These descriptions also contain specifications outside the
   scope of the formal XML syntax.  Therefore, this section will use
   terms defined by RFC 2119 [10] to describe the specification outside
   the scope of the formal XML syntax.  While reading this section,
   please reference Section 4 for needed details on the formal XML
   syntax.

このセクションの中に含まれた記述はプロトコルの中にデータの交換とのXML要素、属性、および彼らの関係を示します。また、これらの記述は正式なXML構文の範囲の外に仕様を保管しています。したがって、このセクションはRFC2119[10]によって定義された、正式なXML構文の範囲の外で仕様を説明した用語を使用するでしょう。このセクションを読んでいる間、正式なXML構文に関する必要な詳細のためにセクション4に参照をつけてください。

3.1.  Query Derivatives

3.1. 質問派生物

3.1.1.  <findEnumsByE164> Query

3.1.1. <findEnumsByE164>質問

   <findEnumsByE164> finds ENUM domains by searching on prefixes of
   E.164 numbers and returns <enum> (Section 3.2.3) results.

<findEnumsByE164>はE.164番号の接頭語で探すことによってENUMにドメインを見つけて、<enum>(セクション3.2.3)に結果を返します。

   The E.164 prefix is specified using the <e164Prefix> child of
   <findEnumsByE164>.  An optional child element of <findEnumsByE164>,

E.164接頭語は、<findEnumsByE164>の<e164Prefix>子供を使用することで指定されます。 <findEnumsByE164>の任意の子供要素

Newton                      Standards Track                     [Page 3]

RFC 4414              ENUM Registry Type for IRIS          February 2006

ニュートンStandardsは虹彩2006年2月にRFC4414ENUM登録タイプを追跡します[3ページ]。

   <specificity>, can narrow the search to ENUM domains associated with
   E.164 numbers that are either more specific or less specific.  If the
   <specificity> element is present and has the content 'less', then the
   search is to be narrowed to E.164 numbers that are less specific
   (i.e., have fewer digits).  If the <specificity> element is present
   and has the content 'more', then the search is to be narrowed to
   E.164 numbers that are more specific (i.e., have more digits).

<の特異性>、缶は、より特定の、または、それほど特定でないE.164番号に関連しているENUMドメインに検索を狭くします。 <特異性>要素が存在していて、それほど'内容を持っていないなら、検索はそれほど特定でないE.164番号に狭くされる(すなわち、より少ないケタを持ってください)ことです。 <特異性>要素が'さらに'存在していて、内容を持っているなら、検索は、より特定のE.164番号に狭くされる(すなわち、より多くのケタを持ってください)ことです。

3.1.2.  <findEnumsByContact> Query

3.1.2. <findEnumsByContact>質問

   <findEnumsByContact> finds ENUM domains by searches on fields
   associated with an ENUM domain's contact.

<findEnumsByContact>はENUMドメインの接触に関連しているフィールドで検索でENUMにドメインを見つけます。

   The allowable search fields are handled with either the
   <contactHandle> element or one of the elements in the
   "contactSearchGroup" (see Section 3.1.5).  The <contactHandle>
   element allows for the ENUM domains to be selected based on the
   contact having the specified contact handle.

許容できる検索分野は<contactHandle>要素か"contactSearchGroup"の要素の1つのどちらかで扱われます(セクション3.1.5を見てください)。 >要素が、ENUMドメインが選択されるのを許容する<contactHandleは指定された接触ハンドルを持っている接触を基礎づけました。

   The query MAY also be constrained further using the optional <role>
   element.  The contents of this element signify the role the contact
   has with the ENUM domain.

また、さらに任意の<役割の>要素を使用して、質問も強制的であるかもしれません。この要素の内容は接触がENUMドメインで持っている役割を意味します。

   This query also provides optional <language> elements containing
   language tags.  Clients MAY use these elements to give a hint about
   the natural language(s) of the affected element.  Servers MAY use
   this information in processing the query, such as tailoring
   normalization routines to aid in more effective searches.

また、この質問は言語タグを含む任意の<言語>要素を提供します。クライアントは、影響を受ける要素の自然言語に関してちょっとほのめかすのにこれらの要素を使用するかもしれません。サーバは、より効果的な検索で支援するために正常化ルーチンを合わせなどなどの質問を処理する際にこの情報を使用するかもしれません。

3.1.3.  <findContacts> Query

3.1.3. <findContacts>質問

   <findContacts> searches for contacts given search constraints.

検索規制を考えて、<findContacts>は接触を捜し求めます。

   The allowable search fields are handled by one of the elements in the
   "contactSearchGroup" (see Section 3.1.5).

許容できる検索分野は"contactSearchGroup"の要素の1つによって扱われます(セクション3.1.5を見てください)。

   This query also provides optional <language> elements containing
   language tags.  Clients MAY use these elements to give a hint about
   the natural language(s) of the affected element.  Servers MAY use
   this information in processing the query, such as tailoring
   normalization routines to aid in more effective searches.

3.1.4.  <findEnumsByHost> Query

3.1.4. <findEnumsByHost>質問

   This query does a simple search for the ENUM domains being hosted by
   a name server.  The search is constrained using either the host name
   [12], host handle, IPv4 address, or IPv6 address of the name server.

この質問はネームサーバによって接待されるENUMドメインのための単純検索をします。検索は、ネームサーバのホスト名[12]、ホストハンドル、IPv4アドレス、またはIPv6アドレスを使用することで強制的です。

Newton                      Standards Track                     [Page 4]

RFC 4414              ENUM Registry Type for IRIS          February 2006

ニュートンStandardsは虹彩2006年2月にRFC4414ENUM登録タイプを追跡します[4ページ]。

3.1.5.  Contact Search Group

3.1.5. 連絡調査班

   Some of the queries above have similar query constraints for
   searching on contacts.  This section describes those common
   parameters.

上の質問のいくつかには、接触で探す同様の質問規制があります。このセクションはそれらの一般的なパラメタについて説明します。

   <commonName> allows the query to be constrained based on the common
   name of the contact.  The constraint can either constrain the query
   by an exact match using the <exactMatch> element, or it may constrain
   the query by a subset of the common name using the <beginsWith> and
   <endsWith> elements.

<commonName>は、質問が接触の一般名に基づいて抑制されるのを許容します。規制が完全な一致で<exactMatch>要素を使用することで質問を抑制できますか、またはそれは、一般名の部分集合で<beginsWith>と<endsWith>要素を使用することで質問を抑制するかもしれません。

   <organization> allows the query to be constrained based on the
   organization name of the contact.  It has the same semantics as the
   <commonName> element.

<組織>は、質問が接触の組織名に基づいて抑制されるのを許容します。それには、<commonName>要素と同じ意味論があります。

   <eMail> constrains the query based on the e-mail address of the
   contact.  This may be done by an exact e-mail address using the
   <exactMatch> element or by any e-mail address in a domain using the
   <inDomain> element.  The <inDomain> MUST only contain a valid domain
   name (i.e., no '@' symbol), and the matching SHOULD take place only
   on the domain given (i.e., no partial matches with respect to
   substrings or parent domains).  If either the contents of the
   <inDomain> element or domain part of the contents of the <exactMatch>
   element contain a name with non-ASCII characters, they MUST be
   normalized according to the processes of RFC 3491 [15].

<eMail>は接触のEメールアドレスに基づく質問を抑制します。 <exactMatch>要素を使用する正確なEメールアドレスかドメインのどんなEメールアドレスも、<inDomain>要素を使用することでこれをするかもしれません。 <inDomain>は有効なドメイン名(すなわち、'@'シンボルがない)を保管するだけでよいです、そして、(すなわち、サブストリングか親ドメインに関する部分的なマッチがありません)と考えて、合っているSHOULDはドメインだけで行われます。 <inDomain>要素の内容か<exactMatch>要素の内容のドメイン部分のどちらかが非ASCII文字の名前を含んでいるなら、RFC3491[15]のプロセスに従って、彼らを正常にしなければなりません。

   The <city>, <region>, and <postalCode> elements restrict the scope of
   the query based on the city, region, or postal code of the contact,
   respectively.  Each one must only contain an <exactMatch> element
   containing the exact city, region, or postal code (i.e., no substring
   searches).

<都市の>、<領域>、および<postalCode>要素はそれぞれ接触の都市、領域、または郵便番号に基づく質問の範囲を制限します。各々は正確な都市、領域、または郵便番号を含む<exactMatch>要素を含むだけでよいです(すなわち、サブストリングは全く探されません)。

3.2.  Result Derivatives

3.2. 結果派生物

3.2.1.  Privacy Labels

3.2.1. プライバシーラベル

   Several of the results in this registry type have values that cannot
   be given but must be specified as present or must be flagged so that
   clients do not divulge them.  In order to achieve this, some of the
   results use the following element types:

与えることができませんが、プレゼントとして指定しなければならないか、または旗を揚げさせなければならない値がこの登録タイプのいくつかの結果にあるので、クライアントは彼らを明かしません。これを達成するために、結果のいくつかが以下の要素型を使用します:

   o  "dateTimePrivacyType" - contains the XML Schema [3] data type
      "dateTime".  The contents of this element MUST be specified using
      the 'Z' indicator for Coordinated Universal Time (UTC).

o "dateTimePrivacyType"--"dateTime"というXML Schema[3]データ型を含んでいます。協定世界時(UTC)の間、'Z'インディケータを使用して、この要素のコンテンツを指定しなければなりません。

   o  "stringPrivacyType" - contains the XML Schema [3] data type
      "string".

o "stringPrivacyType"--「ストリング」というXML Schema[3]データ型を含んでいます。

Newton                      Standards Track                     [Page 5]

RFC 4414              ENUM Registry Type for IRIS          February 2006

ニュートンStandardsは虹彩2006年2月にRFC4414ENUM登録タイプを追跡します[5ページ]。

   o  "normalizedStringPrivacyType" - contains the XML Schema [3] data
      type "normalizedString".

o "normalizedStringPrivacyType"--"normalizedString"というXML Schema[3]データ型を含んでいます。

   o  "tokenPrivacyType" - contains the XML Schema [3] data type
      "token".

o "tokenPrivacyType"--「トークン」というXML Schema[3]データ型を含んでいます。

   o  "enumStatusType" - describes a state for an ENUM domain.  This
      element has the following optional attributes:

o "enumStatusType"--ENUMドメインに状態について説明します。この要素には、以下の任意の属性があります:

      *  'scope' - indicates the scope or origin of the status value.

* '範囲'--状態値の範囲か発生源を示します。

      *  'disposition' - contains either the value "pending", meaning
         that initial processing for this status has begun and is not
         yet complete, or the value "prohibited", meaning this ENUM
         domain cannot achieve this status according to either the
         registry or registrar of this ENUM domain.

* '気質'--この状態のための初期の処理が始まって、まだ完全でないことを意味する「未定」の値かこのENUMドメインの登録か記録係に応じてこのENUMドメインがこの状態を獲得できないことを意味して、「禁止された」値のどちらかを含んでいます。

      *  'actor' - contains either the value "registry", meaning this
         status value has been associated with this ENUM domain by the
         registry, or the value "registrar", meaning this status value
         has been associated with this ENUM domain by the registrar.

* '俳優'--この状態値が記録係でこのENUMドメインに関連していることを意味して、この状態値が登録、または値の「記録係」でこのENUMドメインに関連していることを意味して、値の「登録」を含んでいます。

      This element has the following optional child elements:

この要素には、以下の任意の子供要素があります:

      *  <appliedDate> - indicates the date and time the status was
         applied.

* <appliedDate>--状態が適用された日時を示します。

      *  <description> - provides a textual description of the status.
         This element has a required 'language' attribute.

* <記述>--状態の原文の記述を提供します。この要素には、必要な'言語'属性があります。

      *  <subStatus> - indicates a jurisdictional-dependent reason for
         this status value.  This element has a required 'authority'
         attribute to indicate the jurisdictional authority associated
         with this sub-status.

* <subStatus>--この状態値の司法権に依存する理由を示します。この要素には、このサブ状態に関連している司法権の権威を示す必要な'権威'属性があります。

   o  "contactTypeType" - contains an optional <description> child
      elements.  Each <description> child element requires a 'language'
      attribute.

o "contactTypeType"--任意の<記述>子供要素を含んでいます。それぞれの<記述>子供要素は'言語'属性を必要とします。

   As specified, they are nillable and therefore may be present with
   empty content or present with their specified content.  The use of
   these elements is also optional.

指定されるように、したがって、それらは、nillableで、空の内容の現在である、または自己の指定された内容について存在しているかもしれません。また、これらの要素の使用も任意です。

   If present without content, each of these element types MUST have one
   or more of the following boolean attributes:

内容なしで存在しているなら、これらの要素型各人には、以下の論理演算子属性の1つ以上がなければなりません:

   o  'private' - if true, this specifies that the content is absent
      because it may never be published.

o '個人的'--本当であるなら、これは、それが決して発行されないかもしれないので内容に欠けていると指定します。

Newton                      Standards Track                     [Page 6]

RFC 4414              ENUM Registry Type for IRIS          February 2006

ニュートンStandardsは虹彩2006年2月にRFC4414ENUM登録タイプを追跡します[6ページ]。

   o  'denied' - if true, this specifies that the content is absent
      because policy does not allow it to be given under the current
      level of access.

o これが、方針が、それが現在のアクセスのレベルの下で与えられているのを許容しないので内容が欠けていると本当に指定するなら、'否定されます'。

   If present with content, each of these element types MAY have one or
   more of the following boolean attributes:

内容について存在しているなら、これらの要素型各人には、以下の論理演算子属性の1つ以上があるかもしれません:

   o  'doNotRedistribute' - if true, this specifies that the content is
      not to be redistributed.

o 'doNotRedistribute'--本当であるなら、これは、内容が再配付されないことであると指定します。

   o  'specialAccess' - if true, this specifies that the content has
      been provided due to special access rights.

o 'specialAccess'--本当であるなら、これは、内容が特別なアクセス権のため提供されたと指定します。

   These boolean attributes SHOULD be used in accordance with the level
   of access being granted the recipient of the data.  For example,
   marking data as 'private' or 'denied' is to be expected if the user
   is anonymous or has some other low level of access that does not
   warrant viewing of that particular data.  Likewise, data marked with
   'doNotRedistribute' or 'specialAccess' is to be expected if the user
   is authenticated and has a high level of access.

これらの論理演算子はSHOULDを結果と考えます。データの受取人に与えられるアクセスのレベルに従って、使用されてください。例えば、ユーザに、匿名である、またはその特定のデータについて見るのを保証しないある他の低アクセスのレベルがあるなら、'個人的である'か'否定される'としてデータをマークするのは予想されることになっています。同様に、'doNotRedistribute'か'specialAccess'と共にマークされたデータはユーザが認証されて、高いアクセスのレベルを持っているなら予想されることです。

3.2.2.  Contact Group

3.2.2. 連絡調整グループ

   Many of the results share a set of references to contacts regarding
   an associated role.  These are represented by the following elements:

結果の多くが関連役割に関して接触の1セットの参照を共有します。これらは以下の要素によって表されます:

   o  <billingContact>

o <billingContact>。

   o  <technicalContact>

o <technicalContact>。

   o  <administrativeContact>

o <administrativeContact>。

   o  <legalContact>

o <legalContact>。

   o  <zoneContact>

o <zoneContact>。

   o  <abuseContact>

o <abuseContact>。

   o  <securityContact>

o <securityContact>。

   o  <otherContact>

o <otherContact>。

   Each of these elements contains an entity reference.  The referent of
   each MUST be a <contact> (Section 3.2.5).

それぞれのこれらの要素は実体参照を含んでいます。それぞれの指示物は<接触>であるに違いありません(セクション3.2.5)。

Newton                      Standards Track                     [Page 7]

RFC 4414              ENUM Registry Type for IRIS          February 2006

ニュートンStandardsは虹彩2006年2月にRFC4414ENUM登録タイプを追跡します[7ページ]。

3.2.3.  <enum> Result

3.2.3. <enum>結果

   An example of a <enum> result:

<enum>結果に関する例:

     <enum
       authority="3.0.7.1.e164.arpa" registryType="ereg1"
       entityClass="enum-handle" entityName="555-1234.001" >

"3.0.7.1.e164.arpa"<enum権威=registryTypeは「「enum-ハンドル」ereg1" entityClass=entityNameは「555-1234.001」>と等しいこと」と等しいです。

       <e164Number>+1 703 555 1234</e164Number>

<e164Number>+1 703 555 1234</e164Number>。

       <nameServer
           iris:referentType="ereg:host"
           authority="3.0.7.1.e164.arpa" registryType="ereg1"
           entityClass="host-handle" entityName="ns1.001" />
       <nameServer
           iris:referentType="ereg:host"
           authority="3.0.7.1.e164.arpa" registryType="ereg1"
           entityClass="host-handle" entityName="ns2.001" />

「><nameServer虹彩: referentType=「ereg: ホスト」"3.0.7.1.e164.arpa"権威=registryType=ns1.001"/「ereg1" entityClass=」ホストハンドル」「<nameServer虹彩: referentType=「ereg: ホスト」"3.0.7.1.e164.arpa"権威=registryType=「ereg1" entityClass=」ホストハンドル」entityName=entityNameは「ns2.001"/>」と等しいです。

       <registrant
         iris:referentType="ereg:contact"
         authority="3.0.7.1.e164.arpa" registryType="ereg1"
         entityClass="contact-handle" entityName="beb140">
         <iris:displayName language="en">
           Bill Eckels
         </iris:displayName>
       </registrant>

「<記入者虹彩: referentType=「ereg: 接触」"3.0.7.1.e164.arpa"権威=registryType=「ereg1" entityClass=」接触ハンドル」entityNameが等しい、「beb140、「><虹彩: displayName言語=」アン「>ビルEckels</虹彩: displayName></記入者>」

       <technicalContact
         iris:referentType="ereg:contact"
         authority="3.0.7.1.e164.arpa" registryType="ereg1"
         entityClass="contact-handle" entityName="mak21">
         <iris:displayName language="en">
           Mark Kosters
         </iris:displayName>
       </technicalContact>

「<technicalContact虹彩: referentType=「ereg: 接触」"3.0.7.1.e164.arpa"権威=registryType=「ereg1" entityClass=」接触ハンドル」entityNameは「mak21"><虹彩: displayName言語=」アン「>マークKosters</虹彩: displayName></technicalContact>」と等しいです。

       <status>
         <create/>
         <active/>
         <delete
           actor="registrar"
           disposition="prohibited">
           <subStatus
             authority="regr.example">
             AUTO-LOCK
           </subStatus>
         </delete>

<状態><が作成する、/><能動態/><が俳優=「記録係」気質=を削除する、「禁止、「><subStatus権威が等しい、「regr.example、「>AUTO-LOCK</subStatus></は>を削除します」。

Newton                      Standards Track                     [Page 8]

RFC 4414              ENUM Registry Type for IRIS          February 2006

ニュートンStandardsは虹彩2006年2月にRFC4414ENUM登録タイプを追跡します[8ページ]。

         <update
           actor="registrar"
           disposition="prohibited">
           <subStatus
             authority="regr.example">
             AUTO-LOCK
           </subStatus>
         </update>
         <transfer
           actor="registrar"
           disposition="prohibited">
           <subStatus
             authority="registrar.example">
             AUTO-LOCK
           </subStatus>
         </transfer>
         <redemptionPeriod
           actor="registry"
           disposition="pending">
           <subStatus
             authority="policy-body.example">
             STANDARD RGP
           </subStatus>
         </redemptionPeriod>
       </status>

<アップデート俳優=「記録係」気質=、「禁止、「「regr.example「>AUTO-LOCK</subStatus></アップデート><転送俳優=」記録係」><subStatus権威=気質=、「禁止、「><subStatus権威が等しい、「registrar.example">"; AUTO-LOCK subStatus></転送><redemptionPeriod俳優=</「登録」気質=、「未定の「><subStatus権威=」方針-body.example「>STANDARD RGP</subStatus></redemptionPeriod></状態>」

     </enum>

</enum>。

   The <enum> result represents an instance of an ENUM domain
   assignment.  The children of the <enum> element are as follows:

<enum>結果はENUMドメイン課題のインスタンスを表します。 <enum>要素の子供は以下の通りです:

   o  <e164Number> - the E.164 number for this ENUM domain as defined by
      [13].  It is RECOMMENDED that only space characters be used
      between the digits of these E.164 numbers, as of the international
      number format defined in [14].

o <e164Number>--[13]によって定義されるこのENUMドメインのE.164番号。間隔文字だけがこれらのE.164番号のケタの間で使用されるのは、RECOMMENDEDです、[14]で定義された国際的な数の書式現在。

   o  <enumHandle> - a registry-unique assigned identifier to an ENUM
      domain.

o <enumHandle>--ENUMドメインへの登録ユニークな割り当てられた識別子。

   o  <nameServer> - MUST contain an entity reference to a referent of
      type <host> (Section 3.2.4).

o <nameServer>--タイプ<ホスト>(セクション3.2.4)の指示物の実体参照を含まなければなりません。

   o  <registrant> - elements containing an entity reference to the
      registrant of this ENUM domain.  The referent MUST be a <contact>
      (Section 3.2.5) result.

o <記入者>--このENUMドメインの記入者の実体参照を含む要素。指示物は<接触>(セクション3.2.5)結果であるに違いありません。

   o  ENUM domain contacts - see Section 3.2.2.

o ENUMドメイン接触--セクション3.2.2を見てください。

Newton                      Standards Track                     [Page 9]

RFC 4414              ENUM Registry Type for IRIS          February 2006

ニュートンStandardsは虹彩2006年2月にRFC4414ENUM登録タイプを追跡します[9ページ]。

   o  <status> - may contain at least one of the following elements of
      type 'enumStatusType' (see Section 3.2.1).

o <状態>--少なくともタイプ'enumStatusType'の以下の要素の1つを含むかもしれません(セクション3.2.1を見てください)。

      *  <reserved> - this ENUM domain falls outside the normal
         registration rules and/or processes for registration

* <は>を予約しました--このENUMドメインは登録のための正常な登録規則、そして/または、プロセスをそらせます。

      *  <create> - assigned to a registrant

* <は>を作成します--記入者に割り当てられます。

      *  <active> - available via DNS (either via delegation or direct
         publication)

* DNSを通して利用可能な<アクティブな>。(委譲かダイレクト公表を通した)

      *  <inactive> - unavailable via DNS

* DNSを通して入手できない<不活発な>。

      *  <dispute> - registrant assignment is in dispute

* <論争>--記入者課題は論争中です。

      *  <delete> - registrant assignment removed

* <は>を削除します--記入者課題は取り外されました。

      *  <transfer> - change of authority

* <転送>--権威の変化

      *  <update> - modification of this ENUM domain

* <アップデート>--このENUMドメインの変更

      *  <renew> - renewal of ENUM domain registration

* <は>を取り替えます--、ENUMドメインの取得の更新

      *  <addPeriod> - period at the creation or activation of this ENUM
         domain (see RFC 3915 [18])

* <addPeriod>--このENUMドメインの作成か起動のときに以上(RFC3915[18])を見てください。

      *  <renewPeriod> - period at the renewal of this ENUM domain (see
         RFC 3915 [18])

* <renewPeriod>--このENUMドメインの再開発のときに以上(RFC3915[18])を見てください。

      *  <autoRenewPeriod> - period at the automatic renewal of this
         ENUM domain (see RFC 3915 [18])

* <autoRenewPeriod>--このENUMドメインの自動更新のときに以上(RFC3915[18])を見てください。

      *  <transferPeriod> - period at the transfer of this ENUM domain
         (see RFC 3915 [18])

* <transferPeriod>--このENUMドメインの転送のときに以上(RFC3915[18])を見てください。

      *  <redemptionPeriod> - period at the redemption of this ENUM
         domain (see RFC 3915 [18])

* <redemptionPeriod>--このENUMドメインの償却のときに以上(RFC3915[18])を見てください。

      *  <restore> - change to previous status of this ENUM domain

* <は>を返します--このENUMドメインの前の状態に変化してください。

      *  <other> - a status only defined by its <subStatus> child
         element

* <他の>--<subStatus>子供要素によって定義されただけである状態

      As stated in Section 3.2.1, each status value may have flags to
      indicate the entity responsible for assigning the status (e.g.,
      actor='registrar') and the nature of the status (e.g.,
      disposition="prohibited").  Any one status value MUST NOT imply
      other status values.  For instance, <reserved> is just an

セクション3.2.1で述べられているように、各状態値で実体を示す旗は状態(例えば、俳優='記録係')と状態の本質(例えば=が「禁止した」気質)を割り当てるのに責任があるようになるかもしれません。どんな状態値も他の状態値を含意してはいけません。例えば、<の予約された>は正当です。

Newton                      Standards Track                    [Page 10]

RFC 4414              ENUM Registry Type for IRIS          February 2006

ニュートンStandardsは虹彩2006年2月にRFC4414ENUM登録タイプを追跡します[10ページ]。

      indication that the ENUM domain is given special reserved
      status; the <create disposition="prohibited"/> status value must
      also be present to indicate that the ENUM domain cannot be
      registered.

ENUMドメインに特別番組を与えるという指示は状態を予約しました。 <は「禁止」/>状態値が作成しなければならない気質=を作成します、また、ENUMドメインを登録できないのを示すには、存在してください。

   o  <registrationReference> - an element containing an entity
      reference, the referent of which MUST be an <enum>
      (Section 3.2.3).  The intention of this element is to point to the
      downstream registration reference.  Therefore, if this is a result
      given back by an ENUM domain registry, it should point to the ENUM
      domain in the ENUM domain registrar or registrant service.

o <registrationReference>--実体参照、指示物を含むそれの要素が<enum>であるに違いない(セクション3.2.3)。この要素の意志は川下の登録参照を示すことです。したがって、これがENUMドメイン登録によって返された結果であるなら、それはENUMドメインレジストラか記入者サービスにおけるENUMドメインを示すべきです。

   o  <registry> - contains an entity reference specifying the ENUM
      domain registry operator for this ENUM domain that MUST be a
      <registrationAuthority> (Section 3.2.6).

o <登録>--<registrationAuthority>であるに違いない(セクション3.2.6)このENUMドメインにENUMドメイン登録オペレータを指定する実体参照を含んでいます。

   o  <registrar> - contains an entity reference specifying the ENUM
      domain registrar operator for this ENUM domain that MUST be a
      <registrationAuthority> (Section 3.2.6).

o <記録係>--<registrationAuthority>であるに違いない(セクション3.2.6)このENUMドメインにENUMドメインレジストラのオペレータを指定する実体参照を含んでいます。

   o  <validationEntity> - contains an entity reference specifying the
      validation entity for this ENUM domain that MUST be a
      <validationEntity> (Section 3.2.7).

o <validationEntity>--<validationEntity>であるに違いない(セクション3.2.7)このENUMドメインに合法化実体を指定する実体参照を含んでいます。

   o  communication service providers - the following elements contain
      an entity reference with a relationship to the ENUM domain.  The
      referent of each MUST be a <communicationServiceProvider>
      (Section 3.2.8).

o コミュニケーションサービスプロバイダー--以下の要素はENUMドメインとの関係がある実体参照を含んでいます。それぞれの指示物は<communicationServiceProvider>であるに違いありません(セクション3.2.8)。

      *  <lineCSP>

* <lineCSP>。

      *  <signalCSP>

* <signalCSP>。

      *  <dataCSP>

* <dataCSP>。

      *  <voiceCSP>

* <voiceCSP>。

      *  <otherCSP>

* <otherCSP>。

   o  <validationEvent> -- elements containing an entity reference to
      validation events related to this ENUM domain.  The referent MUST
      be a <validationEvent> (Section 3.2.9).

o <validationEvent>--合法化イベントの実体参照を含む要素がこのENUMドメインに関連しました。指示物は<validationEvent>であるに違いありません(セクション3.2.9)。

   o  <initialDelegationDateTime> - an element containing the date and
      time of the initial delegation of this ENUM domain.

o <initialDelegationDateTime>--このENUMドメインの初期の委譲の日時を含む要素。

   o  <lastRenewalDateTime> - an element containing the date and time of
      last renewal of this ENUM domain.

o <lastRenewalDateTime>--このENUMドメインの最後の再開発の日時を含む要素。

Newton                      Standards Track                    [Page 11]

RFC 4414              ENUM Registry Type for IRIS          February 2006

ニュートンStandardsは虹彩2006年2月にRFC4414ENUM登録タイプを追跡します[11ページ]。

   o  <expirationDateTime> - an element containing the date and time of
      the expiration of this ENUM domain.

o <expirationDateTime>--このENUMドメインの満了の日時を含む要素。

   o  <lastContactModificationDateTime> - specifies the last time a
      contact for the ENUM domain was added or removed.

o <lastContactModificationDateTime>--前回ENUMドメインに関する接触を加えたか、または取り除いたとき、指定します。

   o  <lastContactModificationBy> - an element containing an entity
      reference.  The referent MUST be a <contact> (Section 3.2.5)
      responsible for the last addition or removal of a contact for this
      ENUM domain.

o <lastContactModificationBy>--実体参照を含む要素。指示物はこのENUMドメインに関する接触の最後の追加か取り外しに責任がある<接触>であるに違いありません(セクション3.2.5)。

   o  <lastDelegationModificationDateTime> - an element containing the
      date and time of the last time one of the nameservers was added or
      removed for the delegation of this ENUM domain.

o <lastDelegationModificationDateTime>--このENUMドメインの委譲のためにネームサーバの最後の現代1の日時を含む要素を、加えたか、または取り除きました。

   o  <lastDelegationModificationBy> - an element containing an entity
      reference.  The referent MUST be a <contact> (Section 3.2.5)
      result and be responsible for the last addition or removal of a
      nameserver for this ENUM domain.

o <lastDelegationModificationBy>--実体参照を含む要素。指示物は、<接触>(セクション3.2.5)結果であり、このENUMドメインにおいて、ネームサーバの最後の追加か取り外しに原因となるに違いありません。

   o  <lastVerificationDateTime> - an element containing the date and
      time of the last time the data for this domain was verified by the
      responsible registration authority.

o <lastVerificationDateTime>--最後の現代の日時にこのドメインのためのデータを含む要素は責任がある登録局によって確かめられました。

   o  <iris:seeAlso> - an element containing an entity reference
      specifying a referent that is indirectly associated with this
      domain.

o <iris:seeAlso> - an element containing an entity reference specifying a referent that is indirectly associated with this domain.

3.2.4.  <host> Result

3.2.4. <host> Result

   An example of a <host> result:

An example of a <host> result:

   <host
     authority="iana.org" registryType="ereg1"
     entityClass="host-handle" entityName="nsol184" >
     <hostHandle>nsol184</hostHandle>
     <hostName>a.iana-servers.net</hostName>
     <ipV4Address>192.0.2.43</ipV4Address>
     <hostContact
       iris:referentType="ereg:contact"
       authority="iana.org" registryType="ereg1"
       entityClass="contact-handle" entityName="dbarton" />
   </host>

<host authority="iana.org" registryType="ereg1" entityClass="host-handle" entityName="nsol184" > <hostHandle>nsol184</hostHandle> <hostName>a.iana-servers.net</hostName> <ipV4Address>192.0.2.43</ipV4Address> <hostContact iris:referentType="ereg:contact" authority="iana.org" registryType="ereg1" entityClass="contact-handle" entityName="dbarton" /> </host>

   The <host> element represents an instance of a host registration.
   The children of the <host> element are as follows:

The <host> element represents an instance of a host registration. The children of the <host> element are as follows:

   o  <hostHandle> - a registry-unique assigned identifier for the host.

o <hostHandle> - a registry-unique assigned identifier for the host.

Newton                      Standards Track                    [Page 12]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 12] RFC 4414 ENUM Registry Type for IRIS February 2006

   o  <hostName> - the fully qualified domain name of the host.  The
      contents of this element are a host name and MUST conform to RFC
      1123 [19].

o <hostName> - the fully qualified domain name of the host. The contents of this element are a host name and MUST conform to RFC 1123 [19].

   o  <ipV4Address> - the content of which MUST conform to a valid
      IP version 4 host address as specified by RFC 791 [8].

o <ipV4Address> - the content of which MUST conform to a valid IP version 4 host address as specified by RFC 791 [8].

   o  <ipV6Address> - the content of which MUST conform to a valid
      IP version 6 host address as specified by RFC 3513 [7].

o <ipV6Address> - the content of which MUST conform to a valid IP version 6 host address as specified by RFC 3513 [7].

   o  <hostContact> - an element containing an entity reference
      specifying a contact associated with this host.  The referent MUST
      be <contact> (Section 3.2.5) results.

o <hostContact> - an element containing an entity reference specifying a contact associated with this host. The referent MUST be <contact> (Section 3.2.5) results.

   o  <createdDateTime> - an element containing the date and time this
      host was created.

o <createdDateTime> - an element containing the date and time this host was created.

   o  <lastModificationDateTime> - an element containing the date and
      time this host was last modified.

o <lastModificationDateTime> - an element containing the date and time this host was last modified.

   o  <lastVerificationDateTime> - an element containing the date and
      time this data for this host was last verified to be correct by
      the appropriate registration authority.

o <lastVerificationDateTime> - an element containing the date and time this data for this host was last verified to be correct by the appropriate registration authority.

   o  <iris:seeAlso> - an element containing an entity reference
      specifying a referent that is indirectly associated with this
      host.

o <iris:seeAlso> - an element containing an entity reference specifying a referent that is indirectly associated with this host.

3.2.5.  <contact> Result

3.2.5. <contact> Result

   An example of a <contact> result:

An example of a <contact> result:

   <contact
     authority="example.org" registryType="ereg1"
     entityClass="contact-handle" entityName="example-admin" >
     <contactHandle>example-admin</contactHandle>
     <commonName>Example.Org Manager</commonName>
     <organization>Internet Assigned Numbers Authority</organization>
     <eMail>res-dom@example.org</eMail>
     <postalAddress>
       <address>123 Mocking Bird Lane</address>
       <city>Some City</city>
       <region>CA</region>
       <postalCode>00000</postalCode>
       <country>US</country>
     </postalAddress>
     <phone>+1234567890</phone>
   </contact>

<contact authority="example.org" registryType="ereg1" entityClass="contact-handle" entityName="example-admin" > <contactHandle>example-admin</contactHandle> <commonName>Example.Org Manager</commonName> <organization>Internet Assigned Numbers Authority</organization> <eMail>res-dom@example.org</eMail> <postalAddress> <address>123 Mocking Bird Lane</address> <city>Some City</city> <region>CA</region> <postalCode>00000</postalCode> <country>US</country> </postalAddress> <phone>+1234567890</phone> </contact>

Newton                      Standards Track                    [Page 13]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 13] RFC 4414 ENUM Registry Type for IRIS February 2006

   The <contact> element represents an instance of a contact
   registration.  The children of the <contact> element are as follows:

The <contact> element represents an instance of a contact registration. The children of the <contact> element are as follows:

   o  <contactHandle> - a registry-unique assigned identifier for this
      contact.

o <contactHandle> - a registry-unique assigned identifier for this contact.

   o  <commonName> - the name of the contact.

o <commonName> - the name of the contact.

   o  <language> - a specification of the language code to use to
      localize the data in this result.

o <language> - a specification of the language code to use to localize the data in this result.

   o  <type> - contains one of the following child elements: <person>,
      <organization>, <role>, or <other>.  Each of these elements is a
      "contactTypeType" as defined in Section 3.2.1.

o <type> - contains one of the following child elements: <person>, <organization>, <role>, or <other>. Each of these elements is a "contactTypeType" as defined in Section 3.2.1.

   o  <organization> - an element containing the organization name of
      the contact.

o <organization> - an element containing the organization name of the contact.

   o  The <legalId> child element contains a jurisdictional identifier
      of this contact (an example of such an identifier is a national
      taxation ID or a commercial registry number).

o The <legalId> child element contains a jurisdictional identifier of this contact (an example of such an identifier is a national taxation ID or a commercial registry number).

   o  <eMail> - elements containing an e-mail address for this contact.

o <eMail> - elements containing an e-mail address for this contact.

   o  <sip> - elements containing a SIP URI for this contact.

o <sip> - elements containing a SIP URI for this contact.

   o  <postalAddress> - elements containing children representing a
      postal address. <postalAddress> has the following children:

o <postalAddress> - elements containing children representing a postal address. <postalAddress> has the following children:

      *  <address> - an element containing the street address for this
         contact.

* <address> - an element containing the street address for this contact.

      *  <city> - an element containing the city for this contact.

* <city> - an element containing the city for this contact.

      *  <region> - an element containing the national region for this
         contact.

* <region> - an element containing the national region for this contact.

      *  <postalCode> - an element containing the postal code for this
         contact.

* <postalCode> - an element containing the postal code for this contact.

      *  <country> - an element containing the country for this contact.
         This SHOULD be a 2-letter country code compliant with ISO 3166
         [11].

* <country> - an element containing the country for this contact. This SHOULD be a 2-letter country code compliant with ISO 3166 [11].

   o  <phone> - elements containing a voice phone number for this
      contact.  If it begins with a '+' (plus) character, it MUST be a
      number defined by E.164 [13].  The format number defined in E.164
      [13] is RECOMMENDED.

o <phone> - elements containing a voice phone number for this contact. If it begins with a '+' (plus) character, it MUST be a number defined by E.164 [13]. The format number defined in E.164 [13] is RECOMMENDED.

Newton                      Standards Track                    [Page 14]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 14] RFC 4414 ENUM Registry Type for IRIS February 2006

   o  <fax> - elements containing a facsimile phone number for this
      contact.  If it begins with a '+' (plus) character, it MUST be a
      number defined by E.164 [13].  The format number defined in E.164
      [13] is RECOMMENDED.

o <fax> - elements containing a facsimile phone number for this contact. If it begins with a '+' (plus) character, it MUST be a number defined by E.164 [13]. The format number defined in E.164 [13] is RECOMMENDED.

   o  <createdDateTime> - an element containing the date and time this
      contact was created.

o <createdDateTime> - an element containing the date and time this contact was created.

   o  <lastModificationDateTime> - an element containing the date and
      time this contact was last modified.

o <lastModificationDateTime> - an element containing the date and time this contact was last modified.

   o  <lastVerificationDateTime> - an element containing the date and
      time this data for this contact was last verified to be correct by
      the appropriate registration authority.

o <lastVerificationDateTime> - an element containing the date and time this data for this contact was last verified to be correct by the appropriate registration authority.

   o  <translatedContacts> - an element containing an entity reference
      specifying equivalents of this contact that have been translated
      into other languages.  The referent MUST be <contact>
      (Section 3.2.5) results.

o <translatedContacts> - an element containing an entity reference specifying equivalents of this contact that have been translated into other languages. The referent MUST be <contact> (Section 3.2.5) results.

   o  <iris:seeAlso> - an element containing an entity reference
      specifying a referent that is indirectly associated with this
      contact.

o <iris:seeAlso> - an element containing an entity reference specifying a referent that is indirectly associated with this contact.

3.2.6.  <registrationAuthority> Result

3.2.6. <registrationAuthority> Result

   An example of a <registrationAuthority> result:

An example of a <registrationAuthority> result:

   <registrationAuthority
     authority="iana.org" registryType="ereg1"
     entityClass="registration-authority" entityName="iana" >
     <serviceInstance
       iris:referentType="iris:serviceIdentification"
       authority="iana.org" registryType="ereg1"
       entityClass="iris" entityName="id" />
     <organizationName>
       Internet Assigned Numbers Authority
     </organizationName>
     <registrar />
   </registrationAuthority>

<registrationAuthority authority="iana.org" registryType="ereg1" entityClass="registration-authority" entityName="iana" > <serviceInstance iris:referentType="iris:serviceIdentification" authority="iana.org" registryType="ereg1" entityClass="iris" entityName="id" /> <organizationName> Internet Assigned Numbers Authority </organizationName> <registrar /> </registrationAuthority>

   The <registrationAuthority> result represents an entity capable of
   registering domains.

The <registrationAuthority> result represents an entity capable of registering domains.

   The <serviceInstance> child element of <registrationAuthority>
   contains an entity reference pointing to the entity "id" in the
   entity class "iris".

The <serviceInstance> child element of <registrationAuthority> contains an entity reference pointing to the entity "id" in the entity class "iris".

Newton                      Standards Track                    [Page 15]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 15] RFC 4414 ENUM Registry Type for IRIS February 2006

   The <organizationName> child element contains the name of the
   registration authority.

The <organizationName> child element contains the name of the registration authority.

   The <legalId> child element contains an identifier of this
   registration authority (an example of such an identifier is a
   national taxation ID or a commercial registry number).

The <legalId> child element contains an identifier of this registration authority (an example of such an identifier is a national taxation ID or a commercial registry number).

   The registration authority type child elements, <registry>,
   <registrar>, and <other>, determine the role in which this
   registration authority plays in the process of registering ENUM
   domains.  The intent of this element is to explain the various roles
   a registration authority may have with regards to the authority areas
   pointed to by the <serviceInstance> element.  A client MAY understand
   the relationship of a registration authority with respect to an ENUM
   domain by the placement of the reference in the domain (e.g.,
   <registry> or <registrar>).

The registration authority type child elements, <registry>, <registrar>, and <other>, determine the role in which this registration authority plays in the process of registering ENUM domains. The intent of this element is to explain the various roles a registration authority may have with regards to the authority areas pointed to by the <serviceInstance> element. A client MAY understand the relationship of a registration authority with respect to an ENUM domain by the placement of the reference in the domain (e.g., <registry> or <registrar>).

   contacts - see Section 3.2.2.

contacts - see Section 3.2.2.

   <iris:seeAlso> - an element containing an entity reference specifying
   a referent that is indirectly associated with this registration
   authority.

<iris:seeAlso> - an element containing an entity reference specifying a referent that is indirectly associated with this registration authority.

3.2.7.  <validationEntity> Result

3.2.7. <validationEntity> Result

   An example of a <validationEntity> result:

An example of a <validationEntity> result:

   <validationEntity
     authority="example.org" registryType="ereg1"
     entityClass="validation-entity" entityName="govt" >
     <serviceInstance
       iris:referentType="iris:serviceIdentification"
       authority="example.org" registryType="ereg1"
       entityClass="iris" entityName="id" />
     <organizationName>
       Some Government Authority
     </organizationName>
     <technicalContact
       iris:referentType="iris:contact"
       authority="example.org" registryType="ereg1"
       entityClass="contact-handle" entityName="1234" />
     <administrativeContact
       iris:referentType="iris:contact"
       authority="example.org" registryType="ereg1"
       entityClass="contact-handle" entityName="abc" />
   </validationEntity>

<validationEntity authority="example.org" registryType="ereg1" entityClass="validation-entity" entityName="govt" > <serviceInstance iris:referentType="iris:serviceIdentification" authority="example.org" registryType="ereg1" entityClass="iris" entityName="id" /> <organizationName> Some Government Authority </organizationName> <technicalContact iris:referentType="iris:contact" authority="example.org" registryType="ereg1" entityClass="contact-handle" entityName="1234" /> <administrativeContact iris:referentType="iris:contact" authority="example.org" registryType="ereg1" entityClass="contact-handle" entityName="abc" /> </validationEntity>

Newton                      Standards Track                    [Page 16]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 16] RFC 4414 ENUM Registry Type for IRIS February 2006

   The <validationEntity> result represents an entity responsible for
   validating ENUM domains against E.164 [13] registrations.

The <validationEntity> result represents an entity responsible for validating ENUM domains against E.164 [13] registrations.

   The <serviceInstance> child element of <validationEntity> contains an
   entity reference pointing to the entity "id" in the entity class
   "iris".

The <serviceInstance> child element of <validationEntity> contains an entity reference pointing to the entity "id" in the entity class "iris".

   The <organizationName> child element contains the name of the
   validation authority.

The <organizationName> child element contains the name of the validation authority.

   The <legalId> child element contains an identifier of this validation
   authority (an example of such an identifier is a national taxation ID
   or a commercial registry number).

The <legalId> child element contains an identifier of this validation authority (an example of such an identifier is a national taxation ID or a commercial registry number).

   contacts - see Section 3.2.2.

contacts - see Section 3.2.2.

   <iris:seeAlso> - an element containing an entity reference specifying
   a referent that is indirectly associated with this validation
   authority.

<iris:seeAlso> - an element containing an entity reference specifying a referent that is indirectly associated with this validation authority.

3.2.8.  <communicationServiceProvider> Result

3.2.8. <communicationServiceProvider> Result

   An example of a <communicationServiceProvider> result:

An example of a <communicationServiceProvider> result:

   <communicationServiceProvider
     authority="bell.example.com" registryType="ereg1"
     entityClass="csp" entityName="bellco" >
     <serviceInstance
       iris:referentType="iris:serviceIdentification"
       authority="bell.example.com" registryType="ereg1"
       entityClass="iris" entityName="id" />
     <organizationName>
       Big Phone Co.
     </organizationName>
     <line />
   </communicationServiceProvider>

<communicationServiceProvider authority="bell.example.com" registryType="ereg1" entityClass="csp" entityName="bellco" > <serviceInstance iris:referentType="iris:serviceIdentification" authority="bell.example.com" registryType="ereg1" entityClass="iris" entityName="id" /> <organizationName> Big Phone Co. </organizationName> <line /> </communicationServiceProvider>

   The <communicationServiceProvider> result represents an entity
   providing ENUM domain service.

The <communicationServiceProvider> result represents an entity providing ENUM domain service.

   The <serviceInstance> child element of <communicationServiceProvider>
   contains an entity reference pointing to the entity "id" in the
   entity class "iris".

The <serviceInstance> child element of <communicationServiceProvider> contains an entity reference pointing to the entity "id" in the entity class "iris".

   The <organizationName> child element contains the name of the
   registration authority.

The <organizationName> child element contains the name of the registration authority.

Newton                      Standards Track                    [Page 17]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 17] RFC 4414 ENUM Registry Type for IRIS February 2006

   The <legalId> child element contains an identifier of this
   communication service provider (an example of such an identifier is a
   national taxation ID or a commercial registry number).

The <legalId> child element contains an identifier of this communication service provider (an example of such an identifier is a national taxation ID or a commercial registry number).

   The <cspId> child element contains an identifier unique to this
   communication service provider and identifies this communication
   service provider with regard to its operating jurisdiction.

The <cspId> child element contains an identifier unique to this communication service provider and identifies this communication service provider with regard to its operating jurisdiction.

   The child elements, <line>, <signal>, <data>, <voice>, and <other>,
   detail the capabilities of this communication service provider.  The
   capabilities this communication service provider provides to a
   specific ENUM domain are a subset of these capabilities and are
   expressed in the <enum> result using the <lineCSP>, <signalCSP>,
   <dataCSP>, <voiceCSP>, and <otherCSP> entity references.

The child elements, <line>, <signal>, <data>, <voice>, and <other>, detail the capabilities of this communication service provider. The capabilities this communication service provider provides to a specific ENUM domain are a subset of these capabilities and are expressed in the <enum> result using the <lineCSP>, <signalCSP>, <dataCSP>, <voiceCSP>, and <otherCSP> entity references.

   contacts - see Section 3.2.2.

contacts - see Section 3.2.2.

   <iris:seeAlso> - an element containing an entity reference specifying
   a referent that is indirectly associated with this communication
   service provider.

<iris:seeAlso> - an element containing an entity reference specifying a referent that is indirectly associated with this communication service provider.

3.2.9.  <validationEvent> Result

3.2.9. <validationEvent> Result

   An example of a <validationEvent> result:

An example of a <validationEvent> result:

   <validationEvent
     authority="example.com" registryType="ereg1"
     entityClass="validation-event" entityName="xyz-0123" >
     <serial>xyz-0123</serial>
     <validationEntity
       iris:referentType="ereg:validationEntity"
       authority="bell.example.com" registryType="ereg1"
       entityClass="iris" entityName="id" />
   </validationEvent>

   The <validationEvent> result represents a record of validation for an
   ENUM domain.

The <validationEvent> result represents a record of validation for an ENUM domain.

   The <serial> child element contains an identifier identifying this
   validation event between a validation entity and a registrar.

The <serial> child element contains an identifier identifying this validation event between a validation entity and a registrar.

   The <methodId> child element contains an identifier describing the
   method used for validation.

The <methodId> child element contains an identifier describing the method used for validation.

   <registrar> - contains an entity reference specifying the ENUM domain
   registrar operator for this validation event that MUST be a
   <registrationAuthority> (Section 3.2.6).

<registrar> - contains an entity reference specifying the ENUM domain registrar operator for this validation event that MUST be a <registrationAuthority> (Section 3.2.6).

Newton                      Standards Track                    [Page 18]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 18] RFC 4414 ENUM Registry Type for IRIS February 2006

   <validationEntity> - contains an entity reference specifying the
   validation entity for this validation event that MUST be a
   <validationEntity> (Section 3.2.7).

<validationEntity> - contains an entity reference specifying the validation entity for this validation event that MUST be a <validationEntity> (Section 3.2.7).

   <executionDateTime> - an element containing the date and time of the
   creation of this validation event.

<executionDateTime> - an element containing the date and time of the creation of this validation event.

   <expirationDateTime> - an element containing the date and time of the
   expiration of this validation event.

<expirationDateTime> - an element containing the date and time of the expiration of this validation event.

   <iris:seeAlso> - an element containing an entity reference specifying
   a referent that is indirectly associated with this validation event.

<iris:seeAlso> - an element containing an entity reference specifying a referent that is indirectly associated with this validation event.

3.3.  Generic Code Derivatives

3.3. Generic Code Derivatives

3.3.1.  <searchTooWide>

3.3.1. <searchTooWide>

   Servers MAY use the <searchTooWide> error code when a query must be
   narrowed to yield a result set acceptable to the policies of the
   server operator.

Servers MAY use the <searchTooWide> error code when a query must be narrowed to yield a result set acceptable to the policies of the server operator.

3.3.2.  <languageNotSupported>

3.3.2. <languageNotSupported>

   The queries <findEnumsByContact> and <findContacts> support optional
   language tags that allow a client to suggest to a server the
   languages in which to scope the queries.  If a client passes to the
   server a language that the server does not support, the server MAY
   use this error code to indicate that one of the languages is not
   supported.

The queries <findEnumsByContact> and <findContacts> support optional language tags that allow a client to suggest to a server the languages in which to scope the queries. If a client passes to the server a language that the server does not support, the server MAY use this error code to indicate that one of the languages is not supported.

   This element contains child elements named <unsupportedLanguage>.
   Each of these child elements specifies a language not supported by
   the server.  When a server returns this error, it MUST give the
   languages from the query that are not supported.

This element contains child elements named <unsupportedLanguage>. Each of these child elements specifies a language not supported by the server. When a server returns this error, it MUST give the languages from the query that are not supported.

3.4.  Support for <iris:lookupEntity>

3.4. Support for <iris:lookupEntity>

   The following types of entity classes are recognized by the
   <lookupEntity> query of IRIS for this registry:

The following types of entity classes are recognized by the <lookupEntity> query of IRIS for this registry:

   o  host-name - the fully qualified domain name of a nameserver.  It
      yields a <host> (Section 3.2.4) in the response.

o host-name - the fully qualified domain name of a nameserver. It yields a <host> (Section 3.2.4) in the response.

   o  host-handle - the registry-unique identifier given a nameserver.
      It yields a <host> (Section 3.2.4) in the response.

o host-handle - the registry-unique identifier given a nameserver. It yields a <host> (Section 3.2.4) in the response.

Newton                      Standards Track                    [Page 19]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 19] RFC 4414 ENUM Registry Type for IRIS February 2006

   o  e164 - an E.164 number as specified by [13].  It yields an <enum>
      (Section 3.2.3) in the response.  Clients SHOULD remove all non-
      digit characters between the digits of an E.164 number, and
      servers MUST ignore any non-digit characters between the digits of
      an E.164 number (e.g., "+1 703 555 1234" is to be interpreted as
      "+17035551234").

o e164 - an E.164 number as specified by [13]. It yields an <enum> (Section 3.2.3) in the response. Clients SHOULD remove all non- digit characters between the digits of an E.164 number, and servers MUST ignore any non-digit characters between the digits of an E.164 number (e.g., "+1 703 555 1234" is to be interpreted as "+17035551234").

   o  enum - the fully qualified name of an ENUM domain.  This is a
      domain name as specified by RFC 3761 [17].  It yields an <enum>
      (Section 3.2.3) in the response.

o enum - the fully qualified name of an ENUM domain. This is a domain name as specified by RFC 3761 [17]. It yields an <enum> (Section 3.2.3) in the response.

   o  enum-handle - the registry-unique identifier given an ENUM domain.
      It yields an <enum> (Section 3.2.3) in the response.

o enum-handle - the registry-unique identifier given an ENUM domain. It yields an <enum> (Section 3.2.3) in the response.

   o  contact-handle - the registry-unique identifier given a contact.
      It yields a <contact> (Section 3.2.5) in the response.

o contact-handle - the registry-unique identifier given a contact. It yields a <contact> (Section 3.2.5) in the response.

   o  ipv4-address - the IPv4 address of a nameserver.  It yields a
      <host> (Section 3.2.4) in the response.

o ipv4-address - the IPv4 address of a nameserver. It yields a <host> (Section 3.2.4) in the response.

   o  ipv6-address - the IPv6 address of a nameserver.  It yields a
      <host> (Section 3.2.4) in the response.

o ipv6-address - the IPv6 address of a nameserver. It yields a <host> (Section 3.2.4) in the response.

   o  registration-authority - the name of a registration authority.  It
      yields a <registrationAuthority> (Section 3.2.6) in the response.

o registration-authority - the name of a registration authority. It yields a <registrationAuthority> (Section 3.2.6) in the response.

   o  validation-entity - the name of a validation entity.  It yields a
      <validationEntity> (Section 3.2.7)

o validation-entity - the name of a validation entity. It yields a <validationEntity> (Section 3.2.7)

   o  csp - the identifier of a communication service provider.  Yields
      a <communicationServiceProvider> (Section 3.2.8).

o csp - the identifier of a communication service provider. Yields a <communicationServiceProvider> (Section 3.2.8).

   o  validation-event - the identifier for a validation event.  It
      yields a <validationEvent> (Section 3.2.9).

o validation-event - the identifier for a validation event. It yields a <validationEvent> (Section 3.2.9).

   o  All names in these entity classes are case insensitive.

o All names in these entity classes are case insensitive.

Newton                      Standards Track                    [Page 20]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 20] RFC 4414 ENUM Registry Type for IRIS February 2006

4.  Formal XML Syntax

4. Formal XML Syntax

   This registry schema is specified in the XML Schema notation.  The
   formal syntax presented here is a complete schema representation
   suitable for automated validation of an XML instance when combined
   with the formal schema syntax of IRIS.

This registry schema is specified in the XML Schema notation. The formal syntax presented here is a complete schema representation suitable for automated validation of an XML instance when combined with the formal schema syntax of IRIS.

   <?xml version="1.0"?>
   <schema xmlns="http://www.w3.org/2001/XMLSchema"
     xmlns:ereg="urn:ietf:params:xml:ns:ereg1"
     xmlns:iris="urn:ietf:params:xml:ns:iris1"
     targetNamespace="urn:ietf:params:xml:ns:ereg1"
     elementFormDefault="qualified" >

<?xml version="1.0"?> <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:ereg="urn:ietf:params:xml:ns:ereg1" xmlns:iris="urn:ietf:params:xml:ns:iris1" targetNamespace="urn:ietf:params:xml:ns:ereg1" elementFormDefault="qualified" >

     <import namespace="urn:ietf:params:xml:ns:iris1" />

     <annotation>
       <documentation>
         ENUM registry schema
         derived from IRIS schema
       </documentation>
     </annotation>

<annotation> <documentation> ENUM registry schema derived from IRIS schema </documentation> </annotation>

     <!-- ========================================= -->
     <!--                                           -->
     <!-- Query Types                               -->
     <!--                                           -->
     <!-- ========================================= -->

     <!--                                           -->
     <!-- Find ENUMs by E.164                       -->
     <!--                                           -->

     <complexType
       name="findEnumsByE164Type">
       <complexContent>
         <extension
           base="iris:queryType">
           <sequence>
             <element
               name="e164Prefix"
               type="token" />
             <element
               name="specificity"
               minOccurs="0" >
               <simpleType>
                 <restriction
                   base="string">

Newton                      Standards Track                    [Page 21]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 21] RFC 4414 ENUM Registry Type for IRIS February 2006

                   <enumeration
                     value="less"/>
                   <enumeration
                     value="more"/>
                 </restriction>
               </simpleType>
             </element>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

     <element
       name="findEnumsByE164"
       type="ereg:findEnumsByE164Type"
       substitutionGroup="iris:query" />

     <!--                                           -->
     <!-- Find ENUMs By Contact                     -->
     <!--                                           -->

     <complexType
       name="findEnumsByContactType">
       <complexContent>
         <extension
           base="iris:queryType">
           <sequence>
             <choice>
               <group
                 ref="ereg:contactSearchGroup" />
               <element
                 name="contactHandle"
                 type="ereg:exactMatchParameter" />
             </choice>
             <element
               name="role"
               minOccurs="0"
               maxOccurs="1" >
               <simpleType>
                 <restriction
                   base="string" >
                   <enumeration
                     value="registrant" />
                   <enumeration
                     value="billingContact" />
                   <enumeration
                     value="technicalContact" />
                   <enumeration

<complexType name="findEnumsByContactType"> <complexContent> <extension base="iris:queryType"> <sequence> <choice> <group ref="ereg:contactSearchGroup" /> <element name="contactHandle" type="ereg:exactMatchParameter" /> </choice> <element name="role" minOccurs="0" maxOccurs="1" > <simpleType> <restriction base="string" > <enumeration value="registrant" /> <enumeration value="billingContact" /> <enumeration value="technicalContact" /> <enumeration

Newton                      Standards Track                    [Page 22]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 22] RFC 4414 ENUM Registry Type for IRIS February 2006

                     value="administrativeContact" />
                   <enumeration
                     value="legalContact" />
                   <enumeration
                     value="zoneContact" />
                   <enumeration
                     value="abuseContact" />
                   <enumeration
                     value="securityContact" />
                   <enumeration
                     value="otherContact" />
                 </restriction>
               </simpleType>
             </element>
             <element
               name="language"
               type="language"
               minOccurs="0"
               maxOccurs="unbounded"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

value="administrativeContact" /> <enumeration value="legalContact" /> <enumeration value="zoneContact" /> <enumeration value="abuseContact" /> <enumeration value="securityContact" /> <enumeration value="otherContact" /> </restriction> </simpleType> </element> <element name="language" type="language" minOccurs="0" maxOccurs="unbounded"/> </sequence> </extension> </complexContent> </complexType>

     <element
       name="findEnumsByContact"
       type="ereg:findEnumsByContactType"
       substitutionGroup="iris:query" />

     <!--                                           -->
     <!-- Find Contacts                             -->
     <!--                                           -->

     <complexType
       name="findContactsType">
       <complexContent>
         <extension
           base="iris:queryType">
           <sequence>
             <group
               ref="ereg:contactSearchGroup" />
             <element
               name="language"
               type="language"
               minOccurs="0"
               maxOccurs="unbounded"/>
            </sequence>
         </extension>

Newton                      Standards Track                    [Page 23]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 23] RFC 4414 ENUM Registry Type for IRIS February 2006

       </complexContent>
     </complexType>

</complexContent> </complexType>

     <element
       name="findContacts"
       type="ereg:findContactsType"
       substitutionGroup="iris:query" />

     <!--                                           -->
     <!-- Find ENUMs By Host                        -->
     <!--                                           -->

     <complexType
       name="findEnumsByHostType">
       <complexContent>
         <extension
           base="iris:queryType">
           <sequence>
             <choice>
               <element
                 name="hostName"
                 type="ereg:exactMatchParameter" />
               <element
                 name="hostHandle"
                 type="ereg:exactMatchParameter" />
               <element
                 name="ipV4Address"
                 type="ereg:exactMatchParameter" />
               <element
                 name="ipV6Address"
                 type="ereg:exactMatchParameter" />
             </choice>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

     <element
       name="findEnumsByHost"
       type="ereg:findEnumsByHostType"
       substitutionGroup="iris:query" />

     <!--                                           -->
     <!-- Contact Search Group                      -->
     <!--                                           -->

     <group
       name="contactSearchGroup">

Newton                      Standards Track                    [Page 24]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 24] RFC 4414 ENUM Registry Type for IRIS February 2006

       <choice>
         <element
           name="commonName"
           type="ereg:exactOrPartialMatchParameter" />
         <element
           name="organization"
           type="ereg:exactOrPartialMatchParameter" />
         <element
           name="eMail"
           type="ereg:domainResourceParameter" />
         <element
           name="sip"
           type="ereg:domainResourceParameter" />
         <element
           name="city"
           type="ereg:exactMatchParameter" />
         <element
           name="region"
           type="ereg:exactMatchParameter" />
         <element
           name="postalCode"
           type="ereg:exactMatchParameter" />
       </choice>
     </group>

     <complexType
       name="exactOrPartialMatchParameter">
       <choice>
         <group
           ref="ereg:partialMatchGroup" />
         <group
           ref="ereg:exactMatchGroup" />
       </choice>
     </complexType>

     <complexType
       name="exactMatchParameter">
       <group
         ref="ereg:exactMatchGroup" />
     </complexType>

     <complexType
       name="partialMatchParameter">
       <sequence>
         <group
           ref="ereg:partialMatchGroup" />
       </sequence>
     </complexType>

Newton                      Standards Track                    [Page 25]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 25] RFC 4414 ENUM Registry Type for IRIS February 2006

     <complexType
       name="domainResourceParameter" >
       <choice>
         <group
           ref="ereg:exactMatchGroup" />
         <element
           name="inDomain"
           type="token" />
       </choice>
     </complexType>

     <group
       name="partialMatchGroup">
       <choice>
         <sequence>
           <element
             name="beginsWith">
             <simpleType>
               <restriction
                 base="token">
                 <minLength
                   value="1"/>
               </restriction>
             </simpleType>
           </element>
           <element
             minOccurs="0"
             name="endsWith"
             type="ereg:endsWithType" />
         </sequence>
         <element
           name="endsWith"
           type="ereg:endsWithType" />
       </choice>
     </group>

     <simpleType
       name="endsWithType">
       <restriction
         base="token">
         <minLength
           value="1" />
       </restriction>
     </simpleType>

     <group
       name="exactMatchGroup">
       <sequence>

Newton                      Standards Track                    [Page 26]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 26] RFC 4414 ENUM Registry Type for IRIS February 2006

         <element
           name="exactMatch"
           type="normalizedString" />
       </sequence>
     </group>

     <!-- ========================================= -->
     <!--                                           -->
     <!-- Result Types                              -->
     <!--                                           -->
     <!-- ========================================= -->

     <!--                                           -->
     <!-- ENUM                                      -->
     <!--                                           -->

     <complexType
       name="enumType">
       <complexContent>
         <extension
           base="iris:resultType">
           <sequence>
             <element
               name="e164Number"
               type="token" />
             <element
               name="enumHandle"
               type="ereg:normalizedStringPrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="nameServer"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               name="registrant"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="unbounded" />
             <group ref="ereg:contactGroup" />
             <element
               name="lastContactModificationDateTime"
               type="ereg:dateTimePrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="1" />

Newton                      Standards Track                    [Page 27]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 27] RFC 4414 ENUM Registry Type for IRIS February 2006

             <element
               name="lastContactModificationBy"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="status"
               minOccurs="0"
               maxOccurs="1">
               <complexType>
                 <choice
                   minOccurs="1"
                   maxOccurs="unbounded">
                   <element
                     name="reserved"
                     type="ereg:enumStatusType" />
                   <element
                     name="create"
                     type="ereg:enumStatusType" />
                   <element
                     name="active"
                     type="ereg:enumStatusType" />
                   <element
                     name="inactive"
                     type="ereg:enumStatusType" />
                   <element
                     name="dispute"
                     type="ereg:enumStatusType" />
                   <element
                     name="delete"
                     type="ereg:enumStatusType" />
                   <element
                     name="transfer"
                     type="ereg:enumStatusType" />
                   <element
                     name="renew"
                     type="ereg:enumStatusType" />
                   <element
                     name="update"
                     type="ereg:enumStatusType" />
                   <element
                     name="addPeriod"
                     type="ereg:enumStatusType" />
                   <element
                     name="renewPeriod"
                     type="ereg:enumStatusType" />
                   <element
                     name="autoRenewPeriod"

<element name="lastContactModificationBy" type="iris:entityType" minOccurs="0" maxOccurs="1" /> <element name="status" minOccurs="0" maxOccurs="1"> <complexType> <choice minOccurs="1" maxOccurs="unbounded"> <element name="reserved" type="ereg:enumStatusType" /> <element name="create" type="ereg:enumStatusType" /> <element name="active" type="ereg:enumStatusType" /> <element name="inactive" type="ereg:enumStatusType" /> <element name="dispute" type="ereg:enumStatusType" /> <element name="delete" type="ereg:enumStatusType" /> <element name="transfer" type="ereg:enumStatusType" /> <element name="renew" type="ereg:enumStatusType" /> <element name="update" type="ereg:enumStatusType" /> <element name="addPeriod" type="ereg:enumStatusType" /> <element name="renewPeriod" type="ereg:enumStatusType" /> <element name="autoRenewPeriod"

Newton                      Standards Track                    [Page 28]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 28] RFC 4414 ENUM Registry Type for IRIS February 2006

                     type="ereg:enumStatusType" />
                   <element
                     name="transferPeriod"
                     type="ereg:enumStatusType" />
                   <element
                     name="redemptionPeriod"
                     type="ereg:enumStatusType" />
                   <element
                     name="restore"
                     type="ereg:enumStatusType" />
                   <element
                     name="other"
                     type="ereg:enumStatusType" />
                 </choice>
               </complexType>
             </element>
             <element
               name="registrationReference"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="registry"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="registrar"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="validationEntity"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               name="signalCSP"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               name="dataCSP"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               name="lineCSP"

type="ereg:enumStatusType" /> <element name="transferPeriod" type="ereg:enumStatusType" /> <element name="redemptionPeriod" type="ereg:enumStatusType" /> <element name="restore" type="ereg:enumStatusType" /> <element name="other" type="ereg:enumStatusType" /> </choice> </complexType> </element> <element name="registrationReference" type="iris:entityType" minOccurs="0" maxOccurs="1" /> <element name="registry" type="iris:entityType" minOccurs="0" maxOccurs="1" /> <element name="registrar" type="iris:entityType" minOccurs="0" maxOccurs="1" /> <element name="validationEntity" type="iris:entityType" minOccurs="0" maxOccurs="unbounded" /> <element name="signalCSP" type="iris:entityType" minOccurs="0" maxOccurs="unbounded" /> <element name="dataCSP" type="iris:entityType" minOccurs="0" maxOccurs="unbounded" /> <element name="lineCSP"

Newton                      Standards Track                    [Page 29]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 29] RFC 4414 ENUM Registry Type for IRIS February 2006

               type="iris:entityType"
               minOccurs="0"
               maxOccurs="unbounded"/>
             <element
               name="voiceCSP"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               name="otherCSP"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               name="validationEvent"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="unbounded"/>
             <element
               name="initialDelegationDateTime"
               type="ereg:dateTimePrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="lastRenewalDateTime"
               type="ereg:dateTimePrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="expirationDateTime"
               type="ereg:dateTimePrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="lastDelegationModificationDateTime"
               type="ereg:dateTimePrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="lastDelegationModificationBy"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="1" />
             <element

type="iris:entityType" minOccurs="0" maxOccurs="unbounded"/> <element name="voiceCSP" type="iris:entityType" minOccurs="0" maxOccurs="unbounded" /> <element name="otherCSP" type="iris:entityType" minOccurs="0" maxOccurs="unbounded" /> <element name="validationEvent" type="iris:entityType" minOccurs="0" maxOccurs="unbounded"/> <element name="initialDelegationDateTime" type="ereg:dateTimePrivacyType" nillable="true" minOccurs="0" maxOccurs="1" /> <element name="lastRenewalDateTime" type="ereg:dateTimePrivacyType" nillable="true" minOccurs="0" maxOccurs="1" /> <element name="expirationDateTime" type="ereg:dateTimePrivacyType" nillable="true" minOccurs="0" maxOccurs="1" /> <element name="lastDelegationModificationDateTime" type="ereg:dateTimePrivacyType" nillable="true" minOccurs="0" maxOccurs="1" /> <element name="lastDelegationModificationBy" type="iris:entityType" minOccurs="0" maxOccurs="1" /> <element

Newton                      Standards Track                    [Page 30]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 30] RFC 4414 ENUM Registry Type for IRIS February 2006

               name="lastVerificationDateTime"
               type="ereg:dateTimePrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="1" />
             <element
               ref="iris:seeAlso"
               minOccurs="0"
               maxOccurs="unbounded" />
           </sequence>
         </extension>
       </complexContent>
     </complexType>

name="lastVerificationDateTime" type="ereg:dateTimePrivacyType" nillable="true" minOccurs="0" maxOccurs="1" /> <element ref="iris:seeAlso" minOccurs="0" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType>

     <element
       name="enum"
       type="ereg:enumType"
       substitutionGroup="iris:result" />

     <!--                                           -->
     <!-- Host                                      -->
     <!--                                           -->

     <complexType
       name="hostType">
       <complexContent>
         <extension
           base="iris:resultType">
           <sequence>
             <element
               name="hostHandle"
               type="ereg:normalizedStringPrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="hostName"
               type="normalizedString" />
             <element
               name="ipV4Address"
               type="token"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               name="ipV6Address"
               type="token"
               minOccurs="0"
               maxOccurs="unbounded" />

Newton                      Standards Track                    [Page 31]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 31] RFC 4414 ENUM Registry Type for IRIS February 2006

             <element
               name="hostContact"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               name="createdDateTime"
               type="ereg:dateTimePrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="lastModificationDateTime"
               type="ereg:dateTimePrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="lastVerificationDateTime"
               type="ereg:dateTimePrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="1" />
             <element
               ref="iris:seeAlso"
               minOccurs="0"
               maxOccurs="unbounded" />
           </sequence>
         </extension>
       </complexContent>
     </complexType>

     <element
       name="host"
       type="ereg:hostType"
       substitutionGroup="iris:result" />

     <!--                                           -->
     <!-- Contact                                   -->
     <!--                                           -->

     <complexType
       name="contactType">
       <complexContent>
         <extension
           base="iris:resultType">
           <sequence>
             <element

<complexType name="contactType"> <complexContent> <extension base="iris:resultType"> <sequence> <element

Newton                      Standards Track                    [Page 32]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 32] RFC 4414 ENUM Registry Type for IRIS February 2006

               name="contactHandle"
               type="ereg:normalizedStringPrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="commonName"
               type="ereg:normalizedStringPrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="1"/>
             <element
               name="language"
               type="language"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="type"
               minOccurs="0"
               maxOccurs="1">
               <complexType>
                 <choice>
                   <element
                     name="person"
                     type="ereg:contactTypeType" />
                   <element
                     name="organization"
                     type="ereg:contactTypeType" />
                   <element
                     name="role"
                     type="ereg:contactTypeType" />
                   <element
                     name="other"
                     type="ereg:contactTypeType" />
                 </choice>
               </complexType>
             </element>
             <element
               name="organization"
               type="ereg:normalizedStringPrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="legalId"
               type="ereg:tokenPrivacyType"
               nillable="true"
               minOccurs="0"

name="contactHandle" type="ereg:normalizedStringPrivacyType" nillable="true" minOccurs="0" maxOccurs="1" /> <element name="commonName" type="ereg:normalizedStringPrivacyType" nillable="true" minOccurs="0" maxOccurs="1"/> <element name="language" type="language" minOccurs="0" maxOccurs="1" /> <element name="type" minOccurs="0" maxOccurs="1"> <complexType> <choice> <element name="person" type="ereg:contactTypeType" /> <element name="organization" type="ereg:contactTypeType" /> <element name="role" type="ereg:contactTypeType" /> <element name="other" type="ereg:contactTypeType" /> </choice> </complexType> </element> <element name="organization" type="ereg:normalizedStringPrivacyType" nillable="true" minOccurs="0" maxOccurs="1" /> <element name="legalId" type="ereg:tokenPrivacyType" nillable="true" minOccurs="0"

Newton                      Standards Track                    [Page 33]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 33] RFC 4414 ENUM Registry Type for IRIS February 2006

               maxOccurs="unbounded" />
             <element
               name="eMail"
               type="ereg:stringPrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               name="sip"
               type="ereg:stringPrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               name="postalAddress"
               minOccurs="0"
               maxOccurs="unbounded" >
               <complexType>
                 <sequence>
                   <element
                     name="address"
                     type="ereg:stringPrivacyType"
                     nillable="true"
                     minOccurs="0"
                     maxOccurs="1" />
                   <element
                     name="city"
                     type="ereg:stringPrivacyType"
                     nillable="true"
                     minOccurs="0"
                     maxOccurs="1" />
                   <element
                     name="region"
                     type="ereg:stringPrivacyType"
                     nillable="true"
                     minOccurs="0"
                     maxOccurs="1" />
                   <element
                     name="postalCode"
                     type="ereg:normalizedStringPrivacyType"
                     nillable="true"
                     minOccurs="0"
                     maxOccurs="1" />
                   <element
                     name="country"
                     type="ereg:tokenPrivacyType"
                     nillable="true"
                     minOccurs="0"

maxOccurs="unbounded" /> <element name="eMail" type="ereg:stringPrivacyType" nillable="true" minOccurs="0" maxOccurs="unbounded" /> <element name="sip" type="ereg:stringPrivacyType" nillable="true" minOccurs="0" maxOccurs="unbounded" /> <element name="postalAddress" minOccurs="0" maxOccurs="unbounded" > <complexType> <sequence> <element name="address" type="ereg:stringPrivacyType" nillable="true" minOccurs="0" maxOccurs="1" /> <element name="city" type="ereg:stringPrivacyType" nillable="true" minOccurs="0" maxOccurs="1" /> <element name="region" type="ereg:stringPrivacyType" nillable="true" minOccurs="0" maxOccurs="1" /> <element name="postalCode" type="ereg:normalizedStringPrivacyType" nillable="true" minOccurs="0" maxOccurs="1" /> <element name="country" type="ereg:tokenPrivacyType" nillable="true" minOccurs="0"

Newton                      Standards Track                    [Page 34]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 34] RFC 4414 ENUM Registry Type for IRIS February 2006

                     maxOccurs="1" />
                 </sequence>
               </complexType>
             </element>
             <element
               name="phone"
               type="ereg:normalizedStringPrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               name="fax"
               type="ereg:normalizedStringPrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               name="createdDateTime"
               type="ereg:dateTimePrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="lastModificationDateTime"
               type="ereg:dateTimePrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="lastVerificationDateTime"
               type="ereg:dateTimePrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="translatedContact"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               ref="iris:seeAlso"
               minOccurs="0"
               maxOccurs="unbounded" />
           </sequence>
         </extension>
       </complexContent>
     </complexType>

maxOccurs="1" /> </sequence> </complexType> </element> <element name="phone" type="ereg:normalizedStringPrivacyType" nillable="true" minOccurs="0" maxOccurs="unbounded" /> <element name="fax" type="ereg:normalizedStringPrivacyType" nillable="true" minOccurs="0" maxOccurs="unbounded" /> <element name="createdDateTime" type="ereg:dateTimePrivacyType" nillable="true" minOccurs="0" maxOccurs="1" /> <element name="lastModificationDateTime" type="ereg:dateTimePrivacyType" nillable="true" minOccurs="0" maxOccurs="1" /> <element name="lastVerificationDateTime" type="ereg:dateTimePrivacyType" nillable="true" minOccurs="0" maxOccurs="1" /> <element name="translatedContact" type="iris:entityType" minOccurs="0" maxOccurs="unbounded" /> <element ref="iris:seeAlso" minOccurs="0" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType>

Newton                      Standards Track                    [Page 35]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 35] RFC 4414 ENUM Registry Type for IRIS February 2006

     <element
       name="contact"
       type="ereg:contactType"
       substitutionGroup="iris:result" />

     <!--                                           -->
     <!-- Registration Authority                    -->
     <!--                                           -->

     <complexType
       name="registrationAuthorityType">
       <complexContent>
         <extension
           base="iris:resultType">
           <sequence>
             <element
               name="serviceInstance"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="organizationName"
               type="string"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="legalId"
               type="token"
               minOccurs="0"
               maxOccurs="1"/>
             <choice
               minOccurs="0"
               maxOccurs="3">
               <element
                 name="registry">
                 <complexType/>
               </element>
               <element
                 name="registrar">
                 <complexType/>
               </element>
               <element
                 name="other">
                 <complexType/>
               </element>
             </choice>
             <group ref="ereg:contactGroup" />
             <element

<complexType name="registrationAuthorityType"> <complexContent> <extension base="iris:resultType"> <sequence> <element name="serviceInstance" type="iris:entityType" minOccurs="0" maxOccurs="1" /> <element name="organizationName" type="string" minOccurs="0" maxOccurs="1" /> <element name="legalId" type="token" minOccurs="0" maxOccurs="1"/> <choice minOccurs="0" maxOccurs="3"> <element name="registry"> <complexType/> </element> <element name="registrar"> <complexType/> </element> <element name="other"> <complexType/> </element> </choice> <group ref="ereg:contactGroup" /> <element

Newton                      Standards Track                    [Page 36]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 36] RFC 4414 ENUM Registry Type for IRIS February 2006

               ref="iris:seeAlso"
               minOccurs="0"
               maxOccurs="unbounded" />
           </sequence>
         </extension>
       </complexContent>
     </complexType>

ref="iris:seeAlso" minOccurs="0" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType>

     <element
       name="registrationAuthority"
       type="ereg:registrationAuthorityType"
       substitutionGroup="iris:result" />

     <!--                                           -->
     <!-- Validation Entity                         -->
     <!--                                           -->

     <complexType
       name="validationEntityType">
       <complexContent>
         <extension
           base="iris:resultType">
           <sequence>
             <element
               name="serviceInstance"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="organizationName"
               type="string"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="legalId"
               type="token"
               minOccurs="0"
               maxOccurs="1"/>
             <group ref="ereg:contactGroup" />
             <element
               ref="iris:seeAlso"
               minOccurs="0"
               maxOccurs="unbounded" />
           </sequence>
         </extension>
       </complexContent>
     </complexType>

Newton                      Standards Track                    [Page 37]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 37] RFC 4414 ENUM Registry Type for IRIS February 2006

     <element
       name="validationEntity"
       type="ereg:validationEntityType"
       substitutionGroup="iris:result" />

     <!--                                           -->
     <!-- Communication Service Provider            -->
     <!--                                           -->

     <complexType
       name="communicationServiceProviderType">
       <complexContent>
         <extension
           base="iris:resultType">
           <sequence>
             <element
               name="serviceInstance"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="organizationName"
               type="string"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="legalId"
               type="token"
               minOccurs="0"
               maxOccurs="1"/>
             <element
               name="cspId"
               type="token"
               minOccurs="0"
               maxOccurs="1"/>
             <choice
               minOccurs="0"
               maxOccurs="5">
               <element
                 minOccurs="0"
                 maxOccurs="1"
                 name="line">
                 <complexType/>
               </element>
               <element
                 minOccurs="0"
                 maxOccurs="1"
                 name="data">

Newton                      Standards Track                    [Page 38]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 38] RFC 4414 ENUM Registry Type for IRIS February 2006

                 <complexType/>
               </element>
               <element
                 minOccurs="0"
                 maxOccurs="1"
                 name="voice">
                 <complexType/>
               </element>
               <element
                 minOccurs="0"
                 maxOccurs="1"
                 name="signal">
                 <complexType/>
               </element>
               <element
                 minOccurs="0"
                 maxOccurs="1"
                 name="other">
                 <complexType/>
               </element>
             </choice>
             <group ref="ereg:contactGroup" />
             <element
               ref="iris:seeAlso"
               minOccurs="0"
               maxOccurs="unbounded" />
           </sequence>
         </extension>
       </complexContent>
     </complexType>

     <element
       name="communicationServiceProvider"
       type="ereg:communicationServiceProviderType"
       substitutionGroup="iris:result" />

     <!--                                           -->
     <!-- Validation Event                          -->
     <!--                                           -->

     <complexType
       name="validationEventType">
       <complexContent>
         <extension
           base="iris:resultType">
           <sequence>
             <element
               name="serial"

<complexType name="validationEventType"> <complexContent> <extension base="iris:resultType"> <sequence> <element name="serial"

Newton                      Standards Track                    [Page 39]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 39] RFC 4414 ENUM Registry Type for IRIS February 2006

               type="token"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               name="methodId"
               type="token"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               name="validationEntity"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               name="registrar"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               name="executionDateTime"
               type="ereg:dateTimePrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="expirationDateTime"
               type="ereg:dateTimePrivacyType"
               nillable="true"
               minOccurs="0"
               maxOccurs="1" />
             <element
               ref="iris:seeAlso"
               minOccurs="0"
               maxOccurs="unbounded" />
           </sequence>
         </extension>
       </complexContent>
     </complexType>

type="token" minOccurs="0" maxOccurs="unbounded" /> <element name="methodId" type="token" minOccurs="0" maxOccurs="unbounded" /> <element name="validationEntity" type="iris:entityType" minOccurs="0" maxOccurs="unbounded" /> <element name="registrar" type="iris:entityType" minOccurs="0" maxOccurs="unbounded" /> <element name="executionDateTime" type="ereg:dateTimePrivacyType" nillable="true" minOccurs="0" maxOccurs="1" /> <element name="expirationDateTime" type="ereg:dateTimePrivacyType" nillable="true" minOccurs="0" maxOccurs="1" /> <element ref="iris:seeAlso" minOccurs="0" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType>

     <element
       name="validationEvent"
       type="ereg:validationEventType"
       substitutionGroup="iris:result" />

     <!--                                           -->
     <!-- Contact Group                             -->
     <!--                                           -->

Newton                      Standards Track                    [Page 40]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 40] RFC 4414 ENUM Registry Type for IRIS February 2006

     <group name="contactGroup">
       <sequence>
         <element
           name="billingContact"
           type="iris:entityType"
           minOccurs="0"
           maxOccurs="unbounded" />
         <element
           name="technicalContact"
           type="iris:entityType"
           minOccurs="0"
           maxOccurs="unbounded" />
         <element
           name="administrativeContact"
           type="iris:entityType"
           minOccurs="0"
           maxOccurs="unbounded" />
         <element
           name="legalContact"
           type="iris:entityType"
           minOccurs="0"
           maxOccurs="unbounded" />
         <element
           name="zoneContact"
           type="iris:entityType"
           minOccurs="0"
           maxOccurs="unbounded" />
         <element
           name="abuseContact"
           type="iris:entityType"
           minOccurs="0"
           maxOccurs="unbounded" />
         <element
           name="securityContact"
           type="iris:entityType"
           minOccurs="0"
           maxOccurs="unbounded" />
         <element
           name="otherContact"
           type="iris:entityType"
           minOccurs="0"
           maxOccurs="unbounded" />
       </sequence>
     </group>

     <!--                                           -->
     <!-- Privacy Label Types                       -->
     <!--                                           -->

Newton                      Standards Track                    [Page 41]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 41] RFC 4414 ENUM Registry Type for IRIS February 2006

     <attributeGroup
       name="privacyLabelAttributeGroup">
       <attribute
         name="private"
         type="boolean" />
       <attribute
         name="denied"
         type="boolean" />
       <attribute
         name="doNotRedistribute"
         type="boolean" />
       <attribute
         name="specialAccess"
         type="boolean" />
     </attributeGroup>

     <complexType
       name="dateTimePrivacyType">
       <simpleContent>
         <extension
           base="dateTime">
           <attributeGroup
             ref="ereg:privacyLabelAttributeGroup" />
         </extension>
       </simpleContent>
     </complexType>

     <complexType
       name="stringPrivacyType">
       <simpleContent>
         <extension
           base="string">
           <attributeGroup
             ref="ereg:privacyLabelAttributeGroup" />
         </extension>
       </simpleContent>
     </complexType>

     <complexType
       name="normalizedStringPrivacyType">
       <simpleContent>
         <extension
           base="normalizedString">
           <attributeGroup
             ref="ereg:privacyLabelAttributeGroup" />
         </extension>
       </simpleContent>
     </complexType>

Newton                      Standards Track                    [Page 42]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 42] RFC 4414 ENUM Registry Type for IRIS February 2006

     <complexType
       name="tokenPrivacyType">
       <simpleContent>
         <extension
           base="token">
           <attributeGroup
             ref="ereg:privacyLabelAttributeGroup" />
         </extension>
       </simpleContent>
     </complexType>

     <complexType
       name="enumStatusType">
       <sequence>
         <element
           name="appliedDate"
           type="dateTime"
           minOccurs="0"
           maxOccurs="1" />
         <element
           name="description"
           minOccurs="0"
           maxOccurs="unbounded">
           <complexType>
             <simpleContent>
               <extension
                 base="string">
                 <attribute
                   name="language"
                   type="language"
                   use="required" />
               </extension>
             </simpleContent>
           </complexType>
         </element>
         <element
           name="subStatus"
           minOccurs="0"
           maxOccurs="1">
           <complexType>
             <simpleContent>
               <extension
                 base="token">
                 <attribute
                   type="token"
                   use="required"
                   name="authority"/>
               </extension>

Newton                      Standards Track                    [Page 43]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 43] RFC 4414 ENUM Registry Type for IRIS February 2006

             </simpleContent>
           </complexType>
         </element>
       </sequence>
       <attributeGroup
         ref="ereg:privacyLabelAttributeGroup" />
       <attribute
         name="actor">
         <simpleType>
           <restriction
             base="string">
             <enumeration
               value="registry"/>
             <enumeration
               value="registrar"/>
           </restriction>
         </simpleType>
       </attribute>
       <attribute
         name="disposition">
         <simpleType>
           <restriction
             base="string">
             <enumeration
               value="prohibited"/>
             <enumeration
               value="pending"/>
           </restriction>
         </simpleType>
       </attribute>
       <attribute
         name="scope"
         type="token" />
     </complexType>

</simpleContent> </complexType> </element> </sequence> <attributeGroup ref="ereg:privacyLabelAttributeGroup" /> <attribute name="actor"> <simpleType> <restriction base="string"> <enumeration value="registry"/> <enumeration value="registrar"/> </restriction> </simpleType> </attribute> <attribute name="disposition"> <simpleType> <restriction base="string"> <enumeration value="prohibited"/> <enumeration value="pending"/> </restriction> </simpleType> </attribute> <attribute name="scope" type="token" /> </complexType>

     <complexType
       name="contactTypeType">
       <sequence>
         <element
           name="description"
           minOccurs="0"
           maxOccurs="unbounded">
           <complexType>
             <simpleContent>
               <extension
                 base="string">
                 <attribute
                   name="language"

<complexType name="contactTypeType"> <sequence> <element name="description" minOccurs="0" maxOccurs="unbounded"> <complexType> <simpleContent> <extension base="string"> <attribute name="language"

Newton                      Standards Track                    [Page 44]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 44] RFC 4414 ENUM Registry Type for IRIS February 2006

                   type="language"
                   use="required" />
               </extension>
             </simpleContent>
           </complexType>
         </element>
       </sequence>
       <attributeGroup
         ref="ereg:privacyLabelAttributeGroup" />
     </complexType>

type="language" use="required" /> </extension> </simpleContent> </complexType> </element> </sequence> <attributeGroup ref="ereg:privacyLabelAttributeGroup" /> </complexType>

     <!-- ========================================= -->
     <!--                                           -->
     <!-- Error Codes                               -->
     <!--                                           -->
     <!-- ========================================= -->

     <!--                                           -->
     <!-- Search Too Wide                           -->
     <!--                                           -->

     <element
       name="searchTooWide"
       type="iris:codeType"
       substitutionGroup="iris:genericCode" />

     <!--                                           -->
     <!-- Language Not Supported                    -->
     <!--                                           -->

     <complexType
       name="languageNotSupportedType">
       <complexContent>
         <extension
           base="iris:codeType">
           <sequence>
             <element
               name="unsupportedLanguage"
               type="language"
               minOccurs="1"
               maxOccurs="unbounded" />
           </sequence>
         </extension>
       </complexContent>
     </complexType>

     <element
       name="languageNotSupported"

<element name="languageNotSupported"

Newton                      Standards Track                    [Page 45]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 45] RFC 4414 ENUM Registry Type for IRIS February 2006

       type="ereg:languageNotSupportedType"
       substitutionGroup="iris:genericCode" />

type="ereg:languageNotSupportedType" substitutionGroup="iris:genericCode" />

   </schema>

</schema>

                            Figure 1: ereg.xsd

Figure 1: ereg.xsd

5.  Blocks Extensible Exchange Protocol (BEEP) Transport Compliance

5. Blocks Extensible Exchange Protocol (BEEP) Transport Compliance

   IRIS allows several extensions of the core capabilities.  This
   section outlines those extensions allowable by IRIS-BEEP [6].

IRIS allows several extensions of the core capabilities. This section outlines those extensions allowable by IRIS-BEEP [6].

5.1.  Message Pattern

5.1. Message Pattern

   This registry type uses the default message pattern as described in
   IRIS-BEEP [6].

This registry type uses the default message pattern as described in IRIS-BEEP [6].

5.2.  Server Authentication

5.2. Server Authentication

   This registry type only uses the basic Transport Layer Security (TLS)
   server authentication method as described in IRIS-BEEP [6].

This registry type only uses the basic Transport Layer Security (TLS) server authentication method as described in IRIS-BEEP [6].

6.  URI Resolution

6. URI Resolution

6.1.  Application Service Label

6.1. Application Service Label

   The application service label associated with this registry type MUST
   be "EREG1".  This is the abbreviated form of the URN for this
   registry type, urn:ietf:params:xml:ns:ereg1.

The application service label associated with this registry type MUST be "EREG1". This is the abbreviated form of the URN for this registry type, urn:ietf:params:xml:ns:ereg1.

7.  Internationalization Considerations

7. Internationalization Considerations

   Implementers should be aware of considerations for
   internationalization in IRIS [5].

Implementers should be aware of considerations for internationalization in IRIS [5].

   The social data associated with contacts may be non-ASCII, and could
   contain virtually any Unicode character.  The <language> element is
   provided in queries that have potential to traverse such data.
   Clients should use these elements to indicate to the server of the
   target languages desired, and servers should use these elements to
   better enable normalization and search processes (see
   <http://www.unicode.org/reports/tr15/>).

The social data associated with contacts may be non-ASCII, and could contain virtually any Unicode character. The <language> element is provided in queries that have potential to traverse such data. Clients should use these elements to indicate to the server of the target languages desired, and servers should use these elements to better enable normalization and search processes (see <http://www.unicode.org/reports/tr15/>).

   Clients needing to localize the data tags in this protocol should
   take note that localization is only needed on the names of XML
   elements and attributes with the exception of elements containing
   date and time information.  The schema for this registry has been
   designed so that clients need not interpret the content of elements

Clients needing to localize the data tags in this protocol should take note that localization is only needed on the names of XML elements and attributes with the exception of elements containing date and time information. The schema for this registry has been designed so that clients need not interpret the content of elements

Newton                      Standards Track                    [Page 46]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 46] RFC 4414 ENUM Registry Type for IRIS February 2006

   or attributes for localization, other than those elements containing
   date and time information.

or attributes for localization, other than those elements containing date and time information.

   Clients should also make use of the <language> elements provided in
   many of the results.  Results containing data that may be in Unicode
   are accompanied by these elements in order to aid better presentation
   of the data to the user.

Clients should also make use of the <language> elements provided in many of the results. Results containing data that may be in Unicode are accompanied by these elements in order to aid better presentation of the data to the user.

   The "dateTimePrivacyType" element content conforms to the XML Schema
   [3] data type "dateTime".  The contents of this element MUST be
   specified using the 'Z' indicator for Coordinated Universal Time
   (UTC).

The "dateTimePrivacyType" element content conforms to the XML Schema [3] data type "dateTime". The contents of this element MUST be specified using the 'Z' indicator for Coordinated Universal Time (UTC).

8.  IANA Considerations

8. IANA Considerations

8.1.  XML Namespace URN Registration

8.1. XML Namespace URN Registration

   This document makes use of a proposed XML namespace and schema
   registry specified in XML_URN [16].  Accordingly, the following
   registration information is provided for the IANA:

This document makes use of a proposed XML namespace and schema registry specified in XML_URN [16]. Accordingly, the following registration information is provided for the IANA:

   o  URN/URI:

o URN/URI:

      *  urn:ietf:params:xml:schema:ereg1

* urn:ietf:params:xml:schema:ereg1

   o  Contact:

o Contact:

      *  Andrew Newton <andy@hxr.us>

* Andrew Newton <andy@hxr.us>

   o  XML:

o XML:

      *  The XML Schema specified in Section 4

* The XML Schema specified in Section 4

   o  URN/URI:

o URN/URI:

      *  urn:ietf:params:xml:ns:ereg1

* urn:ietf:params:xml:ns:ereg1

   o  Contact:

o Contact:

      *  Andrew Newton <andy@hxr.us>

* Andrew Newton <andy@hxr.us>

   o  XML:

o XML:

      *  None.

* None.

Newton                      Standards Track                    [Page 47]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 47] RFC 4414 ENUM Registry Type for IRIS February 2006

8.2.  S-NAPTR Registration

8.2. S-NAPTR Registration

   The following S-NAPTR application service tag [20] has been
   registered with IANA according to the IANA considerations defined in
   IRIS [5]:

The following S-NAPTR application service tag [20] has been registered with IANA according to the IANA considerations defined in IRIS [5]:

      EREG1

EREG1

8.3.  BEEP Registration

8.3. BEEP Registration

   The following BEEP Profile URI has been registered with IANA
   (http://www.iana.org/assignments/beep-parameters), in addition to the
   registration provided in IRIS-BEEP [6].

The following BEEP Profile URI has been registered with IANA (http://www.iana.org/assignments/beep-parameters), in addition to the registration provided in IRIS-BEEP [6].

      http://iana.org/beep/iris1/ereg1

http://iana.org/beep/iris1/ereg1

9.  Security Considerations

9. Security Considerations

   This document lays out no new considerations for security precautions
   beyond that specified in IRIS [5].

This document lays out no new considerations for security precautions beyond that specified in IRIS [5].

10.  Normative References

10. Normative References

   [1]   World Wide Web Consortium, "Extensible Markup Language (XML)
         1.0", W3C XML, February 1998,
         <http://www.w3.org/TR/1998/REC-xml-19980210>.

[1] World Wide Web Consortium, "Extensible Markup Language (XML) 1.0", W3C XML, February 1998, <http://www.w3.org/TR/1998/REC-xml-19980210>.

   [2]   World Wide Web Consortium, "Namespaces in XML", W3C XML
         Namespaces, January 1999,
         <http://www.w3.org/TR/1999/REC-xml-names-19990114>.

[2] World Wide Web Consortium, "Namespaces in XML", W3C XML Namespaces, January 1999, <http://www.w3.org/TR/1999/REC-xml-names-19990114>.

   [3]   World Wide Web Consortium, "XML Schema Part 2: Datatypes", W3C
         XML Schema, October 2004, <http://www.w3.org/TR/xmlschema-2/>.

[3] World Wide Web Consortium, "XML Schema Part 2: Datatypes", W3C XML Schema, October 2004, <http://www.w3.org/TR/xmlschema-2/>.

   [4]   World Wide Web Consortium, "XML Schema Part 1: Structures", W3C
         XML Schema, October 2004, <http://www.w3.org/TR/xmlschema-1/>.

[4] World Wide Web Consortium, "XML Schema Part 1: Structures", W3C XML Schema, October 2004, <http://www.w3.org/TR/xmlschema-1/>.

   [5]   Newton, A. and M. Sanz, "IRIS: The Internet Registry
         Information Service (IRIS) Core Protocol", RFC 3981, January
         2005.

[5] Newton, A. and M. Sanz, "IRIS: The Internet Registry Information Service (IRIS) Core Protocol", RFC 3981, January 2005.

   [6]   Newton, A. and M. Sanz, "Using the Internet Registry
         Information Service (IRIS) over the Blocks Extensible Exchange
         Protocol (BEEP)", RFC 3983, January 2005.

[6] Newton, A. and M. Sanz, "Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)", RFC 3983, January 2005.

   [7]   Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6)
         Addressing Architecture", RFC 3513, April 2003.

[7] Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6) Addressing Architecture", RFC 3513, April 2003.

Newton                      Standards Track                    [Page 48]

RFC 4414              ENUM Registry Type for IRIS          February 2006

Newton Standards Track [Page 48] RFC 4414 ENUM Registry Type for IRIS February 2006

   [8]   Postel, J., "Internet Protocol", STD 5, RFC 791, September
         1981.

[8] Postel, J., "Internet Protocol", STD 5, RFC 791, September 1981.

   [9]   Mockapetris, P., "Domain names - implementation and
         specification", STD 13, RFC 1035, November 1987.

[9] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987.

   [10]  Bradner, S., "Key words for use in RFCs to Indicate Requirement
         Levels", RFC 2119, BCP 14, March 1997.

[10] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, BCP 14, March 1997.

   [11]  International Organization for Standardization, "Codes for the
         representation of names of countries, 3rd edition", ISO
         Standard 3166, August 1988.

[11] International Organization for Standardization, "Codes for the representation of names of countries, 3rd edition", ISO Standard 3166, August 1988.

   [12]  Braden, R., "Requirements for Internet Hosts - Application and
         Support", STD 3, RFC 1123, October 1989.

[12] Braden, R., "Requirements for Internet Hosts - Application and Support", STD 3, RFC 1123, October 1989.

   [13]  International Telecommunications Union, "The International
         Public Telecommunication Numbering Plan", ITU-T Recommendation
         E.164, February 2005.

[13] International Telecommunications Union, "The International Public Telecommunication Numbering Plan", ITU-T Recommendation E.164, February 2005.

   [14]  International Telecommunications Union, "Notation for national
         and international telephone numbers, e-mail addresses and Web
         addresses", ITU-T Recommendation E.123, February 2001.

[14] International Telecommunications Union, "Notation for national and international telephone numbers, e-mail addresses and Web addresses", ITU-T Recommendation E.123, February 2001.

   [15]  Hoffman, P. and M. Blanchet, "Nameprep: A Stringprep Profile
         for Internationalized Domain Names (IDN)", RFC 3491, March
         2003.

[15] ホフマン、P.、およびM.Blanchet、「Nameprep:」「国際化ドメイン名(IDN)のためのStringprepプロフィール」、RFC3491、2003年3月。

   [16]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
         January 2004.

[16] 食事、M.、「IETF XML登録」、BCP81、RFC3688、2004年1月。

   [17]  Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource
         Identifiers (URI)  Dynamic Delegation Discovery System (DDDS)
         Application  (ENUM)", RFC 3761, April 2004.

[17]FaltstromとP.とM.食事、「Uniform Resource Identifier(URI)ダイナミックな代表団発見システム(DDDS)アプリケーション(ENUM)へのE.164」、RFC3761、2004年4月。

   [18]  Hollenbeck, S., "Domain Registry Grace Period Mapping for the
         Extensible Provisioning Protocol (EPP)", RFC 3915, September
         2004.

[18]Hollenbeck、S.、「広げることができる食糧を供給するプロトコル(EPP)のためのドメイン登録据置期間のマッピング」、RFC3915、2004年9月。

   [19]  Braden, R., "Requirements for Internet Hosts - Application and
         Support", STD 3, RFC 1123, October 1989.

[19] ブレーデン、R.、「インターネットホストのための要件--、アプリケーションとサポート、」、STD3、RFC1123、10月1989日

   [20]  Daigle, L. and A. Newton, "Domain-Based Application Service
         Location Using SRV RRs and the Dynamic Delegation Discovery
         Service (DDDS)", RFC 3958, January 2005.

[20] Daigle、L.、およびA.ニュートン、「SRV RRsを使用するドメインベースのアプリケーション・サービス位置とダイナミックな代表団発見は(DDDS)を修理します」、RFC3958、2005年1月。

Newton                      Standards Track                    [Page 49]

RFC 4414              ENUM Registry Type for IRIS          February 2006

ニュートンStandardsは虹彩2006年2月にRFC4414ENUM登録タイプを追跡します[49ページ]。

Appendix A.  Contributions and Acknowledgements

付録A.貢献と承認

   This document is a derivative of the specification used to define
   forward domain registries for IRIS.  Marcos Sanz was a major
   contributor to that specification, and many of his words and ideas
   are present in this document.  Other contributors include Alexander
   Mayrhofer, Bernie Hoeneisen, Otmar Lendl, and Scott Hollenbeck.

このドキュメントはIRISのために前進のドメイン登録を定義するのに使用される仕様の派生物です。マルコス・サンスはその仕様への一流の貢献者でした、そして、彼の単語と考えの多くが本書では存在しています。他の貢献者はアレクサンダー・マイルホーファー、バーニーHoeneisen、Otmarレンドル、およびスコットHollenbeckを入れます。

Author's Address

作者のアドレス

   Andrew L. Newton
   VeriSign, Inc.
   21345 Ridgetop Circle
   Sterling, VA  20166
   USA

アンドリューL.ニュートンベリサインInc.21345屋根の頂円の英貨、ヴァージニア20166米国

   Phone: +1.7039483382
   EMail: andy@hxr.us
   URI:   http://www.verisignlabs.com/

以下に電話をしてください。 +1.7039483382 メールしてください: andy@hxr.us ユリ: http://www.verisignlabs.com/

Newton                      Standards Track                    [Page 50]

RFC 4414              ENUM Registry Type for IRIS          February 2006

ニュートンStandardsは虹彩2006年2月にRFC4414ENUM登録タイプを追跡します[50ページ]。

Full Copyright Statement

完全な著作権宣言文

   Copyright (C) The Internet Society (2006).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

このドキュメントはBCP78に含まれた権利、ライセンス、および制限を受けることがあります、そして、そこに詳しく説明されるのを除いて、作者は彼らのすべての権利を保有します。

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

このドキュメントと「そのままで」という基礎と貢献者、その人が代表する組織で提供するか、または後援されて、インターネット協会とインターネット・エンジニアリング・タスク・フォースはすべての保証を放棄します、と急行ORが含意したということであり、他を含んでいて、ここに含まれて、情報の使用がここに侵害しないどんな保証も少しもまっすぐになるという情報か市場性か特定目的への適合性のどんな黙示的な保証。

Intellectual Property

知的所有権

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

IETFはどんなIntellectual Property Rightsの正当性か範囲、実現に関係すると主張されるかもしれない他の権利、本書では説明された技術の使用またはそのような権利の下におけるどんなライセンスも利用可能であるかもしれない、または利用可能でないかもしれない範囲に関しても立場を全く取りません。または、それはそれを表しません。どんなそのような権利も特定するためのどんな独立している努力もしました。 BCP78とBCP79でRFCドキュメントの権利に関する手順に関する情報を見つけることができます。

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

IPR公開のコピーが利用可能に作られるべきライセンスの保証、または一般的な免許を取得するのが作られた試みの結果をIETF事務局といずれにもしたか、または http://www.ietf.org/ipr のIETFのオンラインIPR倉庫からこの仕様のimplementersかユーザによるそのような所有権の使用のために許可を得ることができます。

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.

IETFはこの規格を実行するのに必要であるかもしれない技術をカバーするかもしれないどんな著作権もその注目していただくどんな利害関係者、特許、特許出願、または他の所有権も招待します。 ietf-ipr@ietf.org のIETFに情報を記述してください。

Acknowledgement

承認

   Funding for the RFC Editor function is provided by the IETF
   Administrative Support Activity (IASA).

RFC Editor機能のための基金はIETF Administrative Support Activity(IASA)によって提供されます。

Newton                      Standards Track                    [Page 51]

ニュートン標準化過程[51ページ]

一覧

RFC 1～100	RFC 1401～1500	RFC 2801～2900	RFC 4201～4300
RFC 101～200	RFC 1501～1600	RFC 2901～3000	RFC 4301～4400
RFC 201～300	RFC 1601～1700	RFC 3001～3100	RFC 4401～4500
RFC 301～400	RFC 1701～1800	RFC 3101～3200	RFC 4501～4600
RFC 401～500	RFC 1801～1900	RFC 3201～3300	RFC 4601～4700
RFC 501～600	RFC 1901～2000	RFC 3301～3400	RFC 4701～4800
RFC 601～700	RFC 2001～2100	RFC 3401～3500	RFC 4801～4900
RFC 701～800	RFC 2101～2200	RFC 3501～3600	RFC 4901～5000
RFC 801～900	RFC 2201～2300	RFC 3601～3700	RFC 5001～5100
RFC 901～1000	RFC 2301～2400	RFC 3701～3800	RFC 5101～5200
RFC 1001～1100	RFC 2401～2500	RFC 3801～3900	RFC 5201～5300
RFC 1101～1200	RFC 2501～2600	RFC 3901～4000	RFC 5301～5400
RFC 1201～1300	RFC 2601～2700	RFC 4001～4100	RFC 5401～5500
RFC 1301～1400	RFC 2701～2800	RFC 4101～4200

RFC4414 日本語訳

一覧

リンク

メニュー

コメント

お問い合わせ

プライバシーポリシー