Browse Prior Art Database

Representation of IP Routing Policies in a Routing Registry (ripe-81++) (RFC1786)

IP.com Disclosure Number: IPCOM000004039D
Original Publication Date: 1995-Mar-01
Included in the Prior Art Database: 2019-Feb-12
Document File: 83 page(s) / 89K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

T. Bates: AUTHOR [+6]

Related Documents

10.17487/RFC1786: DOI

Abstract

This document is an update to the original `ripe-81' proposal for representing and storing routing polices within the RIPE database. It incorporates several extensions proposed by Merit Inc. and gives details of a generalized IP routing policy representation to be used by all Internet routing registries. It acts as both tutorial and provides details of database objects and attributes that use and make up a routing registry. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 4% of the total text.

Network Working Group T. Bates Request for Comments: 1786 MCI Telecommunications Corporation Category: Informational E. Gerich Merit, Inc. L. Joncheray Merit, Inc. J-M. Jouanigot CERN D. Karrenberg RIPE NCC M. Terpstra Bay Networks, Inc. J. Yu Merit, Inc. March 1995

Representation of IP Routing Policies in a Routing Registry (ripe-81++)

Status of this Memo

This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

Abstract

This document was originally published as a RIPE document known as ripe-181 but is also being published as an Informational RFC to reach a larger audience than its original scope. It has received community wide interest and acknowledgment throughout the Internet service provider community and will be used as the basic starting point for future work on Internet Routing Registries and routing policy representation. It can also be referred to as ripe-81++. This document is an update to the original ‘ripe-81’[1] proposal for representing and storing routing polices within the RIPE database. It incorporates several extensions proposed by Merit Inc.[2] and gives details of a generalized IP routing policy representation to be used by all Internet routing registries. It acts as both tutorial and provides details of database objects and attributes that use and make up a routing registry.

Bates, et al. [Page 1]

RFC 1786 Representing IP Routing Policies in a RR March 1995

Table of Contents

1. Introduction ................................................ 3

2. Organization of this Document ............................... 3

3. General Representation of Policy Information ............... 5

4. The Routing Registry and the RIPE Database .................. 11

5. The Route Object ............................................ 16

6. The Autonomous System Object ................................ 26

7. AS Macros ................................................... 36

8. The Community Object ........................................ 38

9. Representation of Routing Policies .......................... 41

10. Future Extensions .......................................... 50

11. References ................................................. 51

12. Security Considerations .................................... 52

13. Authors’ Addresses ......................................... 53

Appendix A - Syntax for the "aut-num" object ................... 55

Appendix B - Syntax for the "community" object ................. 68

Appendix C - Syntax for the "as-macro" object .................. 72

Appendix D - Syntax for the "route" object ..................... 76

Appendix E - List of reserved words ............................ 80

Appendix F - Motivations for RIPE-81++ ......................... 81

Appendix G - Transition strategy ............................... 83

Bates, et al. [Page 2]

RFC 1786 Representing IP Routing Policies in a RR March 1995

1. Introduction

This document is a...

Processing...
Loading...