CoRE Resource Directory Extensions
draft-amsuess-core-resource-directory-extensions-00

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00

CoRE                                                          C. Amsuess
Internet-Draft                                          January 10, 2019
Intended status: Experimental
Expires: July 14, 2019

                   CoRE Resource Directory Extensions
          draft-amsuess-core-resource-directory-extensions-00

Abstract

   [ See Introduction ]

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 https://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 July 14, 2019.

Copyright Notice

   Copyright (c) 2019 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
   (https://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.

Amsuess                   Expires July 14, 2019                 [Page 1]
Internet-Draft     CoRE Resource Directory Extensions       January 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Reverse Proxy requests  . . . . . . . . . . . . . . . . . . .   2
     2.1.  Discovery . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Registration  . . . . . . . . . . . . . . . . . . . . . .   3
       2.2.1.  Registration updates  . . . . . . . . . . . . . . . .   4
       2.2.2.  On-Demand proxying  . . . . . . . . . . . . . . . . .   4
       2.2.3.  Examples  . . . . . . . . . . . . . . . . . . . . . .   4
       2.2.4.  Notes on stability and maturity . . . . . . . . . . .   6
       2.2.5.  Security considerations . . . . . . . . . . . . . . .   6
   3.  Infinite lifetime . . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  Example . . . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Lookup across link relations  . . . . . . . . . . . . . . . .   7
     4.1.  Example . . . . . . . . . . . . . . . . . . . . . . . . .   7
   5.  Lifetime Age  . . . . . . . . . . . . . . . . . . . . . . . .   8
   6.  Zone identifier introspection . . . . . . . . . . . . . . . .   8
     6.1.  Example . . . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   9
     7.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   This document pools some extensions to the Resource Directory
   [I-D.ietf-core-resource-directory] that might be useful but have no
   place in the original document.

   They might become individual documents for IETF submission, simple
   registrations in the RD Parameter Registry at IANA, or grow into a
   shape where they can be submitted as a collection of tools.

   At its current state, this draft is a collection of ideas.

   [ This document is being developed at https://gitlab.com/chrysn/
   resource-directory-extensions [1].  ]

2.  Reverse Proxy requests

   When a registrant registers at a Resource Directory, it might not
   have a suitable address it can use as a base address.  Typical
   reasons include being inside a NAT without control over port
   forwarding, or only being able to open outgoing connections (as
   program running inside a web browser utilizing CoAP over WebSocket
   [RFC8323] might be).

Amsuess                   Expires July 14, 2019                 [Page 2]
Internet-Draft     CoRE Resource Directory Extensions       January 2019

   [I-D.ietf-core-resource-directory] suggests (in the Cellular M2M use
   case) that proxy access to such endpoints can be provided, it gives
   no concrete mechanism to do that; this is such a mechanism.

2.1.  Discovery

   An RD that provides proxying functionality advertizes it by
   announcing the additional resource type "TBD1" on its directory
   resource.

2.2.  Registration

   A client passes the "proxy=yes" or "proxy=ondemand" query parameter