%% You should probably cite draft-chen-secure-routing-use-cases-03 instead of this revision.
@techreport{chen-secure-routing-use-cases-02,
    number =    {draft-chen-secure-routing-use-cases-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-chen-secure-routing-use-cases/02/},
    author =    {Meiling Chen and Li Su and BO YANG},
    title =     {{The Use Cases for Secure Routing}},
    pagetotal = 8,
    year =      2023,
    month =     mar,
    day =       13,
    abstract =  {Current routing mechanism is based on the shortest path, which only take the link status and the path accessibility into consideration, without the security of links and forwarding nodes. As security has become an important factor to the user. This paper proposes to add security factor in the routing process. With the frequent occurrence of security incidents, services security is an essential demand for the users. As there are many security devices in the ISP's network, this draft proposes secure routing mechanism. The purpose of secure routing is to converge security and routing to ensure the secure data transmission. The scope is transmission process security, while end-to-end security and application layer security are out of scope.},
}