This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
RIPE-CLNS: Alternate approache
- Previous message (by thread): DRAFT input for the RIPE database on NSAP addresses for SURFnet bv
- Next message (by thread): RIPE-CLNS: Alternate approache
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Susan Hares
skh at merit.edu
Tue Mar 15 20:13:16 CET 1994
Victor: I'd like to suggest a departure from your current structure of the current RIPE for clnp. I think the CLNP information should mirror the IP functions. IP keeps the following information: 1) Registration of IP addresses and AS information 2) Registration of Routing policy 3) Registration of Aggregation policy CLNP ought to have as close as a format to IP as possible. Therefore: I would suggest use use two different denotations: i-prefix - for the nlri prefix RD-prefix - for the domain's RDI which is the AS equivalent. I find your use in the SURFNET prefixes to confuse between RDI - which is the AS equivalent and the nlri prefix. So I propose an alternate structure: ISO-prefix - for nlri I-NET: for BISs RDI: for RDI and policy at RDI level I-AGGR: for iso aggregation This follows the IP format. Then tools might get shared if the only thing you change is ping -> clnpping traceroute -> iso traceroute What do you think? Below the example of the entries. The next message will have your SURFNET stuff with the entries. Susan Hares ---------- Cut below Here's an example given your 39, 39.528F etc ISO-prefix: iso prefixes i-prefix: iso-prefix/length prefix-name: character descr: country: admin-c: tech-c: connect: RDI: community: rev-srv: changed: source: I-NET: iso hosts (including hosts, routers, bis-s) type: <bis> <is> <host> host-name: character descr: country: admin-c: tech-c: connect: RDI: applications: rev-srv: changed: source: RDI: (ASxxxx or RDXXXX) The IDRP for IP specification gives as translation between AS numbers and an RDI. I'd like to recommend using it if IP AS and RDI are the same thing. The RDxxxxx is to use the 39.528f format. But again, I think this confuses between reachable address and the AS number which are different. I wished we'd gotten the AS equivalent space earlier. By the way, anyone who has an AS can use the IDRP for IP RDI. Just use 47:00:05:c0:01:aa:aa Where aa:aa is the AS number. descr: RDI-in: RD-out: default: (points to what RDI) bis: (NETs or names from above list) tech-c: admin-c: guardian: source: changed: I-AGGR: iso-prefix/length descr: i-aggr-prefix: (prefix contained in aggregates) i-aggr-type: <proxy> <originator> country: admin-c: tech-c: connect: i-aggr-RDI: (reference to RDI above) rev-srv: changed: source:
- Previous message (by thread): DRAFT input for the RIPE database on NSAP addresses for SURFnet bv
- Next message (by thread): RIPE-CLNS: Alternate approache
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]