Firewall and Service Tickets
draft-herbert-fast-00

Document Type Active Internet-Draft (individual)
Last updated 2018-01-11
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)
INTERNET-DRAFT                                                T. Herbert
Intended Status: Standard                                     Quantonium
Expires: July 2018                                                      
                                                                        
                                                        January 11, 2018

                      Firewall and Service Tickets
                         draft-herbert-fast-00

Abstract

   This document describes the Firewalls and Service Tickets protocol. A
   ticket is data that accompanies a packet and indicates a granted
   right to traverse a network or a request for network service to be
   applied. Applications request tickets from a local agent in the
   network and attach issued tickets to packets. Firewall tickets are
   issued to grant packets the right to traverse a network; service
   tickets indicate the desired service to be applied to a packets. A
   single ticket may provide both firewall and service ticket
   information. Tickets are sent in either IPv6 Destination options or
   Hop-by-Hop options.   

Status of this Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice
 

T. Herbert               Expires July 15, 2018                  [Page 1]
INTERNET DRAFT           draft-herbert-fast-00          January 11, 2018

   Copyright (c) 2018 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.

Table of Contents

   1  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     2.1 Current mechanisms . . . . . . . . . . . . . . . . . . . . .  4
       2.1.1 Stateful firewalls and proxies . . . . . . . . . . . . .  4
       2.1.2 QoS signaling  . . . . . . . . . . . . . . . . . . . . .  5
       2.1.3 Deep packet inspection . . . . . . . . . . . . . . . . .  5
     2.2 Alternative proposals  . . . . . . . . . . . . . . . . . . .  5
       2.2.1 SPUD/PLUS  . . . . . . . . . . . . . . . . . . . . . . .  5
       2.2.2 Path aware networking  . . . . . . . . . . . . . . . . .  6
     2.3 Emerging use cases . . . . . . . . . . . . . . . . . . . . .  7
   3  Architecture  . . . . . . . . . . . . . . . . . . . . . . . . .  8
     3.1 Example packet flow  . . . . . . . . . . . . . . . . . . . .  9
     3.2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . 10
   4  Packet format . . . . . . . . . . . . . . . . . . . . . . . . . 11
     4.1 Option format  . . . . . . . . . . . . . . . . . . . . . . . 11
     4.2 Option types . . . . . . . . . . . . . . . . . . . . . . . . 12
     4.3 Ticket format  . . . . . . . . . . . . . . . . . . . . . . . 12
   5  Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     5.1 Ticket types and ordering  . . . . . . . . . . . . . . . . . 13
     5.2 Origin application processing  . . . . . . . . . . . . . . . 14
       5.2.1 Ticket requests  . . . . . . . . . . . . . . . . . . . . 14
       5.2.2 Ticket identification  . . . . . . . . . . . . . . . . . 14
       5.2.3 Ticket use . . . . . . . . . . . . . . . . . . . . . . . 14
       5.2.4 Ticket scope . . . . . . . . . . . . . . . . . . . . . . 15
     5.3 Origin network processing  . . . . . . . . . . . . . . . . . 15
     5.4 Peer host processing . . . . . . . . . . . . . . . . . . . . 16
     5.5 Processing reflected tickets . . . . . . . . . . . . . . . . 16
       5.5.1 Network processing . . . . . . . . . . . . . . . . . . . 16
       5.5.2 Host processing  . . . . . . . . . . . . . . . . . . . . 17
Show full document text