| < draft-hollenbeck-rfc4933bis-01.txt | draft-hollenbeck-rfc4933bis-02.txt > | |||
|---|---|---|---|---|
| Network Working Group S. Hollenbeck | Network Working Group S. Hollenbeck | |||
| Internet-Draft VeriSign, Inc. | Internet-Draft VeriSign, Inc. | |||
| Obsoletes: 4933 (if approved) May 14, 2009 | Obsoletes: 4933 (if approved) June 15, 2009 | |||
| Intended status: Standards Track | Intended status: Standards Track | |||
| Expires: November 15, 2009 | Expires: December 17, 2009 | |||
| Extensible Provisioning Protocol (EPP) Contact Mapping | Extensible Provisioning Protocol (EPP) Contact Mapping | |||
| draft-hollenbeck-rfc4933bis-01 | draft-hollenbeck-rfc4933bis-02 | |||
| Status of This Memo | Status of This Memo | |||
| This Internet-Draft is submitted to IETF in full conformance with the | This Internet-Draft is submitted to IETF in full conformance with the | |||
| provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF), its areas, and its working groups. Note that | Task Force (IETF), its areas, and its working groups. Note that | |||
| other groups may also distribute working documents as Internet- | other groups may also distribute working documents as Internet- | |||
| Drafts. | Drafts. | |||
| skipping to change at page 1, line 33 ¶ | skipping to change at page 1, line 33 ¶ | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
| http://www.ietf.org/ietf/1id-abstracts.txt. | http://www.ietf.org/ietf/1id-abstracts.txt. | |||
| The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
| http://www.ietf.org/shadow.html. | http://www.ietf.org/shadow.html. | |||
| This Internet-Draft will expire on November 15, 2009. | This Internet-Draft will expire on December 17, 2009. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2009 IETF Trust and the persons identified as the | Copyright (c) 2009 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents in effect on the date of | Provisions Relating to IETF Documents in effect on the date of | |||
| publication of this document (http://trustee.ietf.org/license-info). | publication of this document (http://trustee.ietf.org/license-info). | |||
| Please review these documents carefully, as they describe your rights | Please review these documents carefully, as they describe your rights | |||
| skipping to change at page 2, line 25 ¶ | skipping to change at page 2, line 25 ¶ | |||
| 2.1. Contact and Client Identifiers . . . . . . . . . . . . . . 3 | 2.1. Contact and Client Identifiers . . . . . . . . . . . . . . 3 | |||
| 2.2. Status Values . . . . . . . . . . . . . . . . . . . . . . 4 | 2.2. Status Values . . . . . . . . . . . . . . . . . . . . . . 4 | |||
| 2.3. Individual and Organizational Names . . . . . . . . . . . 5 | 2.3. Individual and Organizational Names . . . . . . . . . . . 5 | |||
| 2.4. Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 | 2.4. Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 | |||
| 2.4.1. Street, City, and State or Province . . . . . . . . . 6 | 2.4.1. Street, City, and State or Province . . . . . . . . . 6 | |||
| 2.4.2. Postal Code . . . . . . . . . . . . . . . . . . . . . 6 | 2.4.2. Postal Code . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 2.4.3. Country . . . . . . . . . . . . . . . . . . . . . . . 6 | 2.4.3. Country . . . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 2.5. Telephone Numbers . . . . . . . . . . . . . . . . . . . . 6 | 2.5. Telephone Numbers . . . . . . . . . . . . . . . . . . . . 6 | |||
| 2.6. Email Addresses . . . . . . . . . . . . . . . . . . . . . 6 | 2.6. Email Addresses . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 2.7. Dates and Times . . . . . . . . . . . . . . . . . . . . . 6 | 2.7. Dates and Times . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 2.8. Authorization Information . . . . . . . . . . . . . . . . 7 | 2.8. Authorization Information . . . . . . . . . . . . . . . . 6 | |||
| 2.9. Disclosure of Data Elements and Attributes . . . . . . . . 7 | 2.9. Disclosure of Data Elements and Attributes . . . . . . . . 7 | |||
| 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 8 | 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 8 | |||
| 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . . 8 | 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . . 8 | |||
| 3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 9 | 3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 9 | |||
| 3.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . . 10 | 3.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . . 10 | |||
| 3.1.3. EPP <transfer> Query Command . . . . . . . . . . . . . 14 | 3.1.3. EPP <transfer> Query Command . . . . . . . . . . . . . 14 | |||
| 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . . 16 | 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . . 16 | |||
| 3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . . 17 | 3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . . 17 | |||
| 3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . . 20 | 3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . . 20 | |||
| 3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 21 | 3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 21 | |||
| skipping to change at page 5, line 5 ¶ | skipping to change at page 5, line 5 ¶ | |||
| The contact object has at least one active association with | The contact object has at least one active association with | |||
| another object, such as a domain object. Servers SHOULD provide | another object, such as a domain object. Servers SHOULD provide | |||
| services to determine existing object associations. | services to determine existing object associations. | |||
| - ok | - ok | |||
| This is the normal status value for an object that has no pending | This is the normal status value for an object that has no pending | |||
| operations or prohibitions. This value is set and removed by the | operations or prohibitions. This value is set and removed by the | |||
| server as other status values are added or removed. | server as other status values are added or removed. | |||
| - pendingCreate, pendingDelete, pendingRenew, pendingTransfer, | - pendingCreate, pendingDelete, pendingTransfer, pendingUpdate | |||
| pendingUpdate | ||||
| A transform command has been processed for the object, but the | A transform command has been processed for the object, but the | |||
| action has not been completed by the server. Server operators can | action has not been completed by the server. Server operators can | |||
| delay action completion for a variety of reasons, such as to allow | delay action completion for a variety of reasons, such as to allow | |||
| for human review or third-party action. A transform command that | for human review or third-party action. A transform command that | |||
| is processed, but whose requested action is pending, is noted with | is processed, but whose requested action is pending, is noted with | |||
| response code 1001. | response code 1001. | |||
| When the requested action has been completed, the pendingCreate, | When the requested action has been completed, the pendingCreate, | |||
| pendingDelete, pendingTransfer, or pendingUpdate status value MUST be | pendingDelete, pendingTransfer, or pendingUpdate status value MUST be | |||
| skipping to change at page 40, line 11 ¶ | skipping to change at page 40, line 11 ¶ | |||
| Robert Burbidge, Dave Crocker, Ayesha Damaraju, Anthony Eden, Sheer | Robert Burbidge, Dave Crocker, Ayesha Damaraju, Anthony Eden, Sheer | |||
| El-Showk, Dipankar Ghosh, Klaus Malorny, Dan Manley, Michael | El-Showk, Dipankar Ghosh, Klaus Malorny, Dan Manley, Michael | |||
| Mealling, Patrick Mevzek, Asbjorn Steira, and Rick Wesson. | Mealling, Patrick Mevzek, Asbjorn Steira, and Rick Wesson. | |||
| 9. References | 9. References | |||
| 9.1. Normative References | 9.1. Normative References | |||
| [I-D.hollenbeck-rfc4930bis] | [I-D.hollenbeck-rfc4930bis] | |||
| Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", | Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", | |||
| draft-hollenbeck-rfc4930bis-01 (work in progress), | draft-hollenbeck-rfc4930bis-02 (work in progress), | |||
| May 2009. | June 2009. | |||
| [ISO3166-1] | [ISO3166-1] | |||
| International Organization for Standardization, "Codes for | International Organization for Standardization, "Codes for | |||
| the representation of names of countries and their | the representation of names of countries and their | |||
| subdivisions -- Part 1: Country codes", ISO Standard 3166, | subdivisions -- Part 1: Country codes", ISO Standard 3166, | |||
| November 2006. | November 2006. | |||
| [ITU.E164.2005] | [ITU.E164.2005] | |||
| International Telecommunication Union, "The international | International Telecommunication Union, "The international | |||
| public telecommunication numbering plan", ITU- | public telecommunication numbering plan", ITU- | |||
| skipping to change at page 40, line 38 ¶ | skipping to change at page 40, line 38 ¶ | |||
| [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO | [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO | |||
| 10646", STD 63, RFC 3629, November 2003. | 10646", STD 63, RFC 3629, November 2003. | |||
| [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, | [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, | |||
| January 2004. | January 2004. | |||
| [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, | [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, | |||
| October 2008. | October 2008. | |||
| [W3C.REC-xml-20040204] | [W3C.REC-xml-20040204] | |||
| Sperberg-McQueen, C., Maler, E., Yergeau, F., Paoli, J., | Yergeau, F., Maler, E., Bray, T., Paoli, J., and C. | |||
| and T. Bray, "Extensible Markup Language (XML) 1.0 (Third | Sperberg-McQueen, "Extensible Markup Language (XML) 1.0 | |||
| Edition)", World Wide Web Consortium FirstEdition REC-xml- | (Third Edition)", World Wide Web Consortium | |||
| 20040204, February 2004, | FirstEdition REC-xml-20040204, February 2004, | |||
| <http://www.w3.org/TR/2004/REC-xml-20040204>. | <http://www.w3.org/TR/2004/REC-xml-20040204>. | |||
| [W3C.REC-xmlschema-1-20041028] | [W3C.REC-xmlschema-1-20041028] | |||
| Beech, D., Thompson, H., Mendelsohn, N., and M. Maloney, | Thompson, H., Beech, D., Mendelsohn, N., and M. Maloney, | |||
| "XML Schema Part 1: Structures Second Edition", World Wide | "XML Schema Part 1: Structures Second Edition", World Wide | |||
| Web Consortium Recommendation REC-xmlschema-1-20041028, | Web Consortium Recommendation REC-xmlschema-1-20041028, | |||
| October 2004, | October 2004, | |||
| <http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>. | <http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>. | |||
| [W3C.REC-xmlschema-2-20041028] | [W3C.REC-xmlschema-2-20041028] | |||
| Malhotra, A. and P. Biron, "XML Schema Part 2: Datatypes | Malhotra, A. and P. Biron, "XML Schema Part 2: Datatypes | |||
| Second Edition", World Wide Web Consortium | Second Edition", World Wide Web Consortium | |||
| Recommendation REC-xmlschema-2-20041028, October 2004, | Recommendation REC-xmlschema-2-20041028, October 2004, | |||
| <http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>. | <http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>. | |||
| skipping to change at page 41, line 18 ¶ | skipping to change at page 41, line 18 ¶ | |||
| 9.2. Informative References | 9.2. Informative References | |||
| [RFC2781] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO | [RFC2781] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO | |||
| 10646", RFC 2781, February 2000. | 10646", RFC 2781, February 2000. | |||
| [RFC4933] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) | [RFC4933] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) | |||
| Contact Mapping", RFC 4933, May 2007. | Contact Mapping", RFC 4933, May 2007. | |||
| Appendix A. Changes from RFC 4933 | Appendix A. Changes from RFC 4933 | |||
| 1. Changed "This document obsoletes RFC 3733" to "This document is | 1. Changed "This document obsoletes RFC 3733" to "This document is | |||
| intended to obsolete RFC 4933". | intended to obsolete RFC 4933". | |||
| 2. Replaced references to RFC 0822 with references to 5322. | 2. Replaced references to RFC 0822 with references to 5322. | |||
| 3. Replaced references to RFC 3733 with references to 4933. | 3. Replaced references to RFC 3733 with references to 4933. | |||
| 4. Replaced references to RFC 4930 with references to 4930bis. | 4. Replaced references to RFC 4930 with references to 4930bis. | |||
| 5. Updated reference to ISO 3166-1. | 5. Updated reference to ISO 3166-1. | |||
| 6. Modified text in Section 3.2.2 to include 2305 response code. | 6. Removed pendingRenew status from Section 2.2 because this | |||
| 7. Updated Section 5. | document does not define a mapping for the EPP <renew> command. | |||
| 8. Added "Other notification methods MAY be used in addition to the | 7. Modified text in Section 3.2.2 to include 2305 response code. | |||
| required service message" in Section 3.2. | 8. Updated Section 5. | |||
| 9. Added 2201 response code text in Section 3.2. | 9. Added "Other notification methods MAY be used in addition to the | |||
| required service message" in Section 3.2. | ||||
| 10. Added 2201 response code text in Section 3.2. | ||||
| Author's Address | Author's Address | |||
| Scott Hollenbeck | Scott Hollenbeck | |||
| VeriSign, Inc. | VeriSign, Inc. | |||
| 21345 Ridgetop Circle | 21345 Ridgetop Circle | |||
| Dulles, VA 20166-6503 | Dulles, VA 20166-6503 | |||
| US | US | |||
| EMail: shollenbeck@verisign.com | EMail: shollenbeck@verisign.com | |||
| End of changes. 10 change blocks. | ||||
| 25 lines changed or deleted | 26 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||