draft-ietf-sidr-origin-validation-signaling-05.txt   draft-ietf-sidr-origin-validation-signaling-06.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 7, 2016 Cisco Expires: May 13, 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 4, 2015 November 10, 2015
BGP Prefix Origin Validation State Extended Community BGP Prefix Origin Validation State Extended Community
draft-ietf-sidr-origin-validation-signaling-05 draft-ietf-sidr-origin-validation-signaling-06
Abstract Abstract
As part of the origination AS validation process, it can be desirable As part of the origination AS validation process, it can be desirable
to automatically consider the validation state of routes in the BGP to automatically consider the validation state of routes in the BGP
decision process. The purpose of this document is to provide a decision process. The purpose of this document is to provide a
specification for doing so. The document also defines a new BGP specification for doing so. The document also defines a new BGP
opaque extended community to carry the validation state inside an opaque extended community to carry the validation state inside an
autonomous system to influence the decision process of the IBGP autonomous system to influence the decision process of the IBGP
speakers. speakers.
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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 7, 2016. This Internet-Draft will expire on May 13, 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 3, line 32 skipping to change at page 3, line 32
| 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. state of an IBGP route SHOULD be derived directly from the last octet
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 value. If
the value received is greater than the largest specified value (2), the value received is greater than the largest specified value (2),
the implementation MUST apply a strategy similar to attribute discard the implementation MUST apply a strategy similar to attribute discard
[RFC7606] by discarding the erroneous community and logging the error [RFC7606] by discarding the erroneous community and logging the error
for further analysis. for further analysis.
 End of changes. 5 change blocks. 
5 lines changed or deleted 6 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/