Skip to main content
  • Registry

CIRA Fury-rgp-1.0 EPP Extension

CIRA fury-rgp-1.0 EPP Extension

Namespace: urn:ietf:params:xml:ns:fury-rgp-1.0

1. Introduction

This document describes an extension mapping for version 1.0 of the Extensible Provisioning Protocol (EPP). The mapping provides a mechanism to query additional information about the Redemption Grace Period (RGP) status (as defined in RFC 3915) of a domain. This extension adds elements to responses only when it has been selected in the <login> service extensions.

2. EPP Command Mapping

2.1. EPP Query Commands

This extension does not add any elements to the EPP <check>, <poll>, or <transfer> commands or their responses.

2.1.1. EPP <info> Command

This extension does not add elements to the <info> command itself, but it may include elements in the response.

When a <domain:info> command has been processed successfully and the fury‑rgp‑1.0 extension was selected at login, the server may include an <extension> element containing <fury-rgp:rgpInfo> with:

 

  • OPTIONAL <fury-rgp:rgpStatusEnd> — the date/time when the RGP status ends.

S:
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S:  <response>
S:    <result code="1000">
S:      <msg>Command completed successfully</msg>
S:    </result>
S:    <resData>
S:      <domain:infData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S:        <domain:name>example.fury</domain:name>
S:        <domain:roid>1234-EXAMPLE</domain:roid>
S:        <domain:status s="ok"/>
S:        <domain:registrant>contact1</domain:registrant>
S:        <domain:contact type="admin">contact2</domain:contact>
S:        <domain:contact type="tech">contact2</domain:contact>
S:        <domain:ns>
S:          <domain:hostObj>ns1.example.fury</domain:hostObj>
S:          <domain:hostObj>ns1.example.fury</domain:hostObj>
S:        </domain:ns>
S:        <domain:clID>ClientX</domain:clID>
S:        <domain:crID>ClientY</domain:crID>
S:        <domain:crDate>2018-12-17T22:00:00.0Z</domain:crDate>
S:        <domain:exDate>2020-12-28T22:00:00.0Z</domain:exDate>
S:        <domain:authInfo>
S:          <domain:pw>2fooBAR</domain:pw>
S:        </domain:authInfo>
S:      </domain:infData>
S:    </resData>
S:    <extension>
S:      <fury-rgp:rgpInfo xmlns:fury-rgp="urn:ietf:params:xml:ns:fury-rgp-1.0">
S:        <fury-rgp:rgpStatusEnd>2020-12-28T22:00:00.0Z</fury-rgp:rgpStatusEnd>
S:      </fury-rgp:rgpInfo>
S:    </extension>
S:    <trID>
S:      <clTRID>ABC-12345</clTRID>
S:      <svTRID>54322-XYZ</svTRID>
S:    </trID>
S:  </response>
S:</epp>

2.2. EPP Transform Commands

This extension does not add any elements to the EPP <create>, <delete>, <renew>,<transfer>, or <update> commands or responses.

3. Formal Syntax (XML Schema)

An EPP object mapping is specified in XML Schema notation. The formal syntax presented here is a complete schema representation of the object mapping suitable for automated validation of EPP XML instances using this extension.

<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:fury-rgp-1.0"
        xmlns:fury-rgp="urn:ietf:params:xml:ns:fury-rgp-1.0"
        xmlns="http://www.w3.org/2001/XMLSchema"
        elementFormDefault="qualified">

   <annotation>
      <documentation>
         Extensible Provisioning Protocol v1.0
         contact and domain
         extension schema for framework for
         provisioning of Fury additional
         information.
      </documentation>
   </annotation>

   <element name="rgpInfo" type="fury-rgp:infDataType" />

   <!-- child elements of the <info> response. -->
   <complexType name="infDataType">
      <sequence>
         <!-- cira domain extension data -->
         <element name="rgpStatusEnd" type="dateTime" minOccurs="0" />
      </sequence>
   </complexType>

</schema>

4. Security Considerations

This extension does not provide any security services beyond those described by EPP (RFC 5730), the EPP domain name mapping (RFC 5731), and the RGP mapping (RFC 3915). The security
considerations described in those specifications apply here as well.

5. References

  • [RFC5730] Hollenbeck, S., “Extensible Provisioning Protocol (EPP)”, STD 69, RFC 5730.
  • [RFC5731] Hollenbeck, S., “Extensible Provisioning Protocol (EPP) Domain Name Mapping”, STD 69, RFC 5731.
  • [RFC3915] Hollenbeck, S., “Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)”, RFC 3915.

6. Acknowledgments

Authored by the Canadian Internet Registration Authority (CIRA) for the Fury Registry Platform. This is an official CIRA EPP extension specification.

© CIRA. Namespace preserved: urn:ietf:params:xml:ns:fury-rgp-1.0.

 

Loading…