Receive-Only Service Function and External Service in SFC
draft-wang-sfc-receive-only-01

Document Type Active Internet-Draft (individual)
Last updated 2016-10-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)
Service Function Chaining                                        E. Wang
Internet-Draft                                                  K. Leung
Intended status: Informational                        Cisco Systems Inc.
Expires: April 28, 2017                                 October 25, 2016

       Receive-Only Service Function and External Service in SFC
                     draft-wang-sfc-receive-only-01

Abstract

   A category of services such as Intrusion Detection Service and Packet
   Capture operates in "receive-only" mode.  They are "packet sinks"
   which consume all packets sent to them.  This document describes the
   proposals for such service to be part of the Service Function
   Chaining framework.

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 http://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 April 23, 2017.

Copyright Notice

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

Wang & Leung             Expires April 23, 2017                 [Page 1]
Internet-Draft              SFC Receive-only                October 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Definition Of Terms . . . . . . . . . . . . . . . . . . . . .   3
   3.  Receive-Only Service Function vs. External Service  . . . . .   3
   4.  SFC Packet Plane  . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Receive-Only Service Function . . . . . . . . . . . . . .   6
     4.2.  Receive-Only External Service . . . . . . . . . . . . . .   9
   5.  SFC Control Plane . . . . . . . . . . . . . . . . . . . . . .  12
     5.1.  Receive-Only Service Function . . . . . . . . . . . . . .  12
     5.2.  Receive-Only External Service . . . . . . . . . . . . . .  12
   6.  SFC Element Considerations  . . . . . . . . . . . . . . . . .  13
     6.1.  Receive-Only Service Function . . . . . . . . . . . . . .  13
     6.2.  Extended SFC Proxy  . . . . . . . . . . . . . . . . . . .  14
     6.3.  Receive-Only External Service . . . . . . . . . . . . . .  14
     6.4.  Service Function Forwarder  . . . . . . . . . . . . . . .  14
       6.4.1.  Receive-Only Service Function . . . . . . . . . . . .  14
       6.4.2.  Receive-Only External Service . . . . . . . . . . . .  14
       6.4.3.  SFF Capabilities Considerations . . . . . . . . . . .  15
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  16
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  16
     10.2.  Informative References . . . . . . . . . . . . . . . . .  17
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   Services in Service Function Chaining (SFC) usually operate in
   "inline" mode, where they process the received packets and return the
   packets to the Service Function Forwarder (SFF).  Some services
   especially in the network security domain can buffer, inject or block
   certain packets, as well as proxy entire connections
   ([I-D.wang-sfc-ns-use-cases]).  However, in general they still
   forward packets.

   [I-D.wang-sfc-ns-use-cases] also describes a special set of services
   that consume all packets sent to them.  We refer to such behavior as
   "receive-only".  A receive-only service could be a Service Function
Show full document text