draft-ietf-sidrops-ov-clarify-00.txt   draft-ietf-sidrops-ov-clarify-01.txt 
Network Working Group R. Bush Network Working Group R. Bush
Internet-Draft Internet Initiative Japan Internet-Draft Internet Initiative Japan
Intended status: Standards Track October 20, 2017 Intended status: Standards Track April 19, 2018
Expires: April 23, 2018 Expires: October 21, 2018
Origin Validation Clarifications Origin Validation Clarifications
draft-ietf-sidrops-ov-clarify-00 draft-ietf-sidrops-ov-clarify-01
Abstract Abstract
Deployment of RPKI-based BGP origin validation is hampered by, among Deployment of RPKI-based BGP origin validation is hampered by, among
other things, vendor mis-implementations in two critical areas, which other things, vendor mis-implementations in two critical areas, which
routes are validated and whether policy is applied when not specified routes are validated and whether policy is applied when not specified
by configuration. This document is meant to clarify possible by configuration. This document is meant to clarify possible
misunderstandings causing those mis-implementations. misunderstandings causing those mis-implementations.
Requirements Language Requirements Language
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 April 23, 2018. This Internet-Draft will expire on October 21, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 2, line 42 skipping to change at page 2, line 42
operator configuration. operator configuration.
2. Suggested Reading 2. Suggested Reading
It is assumed that the reader understands BGP, [RFC4271], the RPKI, It is assumed that the reader understands BGP, [RFC4271], the RPKI,
[RFC6480], Route Origin Authorizations (ROAs), [RFC6482], and RPKI- [RFC6480], Route Origin Authorizations (ROAs), [RFC6482], and RPKI-
based Prefix Validation, [RFC6811]. based Prefix Validation, [RFC6811].
3. Mark ALL Prefixes 3. Mark ALL Prefixes
An operator O should not have to hear from their neighbor N that O A router SHOULD validate and mark all routes in its BGP, no matter
announced an Invalid route to N. O's routers should tell O before how received. Otherwise the operator does not have the ability to
announcing the Invalid route to neighbor N. For this reason, drop Invalid routes; and is therefore liable to complaints from
neighbors about propagation of invalid routes. For this reason,
[RFC6811] says [RFC6811] says
"When a BGP speaker receives an UPDATE from a neighbor, it SHOULD "When a BGP speaker receives an UPDATE from a neighbor, it SHOULD
perform a lookup as described above for each of the Routes in the perform a lookup as described above for each of the Routes in the
UPDATE message. The lookup SHOULD also be applied to routes that are UPDATE message. The lookup SHOULD also be applied to routes that are
redistributed into BGP from another source, such as another protocol redistributed into BGP from another source, such as another protocol
or a locally defined static route." or a locally defined static route."
[RFC6811] goes on to say "An implementation MAY provide configuration [RFC6811] goes on to say "An implementation MAY provide configuration
options to control which routes the lookup is applied to." options to control which routes the lookup is applied to."
skipping to change at page 3, line 31 skipping to change at page 3, line 31
confederation, AS migration, or other multi-AS configuration, then confederation, AS migration, or other multi-AS configuration, then
the router configuration MUST provide a means of specifying the AS to the router configuration MUST provide a means of specifying the AS to
be used on the redistribution, either per redistribution or globally. be used on the redistribution, either per redistribution or globally.
4. Marking not Acting 4. Marking not Acting
Significant Clarification: Once routes are marked, the operator Significant Clarification: Once routes are marked, the operator
should be in complete control of any policy applied based the should be in complete control of any policy applied based the
markings. Absent operator configuration, policy MUST NOT be applied. markings. Absent operator configuration, policy MUST NOT be applied.
Automatic policy actions such as those described in [RFC8097], BGP Automatic origin validation policy actions such as those described in
Prefix Origin Validation State Extended Community, MUST NOT be [RFC8097], BGP Prefix Origin Validation State Extended Community,
carried out or otherwise applied unless specifically configured by MUST NOT be carried out or otherwise applied unless specifically
the operator. configured by the operator.
5. Security Considerations 5. Security Considerations
This document does not create security considerations beyond those of This document does not create security considerations beyond those of
[RFC6811]. [RFC6811].
6. IANA Considerations 6. IANA Considerations
This document has no IANA Considerations. This document has no IANA Considerations.
7. Acknowledgments 7. Acknowledgments
Many thanks to John Scudder who had the patience to give constructive Many thanks to John Scudder who had the patience to give constructive
review multiple times, and to Keyur Patel who noted that the AS might review multiple times, and to Keyur Patel who noted that the AS might
have to be specified. George Michaelson and Jay Borkenhagen kindly have to be specified. George Michaelson, Jay Borkenhagen, John
helped cleaning up loose wording. Heasley, and Matthias Waehlisch kindly helped clean up loose wording.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC6482] Lepinski, M., Kent, S., and D. Kong, "A Profile for Route [RFC6482] Lepinski, M., Kent, S., and D. Kong, "A Profile for Route
Origin Authorizations (ROAs)", RFC 6482, Origin Authorizations (ROAs)", RFC 6482,
DOI 10.17487/RFC6482, February 2012, DOI 10.17487/RFC6482, February 2012,
<http://www.rfc-editor.org/info/rfc6482>. <http://www.rfc-editor.org/info/rfc6482>.
 End of changes. 7 change blocks. 
14 lines changed or deleted 15 lines changed or added

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