draft-ietf-sidr-origin-validation-signaling-01.txt   draft-ietf-sidr-origin-validation-signaling-02.txt 
Network Working Group P. Mohapatra Network Working Group P. Mohapatra
Internet-Draft K. Patel Internet-Draft K. Patel
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: February 4, 2012 J. Scudder Expires: June 11, 2013 J. Scudder
D. Ward
Juniper Networks Juniper Networks
D. Ward
Cisco Systems
R. Bush R. Bush
Internet Initiative Japan, Inc. Internet Initiative Japan, Inc.
August 3, 2011 December 8, 2012
BGP Prefix Origin Validation State Extended Community BGP Prefix Origin Validation State Extended Community
draft-ietf-sidr-origin-validation-signaling-01 draft-ietf-sidr-origin-validation-signaling-02
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 41 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 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 February 4, 2012. This Internet-Draft will expire on June 11, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 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
described in the Simplified BSD License. described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . . 4 1.1. Requirements Language . . . . . . . . . . . . . . . . . . . 3
2. Origin Validation State Extended Community . . . . . . . . . . 4 2. Origin Validation State Extended Community . . . . . . . . . . 3
3. Changes to the BGP Decision Process . . . . . . . . . . . . . . 5 3. Changes to the BGP Decision Process . . . . . . . . . . . . . . 4
3.1. Policy Control . . . . . . . . . . . . . . . . . . . . . . 5 3.1. Policy Control . . . . . . . . . . . . . . . . . . . . . . 4
4. Deployment Considerations . . . . . . . . . . . . . . . . . . . 5 4. Deployment Considerations . . . . . . . . . . . . . . . . . . . 4
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . . . 6 8.1. Normative References . . . . . . . . . . . . . . . . . . . 5
8.2. Informative References . . . . . . . . . . . . . . . . . . 6 8.2. Informational References . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
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 defines a new BGP opaque specification for doing so. The document defines a new BGP opaque
extended community to carry the validation state inside an autonomous extended community to carry the validation state inside an autonomous
system to influence the decision process of the IBGP speakers. system to influence the decision process of the IBGP speakers.
skipping to change at page 6, line 25 skipping to change at page 5, line 25
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
Protocol 4 (BGP-4)", RFC 4271, January 2006. Protocol 4 (BGP-4)", RFC 4271, January 2006.
[RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended
Communities Attribute", RFC 4360, February 2006. Communities Attribute", RFC 4360, February 2006.
8.2. Informative References 8.2. Informational References
[I-D.ietf-sidr-pfx-validate] [I-D.ietf-sidr-pfx-validate]
Mohapatra, P., Scudder, J., Ward, D., Bush, R., and R. Mohapatra, P., Scudder, J., Ward, D., Bush, R., and R.
Austein, "BGP Prefix Origin Validation", Austein, "BGP Prefix Origin Validation",
draft-ietf-sidr-pfx-validate-02 (work in progress), draft-ietf-sidr-pfx-validate-10 (work in progress),
July 2011. October 2012.
[RFC6480] Lepinski, M. and S. Kent, "An Infrastructure to Support
Secure Internet Routing", RFC 6480, February 2012.
[RFC6482] Lepinski, M., Kent, S., and D. Kong, "A Profile for Route
Origin Authorizations (ROAs)", RFC 6482, February 2012.
Authors' Addresses Authors' Addresses
Pradosh Mohapatra Pradosh Mohapatra
Cisco Systems Cisco Systems
170 W. Tasman Drive 170 W. Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: pmohapat@cisco.com Email: pmohapat@cisco.com
skipping to change at page 7, line 21 skipping to change at page 6, line 21
John Scudder John Scudder
Juniper Networks Juniper Networks
1194 N. Mathilda Ave 1194 N. Mathilda Ave
Sunnyvale, CA 94089 Sunnyvale, CA 94089
USA USA
Email: jgs@juniper.net Email: jgs@juniper.net
David Ward David Ward
Juniper Networks Cisco Systems
1194 N. Mathilda Ave 170 W. Tasman Drive
Sunnyvale, CA 94089 San Jose, CA 95134
USA USA
Email: dward@juniper.net Email: dward@cisco.com
Randy Bush Randy Bush
Internet Initiative Japan, Inc. Internet Initiative Japan, Inc.
5147 Crystal Springs 5147 Crystal Springs
Bainbridge Island, Washington 98110 Bainbridge Island, Washington 98110
USA USA
Email: randy@psg.com Email: randy@psg.com
 End of changes. 12 change blocks. 
38 lines changed or deleted 33 lines changed or added

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