Internet DRAFT - draft-richardson-nasr-terminology
draft-richardson-nasr-terminology
anima Working Group M. Richardson
Internet-Draft Sandelman Software Works
Intended status: Standards Track C. Liu
Expires: 29 August 2024 Huawei Technologies
26 February 2024
Terminology and Use cases for Secured Routing Infrastructure
draft-richardson-nasr-terminology-00
Abstract
This document collects terminology and use cases for Secured Routing.
About This Document
This note is to be removed before publishing as an RFC.
Status information for this document may be found at
https://datatracker.ietf.org/doc/draft-richardson-nasr-terminology/.
Discussion of this document takes place on the nasr Working Group
mailing list (mailto:nasr@ietf.org), which is archived at
https://mailarchive.ietf.org/arch/browse/nasr/. Subscribe at
https://www.ietf.org/mailman/listinfo/nasr/.
Source for this draft and an issue tracker can be found at
https://github.com/mcr/nasr-terminology.
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 29 August 2024.
Richardson & Liu Expires 29 August 2024 [Page 1]
Internet-Draft nasr-names February 2024
Copyright Notice
Copyright (c) 2024 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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3
7. Changelog . . . . . . . . . . . . . . . . . . . . . . . . . . 3
8. Normative References . . . . . . . . . . . . . . . . . . . . 3
Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction
This document collects terminology in use for various secured routing
efforts.
In addition, it may collect use cases that explain the terminology.
This documents is not intended to ever be published.
2. Terminology
Although this document is not an IETF Standards Track publication, it
adopts the conventions for normative language to provide clarity of
instructions to the implementer. The key words "MUST", "MUST NOT",
"REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
"RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14 [RFC2119]
[RFC8174] when, and only when, they appear in all capitals, as shown
here.
Secure routing: A abstract term that applies to all of the various
Richardson & Liu Expires 29 August 2024 [Page 2]
Internet-Draft nasr-names February 2024
work at both control plane and forwarding plane.
Path Validation: an examination of control plane messages (such as
BGP) to validate that the planned route is correct.
Proof of Transit: an examination of data plane messages to provide
evidence that the planned route was the one used
Planned Route: unsure
3. Use Cases
TBD
4. Security Considerations
Just words, no protocols in this document.
5. IANA Considerations
This document makes no requests to IANA.
6. Acknowledgements
Hello.
7. Changelog
8. Normative References
[BCP14] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/rfc/rfc8174>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/rfc/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/rfc/rfc8174>.
Contributors
Meiling Chen
Richardson & Liu Expires 29 August 2024 [Page 3]
Internet-Draft nasr-names February 2024
Authors' Addresses
Michael Richardson
Sandelman Software Works
Email: mcr+ietf@sandelman.ca
Chunchi (Peter) Liu
Huawei Technologies
Email: liuchunchi@huawei.com
Richardson & Liu Expires 29 August 2024 [Page 4]
