Quality of Service for ICN in the IoT
draft-gundogan-icnrg-iotqos-01

Document Type Active Internet-Draft (individual)
Last updated 2019-07-08
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf 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)
ICN Research Group                                           C. Gundogan
Internet-Draft                                               TC. Schmidt
Intended status: Experimental                                HAW Hamburg
Expires: January 9, 2020                                    M. Waehlisch
                                                    link-lab & FU Berlin
                                                                 M. Frey
                                                       F. Shzu-Juraschek
                                                               Safety IO
                                                              J. Pfender
                                                                     VUW
                                                            July 8, 2019

                 Quality of Service for ICN in the IoT
                     draft-gundogan-icnrg-iotqos-01

Abstract

   This document describes manageable resources in ICN IoT deployments
   and a lightweight traffic classification method for mapping
   priorities to resources.  Management methods are further derived for
   controlling latency and reliability of traffic flows in constrained
   environments.  This work includes a distributed management of the
   heterogeneous resources (i) forwarding capacities, (ii) Pending
   Interest Table (PIT) space, and (iii) in-network data storage.  By
   correlating these common ICN resources, performance measures can be
   optimized without sacrificing concurrent traffic demands.  Different
   from the IP world, QoS in ICN can be benifical for all participants
   and manage 'quality instead of unfairness'.

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 January 9, 2020.

Gundogan, et al.         Expires January 9, 2020                [Page 1]
Internet-Draft           QoS for ICN in the IoT                July 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Manageable Resources in the IoT . . . . . . . . . . . . . . .   3
     3.1.  Link Layer  . . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Pending Interest Table  . . . . . . . . . . . . . . . . .   4
     3.3.  Content Store . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Traffic Flow Classification . . . . . . . . . . . . . . . . .   4
   5.  Priority Handling . . . . . . . . . . . . . . . . . . . . . .   5
   6.  Distributed QoS Management  . . . . . . . . . . . . . . . . .   5
     6.1.  Locally Isolated Decisions  . . . . . . . . . . . . . . .   6
     6.2.  Local Resource Correlations . . . . . . . . . . . . . . .   6
     6.3.  Distributed Resource Coordination . . . . . . . . . . . .   7
   7.  Implementation Report and Guidance  . . . . . . . . . . . . .   7
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     10.2.  Informative References . . . . . . . . . . . . . . . . .   8
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The performance of networked systems is largely determined by the
   resources available for forwarding messages between components.  In
   addition to link capacities and buffer queues, Information-centric
   Networks rely on additional resources that shape its overall
   performance, namely Pending Interest Table space, and caching
   capacity.

   Typical IoT deployments add tight resource constraints to this
   picture [RFC7228]: Nodes have processing and memory limitations, the
   underlying link layer technologies are lossy and restricted in
Show full document text