Browse Prior Art Database

Guidelines for Extending the Extensible Provisioning Protocol (EPP) (RFC3735)

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

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Hollenbeck: AUTHOR

Abstract

The Extensible Provisioning Protocol (EPP) is an application layer client-server protocol for the provisioning and management of objects stored in a shared central repository. Specified in XML, the protocol defines generic object management operations and an extensible framework that maps protocol operations to objects. This document presents guidelines for use of EPP's extension mechanisms to define new features and object management capabilities.

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

Network Working Group S. Hollenbeck

Request for Comments: 3735 VeriSign, Inc.

Category: Informational March 2004

Guidelines for Extending the Extensible Provisioning Protocol (EPP)

Status of this Memo

This memo provides information for the Internet community. It does

not specify an Internet standard of any kind. Distribution of this

memo is unlimited.

Copyright Notice

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

Abstract

The Extensible Provisioning Protocol (EPP) is an application layer

client-server protocol for the provisioning and management of objects

stored in a shared central repository. Specified in XML, the

protocol defines generic object management operations and an

extensible framework that maps protocol operations to objects. This

document presents guidelines for use of EPP's extension mechanisms to

define new features and object management capabilities.

Table of Contents

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

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

2. Principles of Protocol Extension . . . . . . . . . . . . . . 3

2.1. Documenting Extensions . . . . . . . . . . . . . . . . 3

2.2. Identifying Extensions . . . . . . . . . . . . . . . . 4

2.2.1. Standards Track Extensions . . . . . . . . . . 4

2.2.2. Other Extensions . . . . . . . . . . . . . . . 5

2.3. Extension Announcement and Selection . . . . . . . . . 5

2.4. Protocol-level Extension . . . . . . . . . . . . . . . 7

2.5. Object-level Extension . . . . . . . . . . . . . . . . 7

2.6. Command-Response Extension . . . . . . . . . . . . . . 7

2.7. Authentication Information Extension . . . . . . . . . 7

3. Selecting an Extension Mechanism . . . . . . . . . . . . . . 8

3.1. Mapping and Extension Archives . . . . . . . . . . . 9

4. Internationalization Considerations . . . . . . . . . . . . 9

5. IANA Considerations . . . . . . . . . . . . . . . . . . . . 10

6. Security Considerations . . . . . . . . . . . . . . . . . . 10

7. References . . . . . . . . . . . . . . . . . . . . . . . . . 10

7.1. Normative References . . . . . . . . . . . . . . . . . 10

Hollenbeck Informational [Page 1]

RFC 3735 Guidelines for Extending the EPP March 2004

7.2. Informative References . . . . . . . . . . . . . . . . 11

8. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

9. Author's Address . . . . . . . . . . . . . . . . . . . . . . 12

10. Full Copyright Statement . . . . . . . . . . . . . . . . . . 13

1. Introduction

The Extensible Provisioning Protocol (EPP, [2]) was originally

designed to provide a standard Internet domain name registration

protocol for use between Internet domain name registrars and domain

name registries. However, specific design decisions were made to

ensure that the protocol could also be used in other provisioning

environments. Specifically:

o Extensibility has been a design goal from the very beginning. EPP

is represented in the Extensible Markup Language (XML, [3]), and

is specified in XML Schema ([4]...