Simplifying Firewall Rules with Network Programming and SRH Metadata
draft-guichard-spring-srv6-simplified-firewall-00

Document Type Active Internet-Draft (individual)
Last updated 2019-03-25
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
SPRING                                                  J. Guichard, Ed.
Internet-Draft                                                    Huawei
Intended status: Informational                               C. Filsfils
Expires: September 26, 2019                          Cisco Systems, Inc.
                                                              D. Bernier
                                                             Bell Canada
                                                                   Z. Li
                                                     Huawei Technologies
                                                            F. Clad, Ed.
                                                            P. Camarillo
                                                           A. AbdelSalam
                                                     Cisco Systems, Inc.
                                                          March 25, 2019

  Simplifying Firewall Rules with Network Programming and SRH Metadata
           draft-guichard-spring-srv6-simplified-firewall-00

Abstract

   A clear application of the SRv6 Network Programming model consists in
   steering, in a stateless manner, packets through a Service Function
   Chain (SFC).  Each Service Function (SF) is identified by a segment.
   Each SF can enrich its operation thanks to metadata present in the
   SRH.

   This document describes a practical use-case where the SF is a
   firewall and the metadata helps to drastically decrease the number of
   rules that need to be maintained by the operation team.

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 September 26, 2019.

Guichard, et al.       Expires September 26, 2019               [Page 1]
Internet-Draft          SRv6 Simplified Firewall              March 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Use-case overview . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Demo availability . . . . . . . . . . . . . . . . . . . . . .   5
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The Segment Routing architecture is defined in [RFC8402].

   The IPv6 instantiation of Segment Routing, also known as SRv6,
   leverages the Segment Routing Header (SRH) defined in
   [I-D.ietf-6man-segment-routing-header] to encode a list of segments,
   as well as some complementary information in an IPv6 header.
   [I-D.filsfils-spring-srv6-network-programming] builds upon the base
   SRv6 definition and introduces the concept of network programming.
   In a sense, the list of segments in the SRH is the source code of a
   network program, while the SRH TLVs represent the memory of that
   program.

   Furthermore, [I-D.xuclad-spring-sr-service-programming] describes how
   segments can be associated with Service Functions and defines SRH
   TLVs specifically designed for carrying service metadata.  Together,
   these documents define an integrated solution for underlay, overlay
   and SFC that uses a single header and does not require any per-flow
   state in the network fabric.

Guichard, et al.       Expires September 26, 2019               [Page 2]
Show full document text