Skip to content

epp-reference-index.md

Latest commit

 

History

History
65 lines (53 loc) · 2.39 KB

epp-reference-index.md

File metadata and controls

65 lines (53 loc) · 2.39 KB
Raw

RsReg2 / RNIDS EPP Reference Index

This documentation set is derived from EPP-commands.txt (RsReg2 EPP Commands, v1.2) and rewritten as implementation-oriented markdown for this repository.

Scope

  • Registry profile: RNIDS / RsReg2
  • Protocol base: EPP (RFC 5730/5731/5732/5733/5734)
  • Additional coverage:
    • DNSSEC extension (secDNS-1.1)
    • RNIDS domain/contact extensions
    • Finance info object
    • Poll message model

Core Namespaces

  • EPP: urn:ietf:params:xml:ns:epp-1.0
  • Domain: urn:ietf:params:xml:ns:domain-1.0
  • Contact: urn:ietf:params:xml:ns:contact-1.0
  • Host: urn:ietf:params:xml:ns:host-1.0
  • Finance: urn:ietf:params:xml:ns:finance-1.0
  • secDNS: urn:ietf:params:xml:ns:secDNS-1.1
  • RNIDS domain extension: http://www.rnids.rs/epp/xml/domain-rnids-ext-1.0
  • RNIDS contact extension: http://www.rnids.rs/epp/xml/contact-rnids-ext-1.0

Document Map

EPP Result Code Summary

Common result codes seen across RsReg2 operations:

  • 1000 — Command completed successfully
  • 1001 — Command completed successfully; action pending
  • 1300 — Command completed successfully; no messages
  • 1301 — Command completed successfully; ack to dequeue
  • 1500 — Command completed successfully; ending session
  • 2001 — Command syntax error
  • 2003 — Required parameter missing
  • 2005 — Parameter value syntax/range error
  • 2102 — Unimplemented option
  • 2200 — Authentication error
  • 2201 — Authorization error
  • 2202 — Invalid authorization information
  • 2301 — Object not pending transfer
  • 2302 — Object exists
  • 2303 — Object does not exist
  • 2304 — Object status prohibits operation
  • 2305 — Object association prohibits operation
  • 2306 — Parameter value policy error
  • 2400 — Command failed
  • 2500/2501/2502 — Server-side closing/session limit errors

Practical Notes for This Client

  • Keep request XML deterministic and namespace-explicit.
  • Include clTRID on command requests.
  • Treat RNIDS extension fields as first-class typed DTO fields.
  • For transfer and secure-mode updates, follow RsReg2-specific behaviors described in command docs.