Registry Maintenance Notifications through Extensible Provisioning Protocol (EPP) poll response with JSON payload
draft-sattler-epp-poll-maintenance-response-04

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2017-11-12
Replaced by draft-sattler-epp-registry-maintenance
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                               T. Sattler
Internet-Draft                                         November 12, 2017  
Intended status: Standard Track                           
Expires: January 31, 2018

              Registry Maintenance Notifications through
 Extensible Provisioning Protocol (EPP) poll response with JSON payload
            draft-sattler-epp-poll-maintenance-response-04

Abstract
   This document describes the JSON payload of an Extensible
   Provisioning Protocol (EPP) poll response to provide Domain Name
   Registry Maintenance Notifications to Domain Name Registrars.

Status of This Memo
   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."
   
   This Internet-Draft will expire on January 31, 2018.

Copyright Notice
   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Sattler                Expires January 31, 2018                 [Page 1]
Internet-Draft         Maintenance JSON Response           November 2017
   
Table of Contents
   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology and Definitions . . . . . . . . . . . . . . .   2
   2.  Common Data Types . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Common Data Structures  . . . . . . . . . . . . . . . . . . .   4
     3.1.  Notifications . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Systems . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.3.  Intervention  . . . . . . . . . . . . . . . . . . . . . .   5
     3.4.  TLDs  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  EPP poll response . . . . . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  Internationalisation Considerations . . . . . . . . . . . . .   7
     7.1.  Character Encoding  . . . . . . . . . . . . . . . . . . .   7
     7.2.  Internationalised Domain Names  . . . . . . . . . . . . .   7
     7.3.  date-time Values  . . . . . . . . . . . . . . . . . . . .   7
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   8
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   Appendix A.  Motivations for using JSON . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9
   
1.  Introduction

   This document describes the JSON [RFC7159] payload of an Extensible
   Provisioning Protocol (EPP) [RFC5730] poll response to provide Domain
   Name Registry Maintenance Notifications to Domain Name Registrars.

1.1.  Terminology and Definitions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119] when
   specified in their uppercase forms.   
   
   The following list describes terminology and definitions used
   throughout this document:
   
   DNRR:             Domain Name Registrar
   
   DNRY:             Domain Name Registry
   
   EPP:              Extensible Provisioning Protocol
   
   JSON:             JavaScript Object Notation
   
   NTFY:             Domain Name Registry Maintenance Notification
   
   UUID:             Universally Unique Identifier
   
Sattler                 Expires January 31, 2018                [Page 2]
Internet-Draft         Maintenance JSON Response           November 2017
                  
2.  Common Data Types

   JSON [RFC7159] defines the data types of a number, character string,
   boolean, array, object, and null.  This section describes the
   semantics and/or syntax reference for common, JSON character strings
   used in this document.
   
   notifications:    contains a single NTFY
Show full document text