<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.6.26 (Ruby 3.0.2) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-chen-secure-routing-requirements-01" category="info" submissionType="IETF" xml:lang="en" version="3">
  <!-- xml2rfc v2v3 conversion 3.16.0 -->
  <front>
    <title abbrev="Requirements">The Requirements for Secure Routing</title>
    <seriesInfo name="Internet-Draft" value="draft-chen-secure-routing-requirements-01"/>
    <author initials="" surname="Chen" fullname="Meiling Chen" role="editor">
      <organization>China Mobile</organization>
      <address>
        <postal>
          <city>BeiJing</city>
          <country>China</country>
        </postal>
        <email>chenmeiling@chinamobile.com</email>
      </address>
    </author>
    <author initials="L." surname="Su" fullname="Li Su">
      <organization>China Mobile</organization>
      <address>
        <postal>
          <city>BeiJing</city>
          <country>China</country>
        </postal>
        <email>suli@chinamobile.com</email>
      </address>
    </author>
    <date year="2023" month="March" day="09"/>
    <area>Security</area>
    <workgroup>Internet Engineering Task Force</workgroup>
    <keyword>Internet-Draft</keyword>
    <keyword>keyword2</keyword>
    <abstract>
      <t>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.</t>
      <t>Attack detection and users security requirements translateion are out of scope.</t>
    </abstract>
  </front>
  <middle>
    <section anchor="introduction">
      <name>Introduction</name>
      <t>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.</t>
      <ol spacing="normal" type="1"><li>Static node security, by appraising the trustworthiness;</li>
        <li>Expression of node security capability, by YANG Model;</li>
        <li>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.</li>
        <li>Protocol for collecting node security capabilities, such as adding new parameters to BGP-LS;</li>
        <li>A protocol for distributing security policy configuration, by SRv6;</li>
      </ol>
    </section>
    <section anchor="requirements-for-secure-routing">
      <name>Requirements for Secure Routing</name>
      <section anchor="appraise-trustworthiness">
        <name>Appraise trustworthiness</name>
        <t>TBD</t>
      </section>
      <section anchor="expression-of-security-capability">
        <name>Expression of security capability</name>
        <t>YANG model is used to describe the security capability of nodes, such as security service type and remaining capacity.</t>
      </section>
      <section anchor="type-of-security-functions">
        <name>Type of security functions</name>
        <t>Fine-grained security functions, more detail in draft draft-chen-atomized-security-functions.</t>
      </section>
      <section anchor="node-security-capability-collection-protocol">
        <name>Node security capability collection protocol</name>
        <t>Collect the security capabilities of all nodes in the network through BGP-LS, more detail in draft draft-chen-idr-bgp-ls-security-capability.</t>
      </section>
      <section anchor="distribution-of-security-policy">
        <name>Distribution of security policy</name>
        <t>Security policies can be distributed through extended SRv6 SRH.</t>
      </section>
    </section>
    <section anchor="IANA">
      <name>IANA Considerations</name>
      <t>This memo includes no request to IANA.</t>
    </section>
    <section anchor="Security">
      <name>Security Considerations</name>
      <t>TBD</t>
    </section>
  </middle>
  <back>







  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA61WTW8bNxC9C9B/GEBX7UJR2gJRLpU/myIxjMiXngpqyZUI
ccktyZWsFPnveUNqZckfzaWwYVjkfLx582aooiiGgxCFlX8L46yaUfSdGg50
69O/IU4nkw+T6XBQiTgjbWtHI7pcq2oDv27Z6BC0s3HfwvXT9cPNcCC8EjNa
qKrzOu6Hg90KNzYqb1Wka7vSVimv7YoeRNjQjfMV8g0H0lVWNIgivahjUa2V
LQIHUYV3XYRD4dU/nfaqUTaGYvKOvaKOBj4Pa0VfT26pdj5DwHn2BrDl0qvt
7MxwODDCAqCyw8FmNxsOiIoj2uKKoeSzjdrvnJcgYkRSROScTqbviwl+P1BR
pDPSSKyNURJEkeiia0TUlTBmT8s9PTZm6uuKdE3WRVrpLWeF2dp5ZC7IO65F
SR2BfkSA6LaqN899IUQOM26A5Q+ZsS9KGya0P3V+xSbaCvriltokvwrNmNGF
0n8mMnDgOhv9/mDJJ6oR2syIqW9yyN8rvmtSkLJyDaPMOT9rWnT/Q7LQGf0y
C/KAU7EM0Ysq8ucLF9f0aXEfCFqlLigfaC1AT9tF7vZOeEn+uQSygOggoDFF
6CRUygqvHSLhSlhh9t9yx/g2qe8/NIjMRSWCCiVEh35n+0OUkELUna0ihiL0
eCRFR7ppTUL2DFTJ1c1jFNWGpIoquZ4UGQ6DdF4ceLHBQHPJGNEQjFyN4lyr
yp7ARktp0nSNWNTeyS6F55NFFJ7zU+1dk3CfJUAsTAAkvyFE9AKSPKF+TDqy
2q2qVAjC77nCKDYqM9xDFjF6vewwGSJTgymiGh1Fa+AQlEG5ObdLVoifKjus
FWoFug7LRonAnLEpdLk5t+rzoSWOBMSktmwKfCsnTO567YxxO663wrpKJQJ9
bs0SkGMntZKJuXclgRwMLuZOPlUz5hkWbeuFDhyHo6YNCZKQzIKIj8PBtKTr
x9arjIxZPI1BlWgFZN6H+2t+d4uxkcrA9T3wY4+mNvb2Ry3N0B6MmrD6W+ZJ
qho5z/l+Ul7o2hawUB+yqEcdUqv7jkq11WjcOAVStmKICNSM4VetuVnHkI2z
vI7y9EDrNWjBjotphZd0qyzEgQU3fgsJqhGHhKjeMtlShQq6ADhkEmiIMVn2
oP+Xku69iw6HaYL7S0b/OpOaC+lxCylzoTtox2NTRZ4h9Pji9r74vADLv5Y0
p/Y0hQQ7SabseYzfOqOrPaul1qsOAwB8qWeLr9vfPrJOeKp++ujAaETzrJoX
euHrh4urg9W5bl6RDNslxTSsGJ4/DGNScM/oeROePHshhlc6jHlOzeE3PAnC
82q2aVQQgFd5eUD4tjzZ4AY1FSsUagHqpckYsD03P2Lx87p9sWqxZBrIWxa9
c3F07hHcvTFNJyI6NpddLvPxG7xAOkmfxmR2+kegn5O4xl5arQ/i+XkBWvpi
uWoLE55KeMLY13B11NuzTmfJpeV8dsQw+9HpfbnvB3TqEftM4oCViT9/lFmd
h70/v5vTJSjUUmUVB/p3xKffk/x4TTb4poGCKtMxCdalp0CFyNJiy5L6aEdg
LyL2N99PRJ1foaXgL4v55wdqkIhEcAoAAA==

-->

</rfc>
