An Experiment of SRv6 Service Chaining at Interop Tokyo 2019 ShowNet
draft-upa-srv6-service-chaining-exp-00

Document Type Active Internet-Draft (individual)
Last updated 2019-10-31
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
On Agenda spring at IETF-106
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
SPRING                                                  R. Nakamura, Ed.
Internet-Draft                                   The University of Tokyo
Intended status: Informational                                   Y. Ueno
Expires: May 2, 2020                      NTT Communications Corporation
                                                               T. Kamata
                                                     Cisco Systems, Inc.
                                                        October 30, 2019

  An Experiment of SRv6 Service Chaining at Interop Tokyo 2019 ShowNet
                 draft-upa-srv6-service-chaining-exp-00

Abstract

   This document reports lessons learned from an experimental deployment
   of service chaining with Segment Routing over the IPv6 data plane
   (SRv6) at an event network.  The service chaining part of the network
   was comprised of four SRv6-capable nodes (three products from
   different vendors), five SRv6 proxy nodes (two products from
   different vendors and three open source software), and six services.
   This network was deployed at Interop Tokyo 2019, and it successfully
   provided network connectivity and services to all the exhibitors and
   visitors on the event.

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 May 2, 2020.

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

Nakamura, et al.           Expires May 2, 2020                  [Page 1]
Internet-Draft    SRv6 Service Chaining in ShowNet 2019     October 2019

   (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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  SRv6 service chaining at Interop Tokyo 2019 ShowNet . . . . .   3
   4.  Lessons Learned . . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Transparency of SRv6 header . . . . . . . . . . . . . . .   5
     4.2.  Services that cannot co-exist with End.AM . . . . . . . .   6
     4.3.  Service liveness detection and conditional advertisement
           of service segments . . . . . . . . . . . . . . . . . . .   6
     4.4.  TTL Decrement on SRv6 Proxies . . . . . . . . . . . . . .   6
     4.5.  Control Plane Capabilities  . . . . . . . . . . . . . . .   7
     4.6.  Match Condition for Applying SRv6 Functions . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   8
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   Standardizing functionalities for SRv6 service programming is still
   an ongoing agenda.  Meanwhile, some fundamental parts have begun to
   be implemented: basic transit behaviors, endpoint functions at
   ingress and egress nodes
   [I-D.filsfils-spring-srv6-network-programming], and SR proxies for
   SR-unaware services [I-D.ietf-spring-sr-service-programming].  Trying
   out such running codes and devices would clarify statuses of recent
   implementations and provide feedback to current and future
   standardization processes.

   To clarify the current status, we conducted an experiment of SRv6
   service chaining at Interop Tokyo.  Interop Tokyo is a large
   exhibition of networking technologies, and ShowNet is the event
   network built at Interop Tokyo while demonstrating new technologies
   and conducting interoperability tests.  In 2019, we deployed SRv6
   service chaining with the latest implementations at ShowNet and
Show full document text