draft-ietf-sidr-origin-validation-signaling-06.txt   draft-ietf-sidr-origin-validation-signaling-07.txt 
SIDR P. Mohapatra SIDR P. Mohapatra
Internet-Draft Sproute Networks Internet-Draft Sproute Networks
Intended status: Standards Track K. Patel Intended status: Standards Track K. Patel
Expires: May 13, 2016 Cisco Expires: May 15, 2016 Cisco
J. Scudder J. Scudder
Juniper Networks Juniper Networks
D. Ward D. Ward
Cisco Cisco
R. Bush R. Bush
Internet Initiative Japan, Inc. Internet Initiative Japan, Inc.
November 10, 2015 November 12, 2015
BGP Prefix Origin Validation State Extended Community BGP Prefix Origin Validation State Extended Community
draft-ietf-sidr-origin-validation-signaling-06 draft-ietf-sidr-origin-validation-signaling-07
Abstract Abstract
As part of the origination AS validation process, it can be desirable This document defines a new BGP opaque extended community to carry
to automatically consider the validation state of routes in the BGP the origination AS validation state inside an autonomous system.
decision process. The purpose of this document is to provide a IBGP speakers that receive this validation state can configure local
specification for doing so. The document also defines a new BGP policies allowing it to influence their decision process.
opaque extended community to carry the validation state inside an
autonomous system to influence the decision process of the IBGP
speakers.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 13, 2016. This Internet-Draft will expire on May 15, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 20 skipping to change at page 2, line 16
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
2. Origin Validation State Extended Community . . . . . . . . . 2 2. Origin Validation State Extended Community . . . . . . . . . 2
3. Deployment Considerations . . . . . . . . . . . . . . . . . . 4 3. Deployment Considerations . . . . . . . . . . . . . . . . . . 3
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
6. Security Considerations . . . . . . . . . . . . . . . . . . . 4 6. Security Considerations . . . . . . . . . . . . . . . . . . . 4
7. Normative References . . . . . . . . . . . . . . . . . . . . 4 7. Normative References . . . . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction 1. Introduction
As part of the origination AS validation process, it can be desirable This document defines a new BGP opaque extended community to carry
to automatically consider the validation state of routes in the BGP the origination AS validation state inside an autonomous system.
decision process. The purpose of this document is to provide a IBGP speakers that receive this validation state can configure local
specification for doing so. The document defines a new BGP opaque policies allowing it to influence their decision process.
extended community to carry the validation state inside an autonomous
system to influence the decision process of the IBGP speakers.
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2. Origin Validation State Extended Community 2. Origin Validation State Extended Community
The origin validation state extended community is an opaque extended The origin validation state extended community is an opaque extended
community [RFC4360] with the following encoding: community [RFC4360] with the following encoding:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x43 | TBD | Reserved | | 0x43 | 0x00 | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |validationstate| | Reserved |validationstate|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The value of the high-order octet of the extended Type Field is 0x43, The value of the high-order octet of the extended Type Field is 0x43,
which indicates it is non-transitive. The value of the low-order which indicates it is non-transitive. The value of the low-order
octet of the extended type field as assigned by IANA is 0x00. The octet of the extended type field as assigned by IANA is 0x00. The
last octet of the extended community encodes the route's validation Reserved field MUST be set to 0 and ignored upon the receipt of this
state [RFC6811]. It can assume the following values: community. The last octet of the extended community encodes the
route's validation state [RFC6811]. It can assume the following
values:
+-------+-----------------------------+ +-------+-----------------------------+
| Value | Meaning | | Value | Meaning |
+-------+-----------------------------+ +-------+-----------------------------+
| 0 | Lookup result = "valid" | | 0 | Lookup result = "valid" |
| 1 | Lookup result = "not found" | | 1 | Lookup result = "not found" |
| 2 | Lookup result = "invalid" | | 2 | Lookup result = "invalid" |
+-------+-----------------------------+ +-------+-----------------------------+
If the router is configured to support the extensions defined in this If the router is configured to support the extensions defined in this
draft, it SHOULD attach the origin validation state extended draft, it SHOULD attach the origin validation state extended
community to BGP UPDATE messages sent to IBGP peers by mapping the community to BGP UPDATE messages sent to IBGP peers by mapping the
computed validation state in the last octet of the extended computed validation state in the last octet of the extended
community. Similarly on the receiving IBGP speakers, the validation community. Similarly on the receiving IBGP speakers, the validation
state of an IBGP route SHOULD be derived directly from the last octet state of an IBGP route SHOULD be derived directly from the last octet
of the extended community, if present. of the extended community, if present.
An implementation SHOULD NOT send more than one instance of the An implementation SHOULD NOT send more than one instance of the
origin validation state extended community. However, if more than origin validation state extended community. However, if more than
one instance is received, an implementation MUST disregard all one instance is received, an implementation MUST disregard all
instances other than the one with the numerically-greatest value. If instances other than the one with the numerically-greatest validation
the value received is greater than the largest specified value (2), state value. If the value received is greater than the largest
the implementation MUST apply a strategy similar to attribute discard specified value (2), the implementation MUST apply a strategy similar
[RFC7606] by discarding the erroneous community and logging the error to attribute discard [RFC7606] by discarding the erroneous community
for further analysis. and logging the error for further analysis.
By default, implementations SHOULD drop the origin validation state By default, implementations SHOULD drop the origin validation state
extended community if received from an EBGP peer, without further extended community if received from an EBGP peer, without further
processing it. However an implementation MAY be configured to accept processing it. However an implementation MAY be configured to accept
the community when warranted, for example when the EBGP session is to the community when warranted, for example when the EBGP session is to
a neighbor AS under control of the same administration. Similarly, a neighbor AS under control of the same administration. Similarly,
an implementation SHOULD NOT send the community to EBGP peers but MAY an implementation SHOULD NOT send the community to EBGP peers but MAY
be configured to do so if warranted. be configured to do so if warranted.
3. Deployment Considerations 3. Deployment Considerations
 End of changes. 11 change blocks. 
27 lines changed or deleted 24 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/