From lpj at merit.edu Thu Aug 10 19:15:20 1995 From: lpj at merit.edu (Laurent Joncheray) Date: Thu, 10 Aug 1995 13:15:20 -0400 (EDT) Subject: Question about DB uptades Message-ID: <199508101715.NAA15486@home.merit.edu> Hi, - I create a community called 'COMM_JONCHY'. - I like to include the network 128.141 to that community. How could i do? -- Laurent -------- Logged at Thu Aug 10 20:38:52 MET DST 1995 --------- From marten at BayNetworks.com Thu Aug 10 20:40:01 1995 From: marten at BayNetworks.com (Marten Terpstra) Date: Thu, 10 Aug 1995 14:40:01 -0400 Subject: Question about DB uptades In-Reply-To: Your message of Thu, 10 Aug 1995 13:15:20 EDT. <199508101715.NAA15486@home.merit.edu> Message-ID: <9508101840.AA08250@class.engeast> Laurent Joncheray writes * Hi, * - I create a community called 'COMM_JONCHY'. * - I like to include the network 128.141 to that community. How could * i do? * * -- * Laurent if you are not the maintainer of 128.141/16 you cannot. You try anyway, and the real maintainer will get your update request and decide whether he wants 128.141/16 to be part of your community. -Marten -------- Logged at Mon Aug 21 19:16:47 MET DST 1995 --------- From curtis at ans.net Mon Aug 21 18:02:02 1995 From: curtis at ans.net (Curtis Villamizar) Date: Mon, 21 Aug 1995 12:02:02 -0400 Subject: inetnum Message-ID: <199508211602.MAA17493@brookfield.ans.net> Is inetnum obsolete? If so why are there so many of them? Sorry if I should already know this. Another question. Has any ever considered a means of registering the CIDR block allocations independently of whether they are routed or aggregated? This way we might be able to look at the effectiveness of prefix allocations delegated by IANA in terms of the number of routes they end up generating. Looks almost as if the inetnum was used for that in the RIPE IRR database. Curtis whois -h radb.ra.net " -t inetnum" inetnum: [mandatory] [single] netname: [mandatory] [single] descr: [mandatory] [multiple] country: [mandatory] [single] admin-c: [mandatory] [multiple] tech-c: [mandatory] [multiple] connect: [optional] [single] aut-sys: [optional] [single] comm-list: [optional] [single] ias-int: [optional] [multiple] nsf-in: [optional] [single] nsf-out: [optional] [single] gateway: [optional] [single] rev-srv: [optional] [multiple] remarks: [optional] [multiple] notify: [optional] [multiple] maintainer: [obsoleted] mnt-by: [optional] [multiple] changed: [mandatory] [multiple] source: [mandatory] [single] -------- Logged at Mon Aug 21 20:25:09 MET DST 1995 --------- From GeertJan.deGroot at ripe.net Mon Aug 21 20:25:03 1995 From: GeertJan.deGroot at ripe.net (Geert Jan de Groot) Date: Mon, 21 Aug 1995 20:25:03 +0200 Subject: inetnum In-Reply-To: Your message of "Mon, 21 Aug 1995 12:02:02 EDT." <199508211602.MAA17493@brookfield.ans.net> Message-ID: <9508211825.AA09737@ncc.ripe.net> On Mon, 21 Aug 1995 12:02:02 -0400 Curtis Villamizar wrote: > Is inetnum obsolete? If so why are there so many of them? Sorry if I > should already know this. > > Another question. Has any ever considered a means of registering the > CIDR block allocations independently of whether they are routed or > aggregated? This way we might be able to look at the effectiveness of > prefix allocations delegated by IANA in terms of the number of routes > they end up generating. Looks almost as if the inetnum was used for > that in the RIPE IRR database. It is. The RIPE-database is both an assignment/allocation database and a routing registry - you will find actual authoritive *assignement* in our database for the 193 and 194 blocks. (that is why the Internic only shows 'please refer to whois.ripe.net' for these blocks) Merit only took the RR part of the database, but the allocation part is by no means obsoleted ;-) As to the CIDR-block allocations, you might want to look at ripe-126 and ripe-127, both available from ftp.ripe.net/ripe/docs/* Geert Jan -------- Logged at Mon Aug 28 01:25:51 MET DST 1995 --------- From dsj at merit.edu Mon Aug 28 01:25:44 1995 From: dsj at merit.edu (Dale S. Johnson) Date: Sun, 27 Aug 1995 19:25:44 -0400 Subject: "advisory" object Message-ID: <199508272325.TAA26321@home.merit.edu> Did anyone ever finish publishing this? From swinnett at BBN.COM Tue Aug 8 11:11:54 1995 Received: from merit.edu (merit.edu [35.1.1.42]) by home.merit.edu (8.6.12/merit-2.0) with ESMTP id LAA05443 for ; Tue, 8 Aug 1995 11:11:52 -0400 Received: from BBN.COM (LABS-N.BBN.COM [128.89.0.100]) by merit.edu (8.6.12/merit-2.0) with SMTP id LAA18409 for ; Tue, 8 Aug 1995 11:11:52 -0400 Message-Id: <199508081511.LAA18409 at merit.edu> Date: Tue, 8 Aug 95 11:11:43 EDT From: Steven Winnett To: dsj at merit.edu cc: swinnett at BBN.COM Subject: RADB Syntax Question Status: RO Dale, Where is the syntax for "advisory" in the RADB route object defined? It's not in RIPE-181. Thanks., Steve Winnett BBN -------- Logged at Mon Aug 28 16:07:38 MET DST 1995 --------- From srh at merit.edu Mon Aug 28 16:07:31 1995 From: srh at merit.edu (Susan R. Harris) Date: Mon, 28 Aug 1995 10:07:31 -0400 (EDT) Subject: "advisory" object In-Reply-To: <199508272325.TAA26321@home.merit.edu> Message-ID: Hi Dale! On Steve Heimlich's request, we've been telling people that their best source of info for the advisories is ANS (noc at ans.net). We've also occasionally sent out this internal doc, to give people some initial help. ------------------- How to Create Advisory Lines for RADB Route Objects In order to route your network traffic over ANSnet (AS690), you must include an advisory line (also known as an "advisory field" or "advisory attribute") in each Route object you submit to the Routing Arbiter Database (RADB). Advisory lines specify: --The peer or adjacent ASs (autonomous systems) that will announce the route to AS690. --Optionally, the AS690 routers that will listen for these announcements, and --The order in which you prefer to have your traffic routed. The use of advisory lines is a temporary measure; advisories won't be needed once ANS installs software that eliminates the need to specify the routers that peer directly with ANSnet. EXAMPLE ADVISORY LINE Here is an example of a Route object containing an advisory line: route: 193.101.106.0/24 descr: DETECON Deutsche Telepost Consulting GmbH descr: Langer Grabenweg 35 descr: D-53175 Bonn descr: Postfach 26 01 01 descr: D-53153 Bonn descr: GERMANY origin: AS1270 comm-list: COMM_NSFNET advisory: AS690 1:701(136) 2:701(134) 3:1800 mnt-by: MAINT-AS1270 changed: nsfnet-admin at merit.edu 950308 source: RADB The advisory line above indicates that, for the IP prefix 193.101.106.0/24, AS690 will prefer AS701 over AS1800; i.e., if AS701 announces 193.101.106.0/24 to AS690, AS690 will forward traffic to addresses matching this prefix to AS701. (If AS701 is down or otherwise not announcing this route to AS690, then AS690 will forward traffic to AS1800 if the latter is announcing 193.101.106.0/24 to AS690.) Further, an announcement of this route by AS701 that is received at the node known as NSS 136 (in AS690) will be preferred over that received at NSS 134; if AS690 receives an announcement of 193.101.106.0/24 from AS701 at both NSSs, it will forward all traffic to destinations matching that prefix to the AS701 router that peers with NSS 136. HOW TO DETERMINE PEER AUTONOMOUS SYSTEMS If you don't know which AS transmits your traffic to AS690, there are several ways to find the information: --The easiest way is to check with your network provider. --If that doesn't work, the 'prtraceroute' tool is helpful, as it is a form of traceroute that displays the ASs that a packet traverses. Prtraceroute is available from: http://www.ra.net/routing.arbiter/RA/RADB.tools.docs.html ftp://ftp.ra.net/routing.arbiter/pride/prtraceroute-2.0beta2.shar.gz ftp://ftp.ra.net/routing.arbiter/pride/prtraceroute.README --If you don't have prtraceroute available, you can also use traceroute. PRTRACEROUTE EXAMPLE To use prtraceroute to identify the AS adjacent to AS690, start by tracing the route from your local network to ANSnet. The example below shows the route to the ANS backbone network, and uses an arbitrary prefix for ANSnet: prtraceroute 140.222.1.1 1 AS237 merit-gw.med.umich.edu 198.108.60.1 2 AS237 tcags-f0.med.umich.edu 141.214.254.3 3 ??? F-BACKBONE.c-CCB.UMNET.UMICH.E 141.211.1.1 4 AS237 fdd3-0.michnet1.mich.net 198.108.3.1 5 ??? cpe2-fddi-1.Chicago.mci.net 192.203.195.5 6 AS3561 border2-hssi2-0.Chicago.mci.ne 204.70.25.9 7 ??? core-fddi-1.Chicago.mci.net 204.70.3.81 8 AS3561 core-hssi-2.Boston.mci.net 204.70.1.45 9 ??? core-hssi-2.NewYork.mci.net 204.70.1.1 10 AS3561 border2-fddi0-0.NewYork.mci.ne 204.70.3.18 11 ??? sprint-nap-ds3.NewYork.mci.net 204.70.45.6 12 AS690 192.157.69.4 192.157.69.4 13 AS690 192.157.69.4 192.157.69.4 You can now query the RADB to determine which provider maintains 204.70.45.6, the router that interfaces directly with AS690 and immediately precedes AS690 on the list. Enter the command: whois -h whois.ra.net 204.70.45.6 The output is an MCI Route object. Here is a partial listing: route: 204.70.45.4/30 descr: MCI NYU Border 1 origin: AS3561 mnt-by: MCI mnt-by: MCI [...] withdrawn: 941007 source: MCI This Route object shows that the route originates in AS3561, which is maintained by MCI. You may now want to contact MCI for help in preparing your advisory line. For MCI contact information, enter this command: whois -h whois.ra.net MAINT-AS3561 The output is an RADB Maintainer object. Here is a partial listing: mntner: MAINT-AS3561 descr: People authorized to make changes for AS3561 admin-c: Not Available from RADB upd-to: AS3561 at ra.net [...] notify: rr-types at mci.net mnt-by: MAINT-AS3561 [...] source: RADB You can then send e-mail to rr-types at mci.net for further information. If there is no "notify:" field, the "tech-c:", "auth:", and "changed:" fields may provide alternate contacts that can probably help you. TRACEROUTE EXAMPLE As with prtraceroute, start by tracing the route from your local network to ANSnet. The example below shows the route to the ANS backbone network using an arbitrary prefix for ANSnet: traceroute 140.222.1.1 1 merit-gw.med.umich.edu (123.456.78.99) 2 ms 100 ms 148 ms 2 tcags-f0.med.umich.edu (141.214.254.3) 6 ms 3 ms 2 ms 3 F-BACKBONE.c-CCB.UMNET.UMICH.EDU (141.211.1.1) 4 ms 5 ms 4 ms 4 fdd3-0.michnet1.mich.net (198.108.3.1) 55 ms 7 ms 99 ms 5 cpe2-fddi-1.Chicago.mci.net (192.203.195.5) 9 ms 4 ms 5 ms 6 border2-hssi2-0.Chicago.mci.net (204.70.25.9) 11 ms 9 ms 9 ms 7 core-fddi-1.Chicago.mci.net (204.70.3.81) 9 ms 9 ms 9 ms 8 core-hssi-2.Boston.mci.net (204.70.1.45) 29 ms 29 ms 65 ms 9 core-hssi-2.NewYork.mci.net (204.70.1.1) 136 ms 226 ms 161 ms 10 border2-fddi0-0.NewYork.mci.net (204.70.3.18) 33 ms 33 ms 34 ms 11 sprint-nap-ds3.NewYork.mci.net (204.70.45.6) 39 ms 37 ms 79 ms 12 fd-0.enss218.t3.ans.net (192.157.69.4) 38 ms 40 ms 39 ms 13 fd-0.enss218.t3.ans.net (192.157.69.4) 39 ms !H 37 ms !H 71 ms Since traceroute does not display any AS numbers that you can check, note the DNS name for the router that immediately precedes AS690 on the list. The name shows that the router is maintained by MCI. You can now query the InterNIC for MCI contact information: whois -h rs.internic.net mci.net Here is a partial listing of the output: MCI Telecommunications Communications (MCI2-DOM) internetMCI Provisioning 100 Perimeter Park Drive, Suite 1 Morrisville, NC 27560 Domain Name: MCI.NET Administrative Contact, Technical Contact, Zone Contact: MCI Internet Services (MCI-IS) hostmaster at mci.net (800) 773-6248 [...] If you have further questions about Route object advisory lines, send e- mail to noc at ans.net. On Sun, 27 Aug 1995, Dale S. Johnson wrote: > Did anyone ever finish publishing this? > > From swinnett at BBN.COM Tue Aug 8 11:11:54 1995 > Received: from merit.edu (merit.edu [35.1.1.42]) by home.merit.edu (8.6.12/merit-2.0) with ESMTP id LAA05443 for ; Tue, 8 Aug 1995 11:11:52 -0400 > Received: from BBN.COM (LABS-N.BBN.COM [128.89.0.100]) by merit.edu (8.6.12/merit-2.0) with SMTP id LAA18409 for ; Tue, 8 Aug 1995 11:11:52 -0400 > Message-Id: <199508081511.LAA18409 at merit.edu> > Date: Tue, 8 Aug 95 11:11:43 EDT > From: Steven Winnett > To: dsj at merit.edu > cc: swinnett at BBN.COM > Subject: RADB Syntax Question > Status: RO > > Dale, > > Where is the syntax for "advisory" in the RADB route object defined? > It's not in RIPE-181. > > Thanks., > > Steve Winnett > BBN > > -------- Logged at Mon Aug 28 17:26:21 MET DST 1995 --------- From Daniel.Karrenberg at ripe.net Mon Aug 28 17:25:05 1995 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Mon, 28 Aug 1995 17:25:05 +0200 Subject: "advisory" object In-Reply-To: Your message of Sun, 27 Aug 1995 19:25:44 EDT. <199508272325.TAA26321@home.merit.edu> References: <199508272325.TAA26321@home.merit.edu> Message-ID: <9508281525.AA03861@ncc.ripe.net> Oops, I thought we had, but we apparently hadn't. I'll look into this. Daniel > "Dale S. Johnson" writes: > Did anyone ever finish publishing this? > > From swinnett at BBN.COM Tue Aug 8 11:11:54 1995 > Received: from merit.edu (merit.edu [35.1.1.42]) by home.merit.edu (8.6 > .12/merit-2.0) with ESMTP id LAA05443 for ; Tue, 8 Aug > 1995 11:11:52 -0400 > Received: from BBN.COM (LABS-N.BBN.COM [128.89.0.100]) by merit.edu (8. > 6.12/merit-2.0) with SMTP id LAA18409 for ; Tue, 8 Aug 1995 > 11:11:52 -0400 > Message-Id: <199508081511.LAA18409 at merit.edu> > Date: Tue, 8 Aug 95 11:11:43 EDT > From: Steven Winnett > To: dsj at merit.edu > cc: swinnett at BBN.COM > Subject: RADB Syntax Question > Status: RO > > Dale, > > Where is the syntax for "advisory" in the RADB route object defined? > It's not in RIPE-181. > > Thanks., > > Steve Winnett > BBN > -------- Logged at Mon Aug 28 18:03:01 MET DST 1995 --------- From heimlich at ans.net Mon Aug 28 18:02:24 1995 From: heimlich at ans.net (Steve Heimlich) Date: Mon, 28 Aug 1995 12:02:24 -0400 Subject: "advisory" object In-Reply-To: Your message of Mon, 28 Aug 1995 17:25:05 +0200. <9508281525.AA03861@ncc.ripe.net> Message-ID: <199508281602.AA77480@interlock.ans.net> There are probably a couple touch ups we'd like to do given that we now support MEDs. Steve > > Oops, > I thought we had, but we apparently hadn't. > I'll look into this. > > Daniel > > > "Dale S. Johnson" writes: > > Did anyone ever finish publishing this? > > > > From swinnett at BBN.COM Tue Aug 8 11:11:54 1995 > > Received: from merit.edu (merit.edu [35.1.1.42]) by home.merit.edu (8.6 > > .12/merit-2.0) with ESMTP id LAA05443 for ; Tue, 8 Aug > > 1995 11:11:52 -0400 > > Received: from BBN.COM (LABS-N.BBN.COM [128.89.0.100]) by merit.edu (8. > > 6.12/merit-2.0) with SMTP id LAA18409 for ; Tue, 8 Aug 1995 > > 11:11:52 -0400 > > Message-Id: <199508081511.LAA18409 at merit.edu> > > Date: Tue, 8 Aug 95 11:11:43 EDT > > From: Steven Winnett > > To: dsj at merit.edu > > cc: swinnett at BBN.COM > > Subject: RADB Syntax Question > > Status: RO > > > > Dale, > > > > Where is the syntax for "advisory" in the RADB route object defined? > > It's not in RIPE-181. > > > > Thanks., > > > > Steve Winnett > > BBN > > -------- Logged at Mon Aug 28 18:06:18 MET DST 1995 --------- From Daniel.Karrenberg at ripe.net Mon Aug 28 18:04:12 1995 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Mon, 28 Aug 1995 18:04:12 +0200 Subject: "advisory" object In-Reply-To: Your message of Mon, 28 Aug 1995 12:02:24 EDT. <199508281602.AA77480@interlock.ans.net> References: <199508281602.AA77480@interlock.ans.net> Message-ID: <9508281604.AA04345@ncc.ripe.net> > Steve Heimlich writes: > There are probably a couple touch ups we'd like to do given that > we now support MEDs. > > Steve Steve, we will only publish the general syntax of advisory: and refer people to the AS contacts for a description of . Daniel -------- Logged at Mon Aug 28 18:13:30 MET DST 1995 --------- From heimlich at ans.net Mon Aug 28 18:11:35 1995 From: heimlich at ans.net (Steve Heimlich) Date: Mon, 28 Aug 1995 12:11:35 -0400 Subject: "advisory" object In-Reply-To: Your message of Mon, 28 Aug 1995 18:04:12 +0200. <9508281604.AA04345@ncc.ripe.net> Message-ID: <199508281611.AA52656@interlock.ans.net> ok, that's fine. We'll try to get this into a web page on our end as well. Thanks, Steve > > > Steve Heimlich writes: > > There are probably a couple touch ups we'd like to do given that > > we now support MEDs. > > > > Steve > > Steve, > > we will only publish the general syntax of advisory: > > > > and refer people to the AS contacts for a description of > . > > Daniel -------- Logged at Mon Aug 28 19:38:46 MET DST 1995 --------- From lpj at merit.edu Mon Aug 28 19:38:41 1995 From: lpj at merit.edu (Laurent Joncheray) Date: Mon, 28 Aug 1995 13:38:41 -0400 (EDT) Subject: "advisory" object In-Reply-To: <199508281611.AA52656@interlock.ans.net> from "Steve Heimlich" at Aug 28, 95 12:11:35 pm Message-ID: <199508281738.NAA17930@home.merit.edu> It will be very secure for the DB that only 's maitainer can set those attributes. C.f. the incident with as690:128/2 -- lpj In our previous episode, Steve Heimlich said: > > ok, that's fine. > > We'll try to get this into a web page on our end as well. > > Thanks, Steve > > > > > > Steve Heimlich writes: > > > There are probably a couple touch ups we'd like to do given that > > > we now support MEDs. > > > > > > Steve > > > > Steve, > > > > we will only publish the general syntax of advisory: > > > > > > > > and refer people to the AS contacts for a description of > > . > > > > Daniel > -- Laurent Joncheray, E-Mail: lpj at merit.edu Merit Network Inc, 4251 Plymouth Rd, Suite C, Phone: +1 (313) 936 2065 Ann Arbor, MI 48105, USA Fax: +1 (313) 747 3185 "This is the end, Beautiful friend. This is the end, My only friend, the end" JM -------- Logged at Tue Aug 29 14:36:37 MET DST 1995 --------- From ncc at ripe.net Tue Aug 29 14:36:27 1995 From: ncc at ripe.net (RIPE NCC Document Annoucement Service) Date: Tue, 29 Aug 1995 14:36:27 +0200 Subject: New Document available: ripe-130 Message-ID: <9508291236.AA15720@ncc.ripe.net> New/Revised RIPE Document Announcement -------------------------------------- A revised/new document is available from the RIPE document store. Ref: ripe-130 Title: The advisory attribute Author: David Kessens, RIPE NCC Date: 1 August 1995 Format: TXT=3230 bytes Obsoletes: Obsoleted by: Updates: ripe-181 Updated by: Old: Short content description ------------------------- This document describes the advisory attribute of the route object. -------------- next part -------------- FTP Access ---------- All RIPE documents and Internet RFC`s are available via anonymous FTP from host ftp.ripe.net. Type "ftp ftp.ripe.net". Login with username "anonymous" supplying your email address as the password. After logging in, type "cd ripe/docs/" followed by the command "get filename". The relevant filenames for this document are: ripe-130.txt for the ASCII version ripe-130.ps for the PostScript version Electronic Mail Retrieval of Documents -------------------------------------- Documents can also be retrieved from the RIPE document store using a mail server program. For more information on how to use the program, send email to: mail-server at ripe.net with "send HELP" in the body text. RIPE NCC Interactive Information Server --------------------------------------- Type "telnet info.ripe.net". This is a menu driven service allows the document store to be browsed. After reading documents you are prompted as to whether you would like to receive an email copy of the document you have just read. If you would, you simply enter your email address and the document will be mailed to you. Below are details of alternative methods of access. Gopher Access ------------- The same documents are available via a "gopher" server at "gopher gopher.ripe.net". WAIS Access ----------- There is also a "WAIS" server at wais.ripe.net, where there is a WAIS index for RIPE documents "ripe-docs.src" WWW Access ---------- For those who wish to add this home page at the RIPE NCC to their own customized home pages, it can be accessed as: http://www.ripe.net MIME Mail Reader ---------------- Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the RIPE document by FTP or mail server. -------------- next part -------------- -------------- next part -------------- SEND ripe/docs/ripe-130.txt -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/postscript Size: 0 bytes Desc: FTP PostScript version Url : https://www.ripe.net/mailman/private/rr-impl/attachments/19950829/015e41fd/attachment.eps