Network Tokens
draft-yiakoumis-network-tokens-01

Document Type Active Internet-Draft (individual)
Authors Yiannis Yiakoumis  , Nick McKeown  , Frode Sorensen 
Last updated 2020-06-18
Stream (None)
Intended RFC status (None)
Formats plain text 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)
TBD                                                         Y. Yiakoumis
Internet-Draft                                      Selfie Networks, Inc
Intended status: Standards Track                              N. McKeown
Expires: December 17, 2020                           Stanford University
                                                             F. Sorensen
                                      Norwegian Communications Authority
                                                           June 15, 2020

                             Network Tokens
                   draft-yiakoumis-network-tokens-01

Abstract

   Network tokens is a method for endpoints to explicitly and securely
   coordinate with networks about how their traffic is treated.  They
   are inserted by endpoints in existing protocols, interpreted by
   trusted networks, and may be signed or encrypted to meet security and
   privacy requirements.  Network tokens provide a means for network
   operators to expose datapath services (such as a zero-rating service,
   a user-driven QoS service, or a firewall whitelist), and for end
   users and application providers to access such services.  Network
   tokens are inspired and derived by existing security tokens (like JWT
   and CWT), and borrow several of their core ideas along with security
   and privacy properties.

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 December 17, 2020.

Copyright Notice

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

Yiakoumis, et al.       Expires December 17, 2020               [Page 1]
Internet-Draft                networktokens                    June 2020

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Network Token Overview  . . . . . . . . . . . . . . . . .   3
   2.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Use cases Overview  . . . . . . . . . . . . . . . . . . .   5
       2.1.1.  Zero Rating . . . . . . . . . . . . . . . . . . . . .   5
       2.1.2.  Firewall Whitelist  . . . . . . . . . . . . . . . . .   6
       2.1.3.  QoS . . . . . . . . . . . . . . . . . . . . . . . . .   7
     2.2.  Existing mechanisms . . . . . . . . . . . . . . . . . . .   8
       2.2.1.  DiffServ  . . . . . . . . . . . . . . . . . . . . . .   8
       2.2.2.  Deep Packet Inspection  . . . . . . . . . . . . . . .   8
     2.3.  Requirements and Challenges . . . . . . . . . . . . . . .   9
       2.3.1.  Integration overhead  . . . . . . . . . . . . . . . .   9
       2.3.2.  Detection Accuracy  . . . . . . . . . . . . . . . . .  10
       2.3.3.  Fraud Prevention  . . . . . . . . . . . . . . . . . .  11
       2.3.4.  Implementing user-centric control . . . . . . . . . .  11
       2.3.5.  Privacy . . . . . . . . . . . . . . . . . . . . . . .  12
   3.  Representation  . . . . . . . . . . . . . . . . . . . . . . .  12
   4.  Contents  . . . . . . . . . . . . . . . . . . . . . . . . . .  13
     4.1.  Network Token Common fields . . . . . . . . . . . . . . .  13
       4.1.1.  'iss' (Issuer) field  . . . . . . . . . . . . . . . .  13
       4.1.2.  "sub" (Subject) field . . . . . . . . . . . . . . . .  13
       4.1.3.  "exp" (Expiration Time) field . . . . . . . . . . . .  13
       4.1.4.  "iat" (Issued At) field . . . . . . . . . . . . . . .  14
       4.1.5.  "nti" field (Network Token ID) field  . . . . . . . .  14
       4.1.6.  "bip" field (Bound IP) field  . . . . . . . . . . . .  14
   5.  Network Token Format  . . . . . . . . . . . . . . . . . . . .  14
   6.  Example Network Tokens  . . . . . . . . . . . . . . . . . . .  15
     6.1.  Application Token . . . . . . . . . . . . . . . . . . . .  15
     6.2.  User-centric Token  . . . . . . . . . . . . . . . . . . .  16
Show full document text