Skip to main content

The Requirements for Secure Routing
draft-chen-secure-routing-requirements-01

Document Type Active Internet-Draft (individual)
Authors chenmeiling , Li Su
Last updated 2023-03-09
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-chen-secure-routing-requirements-01
Internet Engineering Task Force                                Chen, Ed.
Internet-Draft                                                     L. Su
Intended status: Informational                              China Mobile
Expires: 10 September 2023                                  9 March 2023

                  The Requirements for Secure Routing
               draft-chen-secure-routing-requirements-01

Abstract

   Both ISPs and users have put forward requirements for secure routing,
   the scenarios are analyzed in the draft draft-chen-secure-routing-
   use-cases.  This draft analyzes the functions required to implement
   secure routing.

   Attack detection and users security requirements translateion are out
   of scope.

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 10 September 2023.

Copyright Notice

   Copyright (c) 2023 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Chen & Su               Expires 10 September 2023               [Page 1]
Internet-Draft                Requirements                    March 2023

   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 Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements for Secure Routing . . . . . . . . . . . . . . .   3
     2.1.  Appraise trustworthiness  . . . . . . . . . . . . . . . .   3
     2.2.  Expression of security capability . . . . . . . . . . . .   3
     2.3.  Type of security functions  . . . . . . . . . . . . . . .   3
     2.4.  Node security capability collection protocol  . . . . . .   3
     2.5.  Distribution of security policy . . . . . . . . . . . . .   3
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   3

1.  Introduction

   Starting from the requirements of network operators and users, it is
   necessary to take the security attribute as the key factor to select
   the route and transmission path to measure the link transmission
   security.  To achieve this goal, the following contents need to be
   studied.

   1.  Static node security, by appraising the trustworthiness;

   2.  Expression of node security capability, by YANG Model;

   3.  Type of security functions: reorganize and define the security
       functions supported by existing network devices, and encode them,
       such as security monitoring, traffic filtering.  Generally, the
       security functions of a device can be described as a collection.

   4.  Protocol for collecting node security capabilities, such as
       adding new parameters to BGP-LS;

   5.  A protocol for distributing security policy configuration, by
       SRv6;

Chen & Su               Expires 10 September 2023               [Page 2]
Internet-Draft                Requirements                    March 2023

2.  Requirements for Secure Routing

2.1.  Appraise trustworthiness

   TBD

2.2.  Expression of security capability

   YANG model is used to describe the security capability of nodes, such
   as security service type and remaining capacity.

2.3.  Type of security functions

   Fine-grained security functions, more detail in draft draft-chen-
   atomized-security-functions.

2.4.  Node security capability collection protocol

   Collect the security capabilities of all nodes in the network through
   BGP-LS, more detail in draft draft-chen-idr-bgp-ls-security-
   capability.

2.5.  Distribution of security policy

   Security policies can be distributed through extended SRv6 SRH.

3.  IANA Considerations

   This memo includes no request to IANA.

4.  Security Considerations

   TBD

Authors' Addresses

   Meiling Chen (editor)
   China Mobile
   BeiJing
   China
   Email: chenmeiling@chinamobile.com

   Li Su
   China Mobile
   BeiJing
   China
   Email: suli@chinamobile.com

Chen & Su               Expires 10 September 2023               [Page 3]