draft-ietf-sidr-origin-validation-signaling-08.txt   draft-ietf-sidr-origin-validation-signaling-09.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: June 16, 2016 Cisco Expires: December 29, 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.
December 14, 2015 June 27, 2016
BGP Prefix Origin Validation State Extended Community BGP Prefix Origin Validation State Extended Community
draft-ietf-sidr-origin-validation-signaling-08 draft-ietf-sidr-origin-validation-signaling-09
Abstract Abstract
This document defines a new BGP opaque extended community to carry This document defines a new BGP opaque extended community to carry
the origination AS validation state inside an autonomous system. the origination AS validation state inside an autonomous system.
IBGP speakers that receive this validation state can configure local IBGP speakers that receive this validation state can configure local
policies allowing it to influence their decision process. policies allowing it to influence their decision process.
Status of This Memo Status of This Memo
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 June 16, 2016. This Internet-Draft will expire on December 29, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
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
skipping to change at page 3, line 46 skipping to change at page 3, line 46
and logging the error 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. Similarly, by default an implementation SHOULD NOT processing it. Similarly, by default an implementation SHOULD NOT
send the community to EBGP peers. However it SHOULD be possible to send the community to EBGP peers. However it SHOULD be possible to
configure an implementation to send or accept the community when configure an implementation to send or accept the community when
warranted. An example of a case where the community would reasonably warranted. An example of a case where the community would reasonably
be received from, or sent to, an EBGP peer is when two adjacent ASes be received from, or sent to, an EBGP peer is when two adjacent ASes
are under control of the same administration. A second example is are under control of the same administration. A second example is
documented in [I-D.kklf-sidr-route-server-rpki-light]. documented in [I-D.ietf-sidr-route-server-rpki-light].
3. Deployment Considerations 3. Deployment Considerations
In deployment scenarios where not all the speakers in an autonomous In deployment scenarios where not all the speakers in an autonomous
system are upgraded to support the extensions defined in this system are upgraded to support the extensions defined in this
document, it is necessary to define policies that match on the origin document, it is necessary to define policies that match on the origin
validation extended community and set another BGP attribute [RFC6811] validation extended community and set another BGP attribute [RFC6811]
that influences the best path selection the same way as what would that influences the best path selection the same way as what would
have been enabled by an implementation of this extension. have been enabled by an implementation of this extension.
4. Acknowledgements 4. Acknowledgements
The authors would like to acknowledge the valuable review and The authors would like to acknowledge the valuable review and
suggestions from Wesley George, Roque Gagliano and Bruno Decraene on suggestions from Wesley George, Roque Gagliano and Bruno Decraene on
this document. this document.
5. IANA Considerations 5. IANA Considerations
IANA has assigned a value 0x00 from the "BGP Opaque Extended IANA has assigned the value 0x00 from the "Non-Transitive Opaque
Community" type registry in the non-transitive range, which is called Extended Community Sub-Types" registry. The value is called "BGP
"BGP Origin Validation State Extended Community". Origin Validation State Extended Community".
6. Security Considerations 6. Security Considerations
This document introduces no new security concerns beyond what is This document introduces no new security concerns beyond what is
described in [RFC6811]. described in [RFC6811].
7. References 7. References
7.1. Normative References 7.1. Normative References
skipping to change at page 5, line 7 skipping to change at page 5, line 7
DOI 10.17487/RFC6811, January 2013, DOI 10.17487/RFC6811, January 2013,
<http://www.rfc-editor.org/info/rfc6811>. <http://www.rfc-editor.org/info/rfc6811>.
[RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K. [RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K.
Patel, "Revised Error Handling for BGP UPDATE Messages", Patel, "Revised Error Handling for BGP UPDATE Messages",
RFC 7606, DOI 10.17487/RFC7606, August 2015, RFC 7606, DOI 10.17487/RFC7606, August 2015,
<http://www.rfc-editor.org/info/rfc7606>. <http://www.rfc-editor.org/info/rfc7606>.
7.2. Informative References 7.2. Informative References
[I-D.kklf-sidr-route-server-rpki-light] [I-D.ietf-sidr-route-server-rpki-light]
King, T., Kopp, D., Lambrianidis, A., and A. Fenioux, King, T., Kopp, D., Lambrianidis, A., and A. Fenioux,
"Signaling RPKI Validation Results from a Route-Server to "Signaling Prefix Origin Validation Results from a Route-
Peers", draft-kklf-sidr-route-server-rpki-light-00 (work Server to Peers", draft-ietf-sidr-route-server-rpki-
in progress), December 2015. light-00 (work in progress), June 2016.
Authors' Addresses Authors' Addresses
Pradosh Mohapatra Pradosh Mohapatra
Sproute Networks Sproute Networks
Email: mpradosh@yahoo.com Email: mpradosh@yahoo.com
Keyur Patel Keyur Patel
Cisco Cisco
 End of changes. 9 change blocks. 
13 lines changed or deleted 13 lines changed or added

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