draft-ietf-grow-rpsl-via-00.txt   draft-ietf-grow-rpsl-via-01.txt 
Network Working Group J. Snijders Network Working Group J. Snijders
Internet-Draft Independent Internet-Draft NTT
Updates: 4012 (if approved) May 23, 2014 Updates: 4012 (if approved) May 23, 2015
Intended status: Standards Track Intended status: Standards Track
Expires: November 24, 2014 Expires: November 24, 2015
The "import-via" and "export-via" attributes in RPSL Policy The "import-via" and "export-via" attributes in RPSL Policy
Specifications Specifications
draft-ietf-grow-rpsl-via-00 draft-ietf-grow-rpsl-via-01
Abstract Abstract
This document defines two attributes in the aut-num Class which can This document defines two attributes in the aut-num Class which can
be used in RPSL policy specifications to publish desired routing be used in RPSL policy specifications to publish desired routing
policy regarding non-adjacent networks. policy regarding non-adjacent networks.
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
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 November 24, 2014. This Internet-Draft will expire on November 24, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 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
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 17 skipping to change at page 2, line 17
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Notational Conventions . . . . . . . . . . . . . . . . . . . 2 2. Notational Conventions . . . . . . . . . . . . . . . . . . . 2
3. Background . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Background . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Import and Export Via Syntax and Semantics . . . . . . . . . 3 4. Import and Export Via Syntax and Semantics . . . . . . . . . 3
5. Example Usage . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Example Usage . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Ambiguity Resolution . . . . . . . . . . . . . . . . . . . . 5 6. Ambiguity Resolution . . . . . . . . . . . . . . . . . . . . 5
7. Security Considerations . . . . . . . . . . . . . . . . . . . 6 7. Security Considerations . . . . . . . . . . . . . . . . . . . 6
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
10.1. Normative References . . . . . . . . . . . . . . . . . . 6 10.1. Normative References . . . . . . . . . . . . . . . . . . 7
10.2. Informative References . . . . . . . . . . . . . . . . . 7 10.2. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. Grammar Rules . . . . . . . . . . . . . . . . . . . 7 Appendix A. Grammar Rules . . . . . . . . . . . . . . . . . . . 7
Appendix B. Document Change Log . . . . . . . . . . . . . . . . 9 Appendix B. TODO . . . . . . . . . . . . . . . . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9 Appendix C. Document Change Log . . . . . . . . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
The Routing Policy Specification Language [RFC4012] allows operators The Routing Policy Specification Language [RFC4012] allows operators
to specify routing policies regarding directly adjacent networks to specify routing policies regarding directly adjacent networks
through various import and export attributes. These attributes only through various import and export attributes. These attributes only
apply to directly adjacent networks. apply to directly adjacent networks.
This document proposes to extend RPSL according to the following This document proposes to extend RPSL according to the following
goals and requirements: goals and requirements:
skipping to change at page 5, line 22 skipping to change at page 5, line 23
announce AS-SNIJDERS announce AS-SNIJDERS
import-via: AS15562:AS-ROUTESERVERS import-via: AS15562:AS-ROUTESERVERS
from AS15562:AS-CUSTOMERS from AS15562:AS-CUSTOMERS
accept NOT ANY accept NOT ANY
export-via: AS15562:AS-ROUTESERVERS export-via: AS15562:AS-ROUTESERVERS
to AS15562:AS-CUSTOMERS announce NOT ANY to AS15562:AS-CUSTOMERS announce NOT ANY
import-via: AS6777 import-via: AS6777
from AS4247483647 from AS4247483647
accept AS4247483647 accept AS4247483647
export-via: AS6777 export-via: AS6777
to AS4247483647 action community.={5580:40}; to AS4247483647 action community.={15562:40};
announce AS-SNIJDERS announce AS-SNIJDERS
Figure 2 Figure 2
In the above examples AS15562 and AS15562 are Route Server In the above examples AS15562 and AS15562 are Route Server
participants. AS4247483647 is a participant who has been assigned a participants. AS4247483647 is a participant who has been assigned a
32 bit AS Number. AS6777 functions as a Route Server 32 bit AS Number. AS6777 functions as a Route Server
[I-D.ietf-idr-ix-bgp-route-server] and AS-SET AS15562:AS-ROUTESERVERS [I-D.ietf-idr-ix-bgp-route-server] and AS-SET AS15562:AS-ROUTESERVERS
contains a list of Route Server AS Numbers. AS-SET AS15562:AS- contains a list of Route Server AS Numbers. AS-SET AS15562:AS-
CUSTOMERS contains a list of downstream transit customers from CUSTOMERS contains a list of downstream transit customers from
skipping to change at page 9, line 18 skipping to change at page 9, line 23
// from mp-import: + mp-export: // from mp-import: + mp-export:
import_peering_action_list: peering T_FROM peering opt_action import_peering_action_list: peering T_FROM peering opt_action
| import_peering_action_list peering T_FROM peering opt_action | import_peering_action_list peering T_FROM peering opt_action
export_peering_action_list: peering T_TO peering opt_action export_peering_action_list: peering T_TO peering opt_action
| export_peering_action_list peering T_TO peering opt_action | export_peering_action_list peering T_TO peering opt_action
Figure 5 Figure 5
Appendix B. Document Change Log Appendix B. TODO
(RFC Editor - this Appendix can be removed upon publication as RFC)
1. Add python parser example based on Grako EBNF.
Appendix C. Document Change Log
(RFC Editor - this Appendix can be removed upon publication as RFC) (RFC Editor - this Appendix can be removed upon publication as RFC)
1. Initial document. 1. Initial document.
2. Changes to draft-snijders-rpsl-via-01.txt 2. Changes to draft-snijders-rpsl-via-01.txt
A. Moved from adding a new RPSL keyword to a new RPSL attribute A. Moved from adding a new RPSL keyword to a new RPSL attribute
to improve backwards compatibility. to improve backwards compatibility.
3. Changes to draft-snijders-rpsl-via-02.txt 3. Changes to draft-snijders-rpsl-via-02.txt
A. Added grammar appendix. A. Added grammar appendix.
B. Added section about Ambiguity Resolution. B. Added section about Ambiguity Resolution.
4. Changes to draft-snijders-rpsl-via-03.txt 4. Changes to draft-snijders-rpsl-via-03.txt
A. Updated current IRR implementations. A. Updated current IRR implementations.
5. Changes to draft-grow-rpsl-via-01.txt
A. Bump version - add TODO.
Author's Address Author's Address
Job Snijders Job Snijders
Independent NTT
Theodorus Majofskistraat 100 Theodorus Majofskistraat 100
Amsterdam 1065 SZ Amsterdam 1065 SZ
NL NL
Email: job@instituut.net Email: job@ntt.net
 End of changes. 12 change blocks. 
12 lines changed or deleted 22 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/