Security Considerations for SRv6 Networks
draft-li-spring-srv6-security-consideration-04

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04

Spring                                                             C. Li
Internet-Draft                                                     Z. Li
Intended status: Informational                                    Huawei
Expires: November 10, 2020                                        C. Xie
                                                           China Telecom
                                                                 H. Tian
                                                                   CAICT
                                                                  J. Mao
                                                                  Huawei
                                                             May 9, 2020

               Security Considerations for SRv6 Networks
             draft-li-spring-srv6-security-consideration-04

Abstract

   SRv6 inherits potential security vulnerabilities from Source Routing
   in general, and also from IPv6.  This document describes various
   threats and security concerns related to SRv6 networks and existing
   approaches to solve these threats.

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 November 10, 2020.

Copyright Notice

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

Li, et al.              Expires November 10, 2020               [Page 1]
Internet-Draft        SRv6 Security Considerations              May 2020

   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
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   3.  Security Principles of SRv6 Networking  . . . . . . . . . . .   4
   4.  Types of Vulnerabilities in SR Networks . . . . . . . . . . .   4
     4.1.  Eavesdropping Vulnerabilities in SRv6 Networks  . . . . .   4
     4.2.  Packet Falsification in SRv6 Networks . . . . . . . . . .   5
     4.3.  Identity Spoofing in SRv6 Networks  . . . . . . . . . . .   6
     4.4.  Packet Replay in SRv6 Networks  . . . . . . . . . . . . .   7
     4.5.  DOS/DDOS in SRv6 Networks . . . . . . . . . . . . . . . .   7
     4.6.  Malicious Packet Data in SRv6 Networks  . . . . . . . . .   8
   5.  Effects of the above on SRv6 Use Cases  . . . . . . . . . . .   8
   6.  Security Policy Design  . . . . . . . . . . . . . . . . . . .   8
     6.1.  Basic Security Design . . . . . . . . . . . . . . . . . .   9
       6.1.1.  ACL for External Interfaces . . . . . . . . . . . . .   9
       6.1.2.  ACL for Internal Interfaces . . . . . . . . . . . . .   9
       6.1.3.  SID Instantiation . . . . . . . . . . . . . . . . . .   9
     6.2.  Enhanced Security Design  . . . . . . . . . . . . . . . .  10
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   Segment Routing (SR) [RFC8402] is a source routing paradigm that
   explicitly indicates the forwarding path for packets at the source
   node by inserting an ordered list of instructions, called segments.
   A segment can represent a topological or service-based instruction.

   When segment routing is deployed on IPv6 [RFC8200] dataplane, called
   SRv6 [RFC8754], a segment is a 128 bit value, and can the IPv6
   address of a local interface but it does not have to.  For supporting
   SR, a new type of Routing Extension Header is defined and called the