BGPsec Validation State Signaling
draft-sidrops-bgpsec-validation-signaling-01
Internet Engineering Task Force (IETF) O. Borchert
Internet-Draft D. Montgomery
Updates: 8097 (if approved) USA NIST
Intended status: Standards Track D. Kopp
Expires: May 21, 2020 DE-IX
November 18, 2019
BGPsec Validation State Signaling
draft-sidrops-bgpsec-validation-signaling-01
Abstract
This document updates RFC 8097 by adding the BGPsec path validation
state to the reserved portion of the extended community in RFC 8097.
BGP speakers that receive this community string can use the embedded
BGPsec validation state and configure local policies that allow it
being used to influence their decision process. This is especially
helpful because Section 5 of RFC 8205 specifically allows putting
BGPsec path validation temporarily on hold. This allows reducing the
load of validation particularly from IBGP learned routes or EBGP
learned routes when warranted.
Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Borchert, et al. Expires May 21, 2020 [Page 1]
Internet Draft BGPsec Validation State Signaling November 18, 2019
Copyright Notice
Copyright (c) 2019 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
(http://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 Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Suggested Reading . . . . . . . . . . . . . . . . . . . . . . 3
3. Validation State Extended Community . . . . . . . . . . . . . 3
3.1. Error Handling at Peers . . . . . . . . . . . . . . . . . . 4
3.2. Backwards Compatibility to RFC8097 . . . . . . . . . . . . 4
4. Deployment Considerations . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
6.1. Normative References . . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . . 7
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
This document updates the BGP non-transitive extended community as
specified in RFC 8097 to also carry BGPsec path validation state
information. BGP speakers that receive this community string can be
used used to configure local policies that use the signaled BGPsec
path validation state to influence their decision process. When used
in IBGP sessions, this new community can result in significant
reduction in the computational load imposed by BGPsec path
validation. When used in EBGP sessions, the new community can
provide utility to receivers that are unable to perform BGPsec
validation for themselves or put it temporarily on hold as specified
in [RFC8205] (Section 5) as well as provides important diagnostic
information about a peer's validation process.
Borchert, et al. Expires May 21, 2020 [Page 2]
Internet Draft BGPsec Validation State Signaling November 18, 2019
1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text