A JSON Binding and Encoding for TeRI
draft-peterson-modern-teri-json-01

Document Type Active Internet-Draft (individual)
Last updated 2017-07-03
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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)
Network Working Group                                        J. Peterson
Internet-Draft                                                   Neustar
Intended status: Informational                              July 3, 2017
Expires: January 4, 2018

                  A JSON Binding and Encoding for TeRI
                 draft-peterson-modern-teri-json-01.txt

Abstract

   The Telephone-Related Information (TeRI) framework defines an
   information model for data objects related to the acquisiton,
   management, and retrieval of telephone numbers and information
   related to them via the Internet.  TeRI provides an abstract
   framework that must be instantiated by a particular binding and
   encoding.  This document defines an HTTP binding for TeRI and a
   JavaScript Object Notation (JSON) encoding for TeRI.

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 4, 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

Peterson                 Expires January 4, 2018                [Page 1]
Internet-Draft                  JSON TeRI                      July 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  HTTP TeRI Binding . . . . . . . . . . . . . . . . . . . . . .   3
   4.  JSON TeRI Encoding  . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  TeRI Requests . . . . . . . . . . . . . . . . . . . . . .   3
     4.2.  TeRI Responses  . . . . . . . . . . . . . . . . . . . . .   4
     4.3.  TeRI Records  . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  Informative References  . . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The Telephone-Related Information (TeRI) framework
   [I-D.peterson-modern-teri] defines an information model for data
   objects related to the acquisiton, management, and retrieval of
   telephone numbers and information related to them via the Internet.
   TeRI provides an abstract framework that must be instantiated by a
   particular binding and encoding, as described in
   [I-D.peterson-modern-teri] Section 6.2 and 6.3, respectively.  This
   document defines an HTTP binding and JavaScript Object Notation
   (JSON) [RFC7159] encoding for TeRI.  It does not however define any
   particular profile or deployment environment for using TeRI in this
   fashion; this only demonstrates an instantiation of the baseline TeRI
   specification using JSON.

   This is an early stage Internet-Draft that serves primarily as a
   vehicle to give examples of a potential syntax for TeRI Requests and
   Responses in order to facilitate discussion.

2.  Terminology

   In this document, the key words "MAY", "MUST, "MUST NOT", "SHOULD",
   and "SHOULD NOT", are to be interpreted as described in [RFC2119].
   This document also incorporates the terminology of the MODERN
   Framework [I-D.ietf-modern-problem-framework].

Peterson                 Expires January 4, 2018                [Page 2]
Internet-Draft                  JSON TeRI                      July 2017

3.  HTTP TeRI Binding
Show full document text