Browse Prior Art Database

Extensible Provisioning Protocol (EPP) Contact Mapping (RFC3733)

IP.com Disclosure Number: IPCOM000022707D
Original Publication Date: 2004-Mar-01
Included in the Prior Art Database: 2004-Mar-26
Document File: 42 page(s) / 83K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Hollenbeck: AUTHOR

Abstract

This document describes an Extensible Provisioning Protocol (EPP) mapping for the provisioning and management of individual or organizational social information identifiers (known as "contacts") stored in a shared central repository. Specified in Extensible Markup Language (XML), the mapping defines EPP command syntax and semantics as applied to contacts.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 5% of the total text.

Network Working Group S. Hollenbeck

Request for Comments: 3733 VeriSign, Inc.

Category: Standards Track March 2004

Extensible Provisioning Protocol (EPP) Contact Mapping

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.

Copyright Notice

Copyright (C) The Internet Society (2004). All Rights Reserved.

Abstract

This document describes an Extensible Provisioning Protocol (EPP)

mapping for the provisioning and management of individual or

organizational social information identifiers (known as "contacts")

stored in a shared central repository. Specified in Extensible

Markup Language (XML), the mapping defines EPP command syntax and

semantics as applied to contacts.

Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.1. Conventions Used In This Document. . . . . . . . . . . . 2

2. Object Attributes. . . . . . . . . . . . . . . . . . . . . . . 3

2.1. Contact and Client Identifiers . . . . . . . . . . . . . 3

2.2. Status Values. . . . . . . . . . . . . . . . . . . . . . 3

2.3. Individual and Organizational Names. . . . . . . . . . . 5

2.4. Address. . . . . . . . . . . . . . . . . . . . . . . . . 5

2.4.1. Street, City, and State or Province. . . . . . . 5

2.4.2. Postal Code. . . . . . . . . . . . . . . . . . . 5

2.4.3. Country. . . . . . . . . . . . . . . . . . . . . 5

2.5. Telephone Numbers. . . . . . . . . . . . . . . . . . . . 5

2.6. Email Addresses. . . . . . . . . . . . . . . . . . . . . 6

2.7. Dates and Times. . . . . . . . . . . . . . . . . . . . . 6

2.8. Authorization Information. . . . . . . . . . . . . . . . 6

2.9. Disclosure of Data Elements and Attributes . . . . . . . 6

3. EPP Command mapping. . . . . . . . . . . . . . . . . . . . . . 8

3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 8

3.1.1. EPP <check> Command. . . . . . . . . . . . . . . 8

Hollenbeck Standards Track [Page 1]

RFC 3733 EPP Contact Mapping March 2004

3.1.2. EPP <info> Command . . . . . . . . . . . . . . . 10

3.1.3. EPP <transfer> Query Command . . . . . . . . . . 14

3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 16

3.2.1. EPP <create> Command . . . . . . . . . . . . . . 17

3.2.2. EPP <delete> Command . . . . . . . . . . . . . . 20

3.2.3. EPP <renew> Command . . . . . . . . . . . . . . 21

3.2.4. EPP <transfer> Command. . . . . . . . . . . . . 21

3.2.5. EPP <update> Command. . . . . . . . . . . . . . 23

3.2.6. Offline Review of Requested Actions. . . . . . . 26

4. Formal Syntax. . . . . . . . . . . . . . . . . . . . . . . . . 29

5. Internationalization Considerations . . . . . . . . . . . . . 37

6. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 38

7. Security Considerations. . . . . . . . . . ....