The Requirements for Secure Routing

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.¶

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

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;¶

2. Requirements for Secure Routing

3. IANA Considerations

This memo includes no request to IANA.¶

4. Security Considerations

TBD¶

Authors' Addresses