% Datatracker information for RFCs on the Legacy Stream is unfortunately often
% incorrect. Please correct the bibtex below based on the information in the
% actual RFC at https://rfc-editor.org/rfc/rfc1786.txt

@misc{rfc1786,
    series =    {Request for Comments},
    number =    1786,
    howpublished =  {RFC 1786},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC1786},
    url =       {https://www.rfc-editor.org/info/rfc1786},
    author =    {},
    title =     {{Representation of IP Routing Policies in a Routing Registry (ripe-81++)}},
    pagetotal = 83,
    year =      1995,
    month =     mar,
    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.},
}