Encoding Routing in Firewall and Service Tickets
draft-herbert-route-fast-00

Document Type Active Internet-Draft (individual)
Last updated 2018-10-10
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: Informational                                Quantonium
Expires: April 2019                                                     
                                                                        
                                                        October 10, 2018

            Encoding Routing in Firewall and Service Tickets
                      draft-herbert-route-fast-00

Abstract

   This document describes a method to encode routing information in
   Firewall and Service Tickets (FAST). Encoded routing information
   provides the local routing for packets sent in either the forward or
   return paths of a flow. FAST ticket reflection at peer hosts ensures
   that the routing information is attached to packets being sent in the
   return path. When a packet with a FAST ticket containing routing
   information enters the network in which the ticket was issued, the
   ticket is parsed to extract the routing information and is forwarded
   per the information. Routing in Firewall and Service Tickets has a
   number of use cases. It can be used as a type of source routing, used
   with identifier-locator protocols to provide a locator in the return
   path, and can be used to specify a backend instance in Layer 4 load
   balancing for processing connections to a virtual IP address. 

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

 

T. Herbert               Expires April 13, 2019                 [Page 1]
INTERNET DRAFT        draft-herbert-route-fast-00       October 10, 2018

Copyright and License Notice

   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  Background and motivation . . . . . . . . . . . . . . . . . . .  4
     2.1 Problem statement  . . . . . . . . . . . . . . . . . . . . .  4
     2.2 Firewall and Service Tickets . . . . . . . . . . . . . . . .  4
     2.3  Similar efforts . . . . . . . . . . . . . . . . . . . . . .  5
       2.3.1 Segment routing  . . . . . . . . . . . . . . . . . . . .  5
       2.3.2 hICN mobility proposal . . . . . . . . . . . . . . . . .  5
     2.4 Use cases  . . . . . . . . . . . . . . . . . . . . . . . . .  6
       2.4.1 Identifier-locator protocols and virtualization  . . . .  6
       2.4.2 Segment routing  . . . . . . . . . . . . . . . . . . . .  6
       2.4.3 Layer 4 load balancing . . . . . . . . . . . . . . . . .  7
   3  Solution Overview . . . . . . . . . . . . . . . . . . . . . . .  8
     3.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . .  8
     3.2 Reference Topology . . . . . . . . . . . . . . . . . . . . .  9
     3.3 Basic packet flow  . . . . . . . . . . . . . . . . . . . . . 10
   4  Firewall and Service Tickets encoding . . . . . . . . . . . . . 11
     4.1 ILA locator encoding . . . . . . . . . . . . . . . . . . . . 12
     4.2 Locator index encoding . . . . . . . . . . . . . . . . . . . 12
   5  Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     5.1 Ticket requests  . . . . . . . . . . . . . . . . . . . . . . 13
     5.2 Qualified locators . . . . . . . . . . . . . . . . . . . . . 13
       5.2.1 Fully qualified locators . . . . . . . . . . . . . . . . 14
       5.2.2 Unqualified locators . . . . . . . . . . . . . . . . . . 14
     5.3 First hop router processing  . . . . . . . . . . . . . . . . 14
     5.4 Transit to the peer  . . . . . . . . . . . . . . . . . . . . 14
Show full document text