]> Sandelman Software Works

mcr+ietf@sandelman.ca

Huawei Technologies

liuchunchi@huawei.com

Internet anima Working Group Internet-Draft This document collects terminology and use cases for Secured Routing. About This Document Status information for this document may be found at . Discussion of this document takes place on the nasr Working Group mailing list (), which is archived at . Subscribe at . Source for this draft and an issue tracker can be found at .

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.

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 when, and only when, they appear in all capitals, as shown here.

Secure routing:

A abstract term that applies to all of the various 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

Use Cases TBD

Security Considerations Just words, no protocols in this document.

IANA Considerations This document makes no requests to IANA.

Acknowledgements Hello.

Changelog

Normative References RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.

Contributors