BGPDEPL Minutes
mathis@pele.psc.edu Sat, 12 December 1992 16:26 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01600; 12 Dec 92 11:26 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa01596; 12 Dec 92 11:26 EST
Received: from merit.edu by CNRI.Reston.VA.US id aa09718; 12 Dec 92 11:28 EST
Return-Path: <bgpd-owner@merit.edu>
Received: by merit.edu (5.65/1123-1.0) id AA12240; Sat, 12 Dec 92 11:12:53 -0500
Received: from pele.psc.edu by merit.edu (5.65/1123-1.0) id AA12236; Sat, 12 Dec 92 11:12:51 -0500
Received: by pele.psc.edu (5.57/Ultrix2.4-C cf:ab 9/11/90 --MM--) id AA00769; Sat, 12 Dec 92 11:12:45 -0500
Message-Id: <9212121612.AA00769@pele.psc.edu>
To: mdavies@CNRI.Reston.VA.US
Cc: bgpd@merit.edu, mathis@psc.edu
Subject: BGPDEPL Minutes
Date: Sat, 12 Dec 1992 11:12:41 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: mathis@pele.psc.edu
X-Mts: smtp
Megan, These are the minutes of the BGP deploymnent WG, as reviewed by the attendees. I don't expect any late changes, but you never know... Cheers, --MM-- BGP Deployment WG 18-Nov-9 Matt Mathis, Pittsburgh Supercomputing Center (on behalf of Jessica Yu, Merrit) Opening: The immediate agenda of the BGP WG is to expedite BGP-4 deployment in the Internet. At this moment none of the vendors have BGP-4 code running. Network operators are all waiting on their vendors, and our task is to encourage the vendors to complete BGP-4 as soon as possible. The AS path tree collected from Pittsburgh was discussed (attached below). Of the approximately 5000 networks which are currently reachable, almost 3000 are being originated with EGP2. No single AS originating more than 100 networks is using BGP at all, including all other US Backbones and large regionals. NSFnet, Ebone, CAnet, a few mid sized regionals, and ANS stub customers account for all deployed BGP in the Internet today. Four mid-level operators (representing relatively large networks) indicated that they had tested BGP-3, and had reverted to EGP2 because their vendor's implementations to be missing some features required in their environment. (Note that there are several BGP based transit networks including ANS, AlterNet, Sprint and the EBone, but these originate relatively few networks.) This situation is pretty bleak. There is only a short time available to test and deploy BGP-4, and operators whom have not yet deployed BGP-3 will face additional difficulties phasing out EGP2. It is desirable for all network operators to have BGP experience as soon as possible. Implementor reports: ANS - Currently has a "routed" implementation of BGP-1 and BGP-2 running in the backbone. Will be converting to "gated" in January or early February (This will deprecate BGP-1). They expect to begin testing BGP-4 w/CIDR in the production backbone during 1Q93. Cisco - Currently support BGP-2 and BGP-3. Chose not to announce plans or timetable for BGP-4. Wellfleet - Plans to have BGP-3 in summer of 93 and BGP-4 sometime after. EMPB - PTT Telecom, The Netherlands). Will have BGP-3 Soon. Uncertain about schedule for BGP-4. IBM (Networking Systems at RTP) - BGP-3 has been announced for 6611 router in 2Q93. 3Com - Hopes to be testing BGP-4 by March, for possible release by August. BBN - BGP-3 is currently deployed in T20's. They are working on BGP-4. Proteon was not represented, but several of their customers (who were present) have been promised BGP-4 in April 93. Claudio Topolcic, from CNRI, presented RFC1366 and RFC1367, the proposed addressing plan and schedule to deploy CIDR. This served to initiate a general discussion about timetables. The consensus was that the following schedule is reasonable: 1/93-3/93 BGP-4 interoperability testing with the ANS testing facility (See below - all vendors are invited to participate) 3/93 - BGP-4 capable code deployed in the production NSFnet backbone. Begin testing by propagating some non-production/non-ABC networks through the backbone. 6/93 - Start aggregating *production* networks in the backbone. 12/93 - Completely phase out all EGP2 on NSFnet DMZs. There was some discussion about how this interacts with the new network assignment rules and schedule specified in RFC1366 and RFC1367. It was noted that 8 of the operators present had already obtained contiguous blocks of 256 class C addresses in advance of the formal plan. This has two implications: Since the NIC does not track assignments which are slated for subsequent reassignment, current growth figures are exaggerated by at at least 2000 networks and probably more. Clusters of Class C networks will start appearing before predicted by RFC1367. This may slightly steepen the growth of the routing tables but most of the operators were not concerned. Several pointed out that most mature technology companys already had old network numbers. At the regional level most of the sites requesting new numbers were new to IP networking, and even if they had plans for hundreds or thousands of IP hosts, they currently only needed to announce one or two class C networks out of their entire block. The first aggregation of production networks (scheduled for June 1993) will be a flag day for any site requiring full routing tables and not running BGP-4. There are only a few sites which may find them selves in this situation. All others can use default to route to their favorite backbone/mid-level provider. The sites which require full routing tables are either enforcing AUPs or implement optimal routing to multiple backbones or mid-levels. In the latter case, not having BGP-4 will result in non-optimal routes for the aggregated networks only. This is not viewed as a show stopper. However, if some organization has a mission requirement to enforce an AUP but can not deploy BGP-4 by June 1993, there will be pressure to slip the schedule. This must be balanced against the cost to everyone else of carrying ever growing non-CIDR routing tables. We also considered the scenario where BGP-4 isn't deployed on time for some reason (e.g. finding a serious bug in the specification.) Our conclusion was that the above discussion also applys, as long as the NSFnet backbone can still hold the routing table for the entire Internet. All other providers can (in principle) use default reach the NSFnet when they can no longer hold the entire routing table themselves. As a corollary, the Internet will survive the RO+AD crisis if and only if at least one network provider implements a solution. If no solutions are successful, the network provider of last resort will be blamed, even if the problem has become intractable. Jordan Becker (ANS) estimated that full route aggregation will reduce the current routing tables by about 30%, because the old address assignment policies tended to allocate addresses in blocks anyhow. Jordan repeated his invitation for all router vendors to make use of the ANS test facility for BGP interoperability testing. Vendors can make arrangements to bring equipment to the test facility, or to do remote testing through a "wide area" BGP session across the internet. Contact him for further information (becker@ans.net). Dennis Ferguson (ANS/gated implementor) announced that he had avoided implementing the supernet expansion code, which would map BGP-4 supernets into a block of BGP-3 class C networks. He was concerned that this is difficult to do correctly and unlikely to be useful for very long. After some discussion it was observed that the 8 blocks of 256 class C networks represented in the room would be announced as 8 BGP-4 routes as soon as prudent. These would in turn map to 2048 class C BGP-3 routes, which are likely to immediately overwhelm any BGP-3 router. Ergo the supernet expansion code would probably be useful for less time than it would take to debug it. The BGP deployment working group concurs that implementing the supernet expansion code would not be cost effective. Tony Li of Cisco made an interesting point about software release schedules. Releases are typically on a 6 month cycle with an 8 month lead time between code freeze and "first customer ship" (aka: beginning of General Availability for some new feature). Cisco's next scheduled code freeze is February 93, so even if bug-free BGP-4 code exists today the earliest it will appear in General Availability products is October 1993. All customers who need BGP-4 before then must run pre-GA code. Other vendors were in general agreement. Some of the operators were upset - one was operating under a prohibition against using non-GA code. Thank you to Gene Hastings for taking minutes. ---------------------------------------------------------------- AS path tree (collected from Pittsburgh): 145 IGP (1) NSFNET-CORE . 22 UNKNOWN (7) NOSC . 26 UNKNOWN (5) CORNELL Cornell Regional network . 32 UNKNOWN (1) STANFORD BARRNet . 38 UNKNOWN (3) UIUC UIUC Regional Network . 68 UNKNOWN (2) LANL-INET-AS . 73 UNKNOWN (3) WASHINGTON-AS NorthWestNet Regional Network . 81 UNKNOWN (43) CONCERT CONCERT . 86 UNKNOWN (172) SURANET-AS SURANET Regional Network (College Park) . 93 UNKNOWN (91) FORD-AS MIDnet . 97 UNKNOWN (97) JVNC-AS JvNCnet Regional Network . 104 UNKNOWN (1) COLORADO-AS NCAR Regional Network . 114 UNKNOWN (86) SESQUINET-AS SESQUINET Regional Network . 164 UNKNOWN (112) DDN-MB-AS Milnet (FIX-West) . 174 UNKNOWN (400) NYSERNET-AS NYSERNet Regional Network / PSI . 184 UNKNOWN (367) NSFNETTEST4-AS Milnet (FIX-East) . 194 UNKNOWN (4) USAN-AS NCAR Regional Network . 195 UNKNOWN (17) SDSC-AS SDSC Regional network . 200 UNKNOWN (241) BARRNET-AS BARRNet . 209 UNKNOWN (150) WESTNET-EAST Westnet Regional Network (Colorado Attachment) - ENSS 141 . 210 UNKNOWN (69) WESTNET-WEST Westnet Regional Network (Utah Attachment) - ENSS 142 . 233 UNKNOWN (46) NSFNETTEST10-AS MERIT network . 237 UNKNOWN (10) NSFNETTEST14-AS MERIT network . 266 UNKNOWN (16) CICNET1-AS CICNET at MERIT . 267 UNKNOWN (148) CICNET2-AS CICNET at UIUC . 274 UNKNOWN (24) SOFT-CON-NTS-AS TWBNET (FIX-East) . 278 UNKNOWN (3) RAM-AS Mexican Networks at NCAR . 279 UNKNOWN (149) SURANET-AS-2 SURANET Regional Network (Georgia Tech) . 280 UNKNOWN (84) SESQUI-AUX-AS SESQUINET Regional Network . 281 UNKNOWN (136) NEARNET-AS NEARnet Regional Network . 291 UNKNOWN (30) ESNET-EAST-AS Energy Science Network (FIX-West) . 293 UNKNOWN (146) ESNET-WEST-AS Energy Science Network (FIX-East) . 297 UNKNOWN (644) NSN-UMD-AS Nasa Science Network (FIX-East) . 372 UNKNOWN (3) NSN-AMES-AS Nasa Science Network (FIX-West) . 555 UNKNOWN (27) MSCNET-AS Minnesota Supercomputer Center Network (MSCNet) . 590 UNKNOWN (352) EASINET-AS1 . 603 UNKNOWN (216) CANET . 685 UNKNOWN (62) NWNET-AS NorthWestNet Regional Network . 698 UNKNOWN (7) ASN-UIUC-REGION-AS UIRNet . 701 UNKNOWN (486) ALTERNET-AS Alternet . 750 UNKNOWN (1) NSFNETTEST16-AS . 754 UNKNOWN (288) NSFNETTEST20-AS . 771 UNKNOWN (14) NSN-RICE-AS Nasa Science Network (Houston) . 1224 UNKNOWN (2) NCSA-AS NCSA, Champaign, IL . 1240 UNKNOWN (15) ICM-NACSIS FIX-W.ICM.NET . 1250 UNKNOWN (67) SINGAPORE-AS ENSS 137 - Princeton . 1262 UNKNOWN (3) NSN-NCAR-AS-AS Nasa Science Network (Boulder, CO) . 1383 UNKNOWN (106) NSFNETTEST48-AS . 1740 UNKNOWN (165) CERFNET CERFnet . 1800 UNKNOWN (306) ICMNET-2 ICM (FIX-East) 690 IGP (1) NSFNET-T3-RT-AS ANS T3 Network . 17 EGP (7) PURDUE-CS ENSS 152 Purdue - AS . 26 EGP (5) CORNELL Cornell Regional network . 32 EGP (1) STANFORD BARRNet . 38 EGP (3) UIUC UIUC Regional Network . 73 IGP (3) WASHINGTON-AS NorthWestNet Regional Network . 81 IGP (48) CONCERT CONCERT . 86 EGP (171) SURANET-AS SURANET Regional Network (College Park) . 93 EGP (92) FORD-AS MIDnet . 97 IGP (1) JVNC-AS JvNCnet Regional Network . 104 IGP (2) COLORADO-AS NCAR Regional Network . 114 IGP (2) SESQUINET-AS SESQUINET Regional Network . 164 EGP (111) DDN-MB-AS Milnet (FIX-West) . 174 EGP (400) NYSERNET-AS NYSERNet Regional Network / PSI . 184 EGP (367) NSFNETTEST4-AS Milnet (FIX-East) . 189 EGP (1) BARRNET-AS BARRNet . 194 EGP (3) USAN-AS NCAR Regional Network . 195 EGP (16) SDSC-AS SDSC Regional network . 200 EGP (238) BARRNET-AS BARRNet . 201 EGP (1) BARRNET-AS BARRNet . 204 IGP (90) PSCNET-AS PSCNET Regional Network . 209 EGP (151) WESTNET-EAST Westnet Regional Network (Colorado Attachment) - ENSS 141 . 210 EGP (69) WESTNET-WEST Westnet Regional Network (Utah Attachment) - ENSS 142 . 237 IGP (1) NSFNETTEST14-AS MERIT network . 238 IGP (1) NSFNETTEST15-AS IBM Information Network . 266 IGP (1) CICNET1-AS CICNET at MERIT . 267 EGP (95) CICNET2-AS CICNET at UIUC . 274 EGP (24) SOFT-CON-NTS-AS TWBNET (FIX-East) . 279 EGP (148) SURANET-AS-2 SURANET Regional Network (Georgia Tech) . 280 Incomplete (84) SESQUI-AUX-AS SESQUINET Regional Network . 281 EGP (241) NEARNET-AS NEARnet Regional Network . 291 EGP (30) ESNET-EAST-AS Energy Science Network (FIX-West) . 293 EGP (137) ESNET-WEST-AS Energy Science Network (FIX-East) . 297 EGP (247) NSN-UMD-AS Nasa Science Network (FIX-East) . 372 EGP (387) NSN-AMES-AS Nasa Science Network (FIX-West) . 555 Incomplete (27) MSCNET-AS Minnesota Supercomputer Center Network (MSCNet) . 600 IGP (1) OARNET-AS OARNET, Cleveland, OH . 683 IGP (9) ARGONNE-AS Argonne Labs . 685 IGP (62) NWNET-AS NorthWestNet Regional Network . 698 EGP (7) ASN-UIUC-REGION-AS UIRNet . 701 IGP (8) ALTERNET-AS Alternet . . 35 EGP (1) MICATON . . 86 EGP (1) SURANET-AS SURANET Regional Network (College Park) . . 286 Incomplete (29) EUNET-AS . . . 1270 IGP (90) UNIDO-AS . . . 1290 IGP (19) UKNET-AS . . . 1836 IGP (9) EUNET-CH-AS2 . . . 1890 Incomplete (1) . . . . 1888 IGP (3) . . . 1891 IGP (3) . . 545 EGP (1) NRI NRI-NET, Reston, VA . . 558 EGP (3) OLIVETTI-AS1 . . 1705 IGP (8) GM-INDY-NET . . 1729 IGP (6) TIPNET1 . . 1800 TRANSIT (0) ICMNET-2 ICM (FIX-East) . . . 294 EGP (6) FRANCE-IP-NET-AS . . . 1755 TRANSIT (0) EBONE-INTERNAL . . . . 286 TRANSIT (0) EUNET-AS . . . . . 1899 IGP (17) . . . . 786 TRANSIT (0) ULCC-CISCO-AS . . . . . 1275 IGP (1) UNIDO-AS . . . . 1103 IGP (1) SURFNET-AS . . . . 1741 TRANSIT (0) FUNET . . . . . 719 IGP (5) LANLINK-AS . . . . . 790 IGP (1) FUUG-NET-AS-AS . . . . 1853 TRANSIT (0) AT-BONE . . . . . 760 IGP (12) UNIVIE-AS . . 1849 EGP (23) PIPEX-AS . 771 EGP (14) NSN-RICE-AS Nasa Science Network (Houston) . 1224 EGP (2) NCSA-AS NCSA, Champaign, IL . 1225 Incomplete (64) CICNET3-AS CICNET at Argonne Labs . 1240 IGP (10) ICM-NACSIS FIX-W.ICM.NET . . 1239 IGP (5) ICM-NORDUNET . 1262 EGP (5) NSN-NCAR-AS-AS Nasa Science Network (Boulder, CO) . 1312 IGP (2) VA-TECH-AS VPI - ENSS 151 . 1321 IGP (1) NSFNETTEST26-AS ANS San Francisco - DNSS 11 . 1322 IGP (1) NSFNETTEST27-AS ANS Los Angeles - DNSS 19 . 1323 IGP (1) NSFNETTEST28-AS ANS Chicago - DNSS 27 . 1324 IGP (1) NSFNETTEST29-AS ANS New York City - DNSS 35 . 1325 IGP (1) NSFNETTEST30-AS ANS Cleveland - DNSS 43 . 1326 IGP (1) NSFNETTEST31-AS ANS Hartford - DNSS 51 . 1327 IGP (1) NSFNETTEST32-AS ANS Washington D.C. - DNSS 59 . 1328 IGP (1) NSFNETTEST33-AS ANS Houston - DNSS 67 . 1329 IGP (1) NSFNETTEST34-AS ANS Greensboro - DNSS 75 . 1330 IGP (1) NSFNETTEST35-AS ANS St. Louis - DNSS 83 . 1331 IGP (1) NSFNETTEST36-AS ANS Seattle - DNSS 91 . 1332 IGP (1) NSFNETTEST37-AS ANS Denver - DNSS 99 . 1333 IGP (1) NSFNETTEST38-AS ANS Atlanta - DNSS 107 . 1660 IGP (2) ANS-BLK1 ANS, Elmsford, New York . 1662 IGP (8) ANS-BLK1 CUNY, New York, New York . 1663 IGP (1) ANS-BLK1 MCI, Southfield, MI . 1666 IGP (2) ANS-BLK1 ANS at Merit . 1700 IGP (1) SESQUI-3 SESQUINET Regional Network . 1740 IGP (3) CERFNET CERFnet . 1747 EGP (2) IBMWATSON-AS IBM Watson, Yorktown Heights, NY . 1751 IGP (1) LEXMARK-AS Lexmark, Lexington, KY . 1757 IGP (1) MDCI-AS Mead Data Central . 1782 EGP (2) AIXSERV-AS, ENSS 174 . 1800 IGP (4) ICMNET-2 ICM (FIX-East) . . 294 EGP (156) FRANCE-IP-NET-AS . . 1239 IGP (6) ICM-NORDUNET . . 1755 IGP (4) EBONE-INTERNAL . . . 224 IGP (29) UNINETT-AS . . . 286 Incomplete (7) EUNET-AS . . . 1257 IGP (12) SWIPNET-AS . . . . 1653 IGP (1) SUNET . . . 1653 IGP (17) SUNET . . . 1654 IGP (4) SWEDEN . . . 1741 IGP (28) FUNET . . . . 544 IGP (8) PTN-FINLAND . . . . 790 IGP (3) FUUG-NET-AS-AS . . . . 1739 IGP (1) TAMNET . . . 1835 IGP (6) DENET . . . 1853 TRANSIT (0) AT-BONE . . . . 1887 IGP (9) . . . 1880 IGP (12) . 1810 EGP (2) NEARNET-1 NEARnet-2 . 1907 IGP (2) IPSERV-AS IPSERV . 1934 IGP (1) ANS-RESTON-AS ANS, Reston, Virginia . 1956 EGP (1) IBMEVS-AS IBMEVS-AS . 1972 IGP (1) HPC-NET DARPA . 1975 IGP (1) UMI-AS University Microfilms, Inc. . 1997 EGP (1) IBMDES-AS IBM Dallas Engineering & Scientific . 2002 IGP (1) IBM-PV-AS IBM-PV-AS . . 9001 EGP (1) . . 9005 EGP (1) . . 9007 EGP (1) Summary by origin Origin #nets #as UNKNOWN 5427 49 TRANSIT 0 7 Incompl 212 6 EGP 3175 43 IGP 605 72 Summary by AS AS# #ref name 17 1 PURDUE-CS ENSS 152 Purdue - AS 22 1 NOSC 26 2 CORNELL Cornell Regional network 32 2 STANFORD BARRNet 35 1 MICATON 38 2 UIUC UIUC Regional Network 68 1 LANL-INET-AS 73 2 WASHINGTON-AS NorthWestNet Regional Network 81 2 CONCERT CONCERT 86 3 SURANET-AS SURANET Regional Network (College Park) 93 2 FORD-AS MIDnet 97 2 JVNC-AS JvNCnet Regional Network 104 2 COLORADO-AS NCAR Regional Network 114 2 SESQUINET-AS SESQUINET Regional Network 145 1 NSFNET-CORE 164 2 DDN-MB-AS Milnet (FIX-West) 174 2 NYSERNET-AS NYSERNet Regional Network / PSI 184 2 NSFNETTEST4-AS Milnet (FIX-East) 189 1 BARRNET-AS BARRNet 194 2 USAN-AS NCAR Regional Network 195 2 SDSC-AS SDSC Regional network 200 2 BARRNET-AS BARRNet 201 1 BARRNET-AS BARRNet 204 1 PSCNET-AS PSCNET Regional Network 209 2 WESTNET-EAST Westnet Regional Network (Colorado Attachment) - ENSS 141 210 2 WESTNET-WEST Westnet Regional Network (Utah Attachment) - ENSS 142 224 1 UNINETT-AS 233 1 NSFNETTEST10-AS MERIT network 237 2 NSFNETTEST14-AS MERIT network 238 1 NSFNETTEST15-AS IBM Information Network 266 2 CICNET1-AS CICNET at MERIT 267 2 CICNET2-AS CICNET at UIUC 274 2 SOFT-CON-NTS-AS TWBNET (FIX-East) 278 1 RAM-AS Mexican Networks at NCAR 279 2 SURANET-AS-2 SURANET Regional Network (Georgia Tech) 280 2 SESQUI-AUX-AS SESQUINET Regional Network 281 2 NEARNET-AS NEARnet Regional Network 286 3 EUNET-AS 291 2 ESNET-EAST-AS Energy Science Network (FIX-West) 293 2 ESNET-WEST-AS Energy Science Network (FIX-East) 294 2 FRANCE-IP-NET-AS 297 2 NSN-UMD-AS Nasa Science Network (FIX-East) 372 2 NSN-AMES-AS Nasa Science Network (FIX-West) 544 1 PTN-FINLAND 545 1 NRI NRI-NET, Reston, VA 555 2 MSCNET-AS Minnesota Supercomputer Center Network (MSCNet) 558 1 OLIVETTI-AS1 590 1 EASINET-AS1 600 1 OARNET-AS OARNET, Cleveland, OH 603 1 CANET 683 1 ARGONNE-AS Argonne Labs 685 2 NWNET-AS NorthWestNet Regional Network 690 1 NSFNET-T3-RT-AS ANS T3 Network 698 2 ASN-UIUC-REGION-AS UIRNet 701 2 ALTERNET-AS Alternet 719 1 LANLINK-AS 750 1 NSFNETTEST16-AS 754 1 NSFNETTEST20-AS 760 1 UNIVIE-AS 771 2 NSN-RICE-AS Nasa Science Network (Houston) 786 1 ULCC-CISCO-AS 790 2 FUUG-NET-AS-AS 1103 1 SURFNET-AS 1224 2 NCSA-AS NCSA, Champaign, IL 1225 1 CICNET3-AS CICNET at Argonne Labs 1239 2 ICM-NORDUNET 1240 2 ICM-NACSIS FIX-W.ICM.NET 1250 1 SINGAPORE-AS ENSS 137 - Princeton 1257 1 SWIPNET-AS 1262 2 NSN-NCAR-AS-AS Nasa Science Network (Boulder, CO) 1270 1 UNIDO-AS 1275 1 UNIDO-AS 1290 1 UKNET-AS 1312 1 VA-TECH-AS VPI - ENSS 151 1321 1 NSFNETTEST26-AS ANS San Francisco - DNSS 11 1322 1 NSFNETTEST27-AS ANS Los Angeles - DNSS 19 1323 1 NSFNETTEST28-AS ANS Chicago - DNSS 27 1324 1 NSFNETTEST29-AS ANS New York City - DNSS 35 1325 1 NSFNETTEST30-AS ANS Cleveland - DNSS 43 1326 1 NSFNETTEST31-AS ANS Hartford - DNSS 51 1327 1 NSFNETTEST32-AS ANS Washington D.C. - DNSS 59 1328 1 NSFNETTEST33-AS ANS Houston - DNSS 67 1329 1 NSFNETTEST34-AS ANS Greensboro - DNSS 75 1330 1 NSFNETTEST35-AS ANS St. Louis - DNSS 83 1331 1 NSFNETTEST36-AS ANS Seattle - DNSS 91 1332 1 NSFNETTEST37-AS ANS Denver - DNSS 99 1333 1 NSFNETTEST38-AS ANS Atlanta - DNSS 107 1383 1 NSFNETTEST48-AS 1653 2 SUNET 1654 1 SWEDEN 1660 1 ANS-BLK1 ANS, Elmsford, New York 1662 1 ANS-BLK1 CUNY, New York, New York 1663 1 ANS-BLK1 MCI, Southfield, MI 1666 1 ANS-BLK1 ANS at Merit 1700 1 SESQUI-3 SESQUINET Regional Network 1705 1 GM-INDY-NET 1729 1 TIPNET1 1739 1 TAMNET 1740 2 CERFNET CERFnet 1741 2 FUNET 1747 1 IBMWATSON-AS IBM Watson, Yorktown Heights, NY 1751 1 LEXMARK-AS Lexmark, Lexington, KY 1755 2 EBONE-INTERNAL 1757 1 MDCI-AS Mead Data Central 1782 1 AIXSERV-AS, ENSS 174 1800 3 ICMNET-2 ICM (FIX-East) 1810 1 NEARNET-1 NEARnet-2 1835 1 DENET 1836 1 EUNET-CH-AS2 1849 1 PIPEX-AS 1853 2 AT-BONE 1880 1 1887 1 1888 1 1890 1 1891 1 1899 1 1907 1 IPSERV-AS IPSERV 1934 1 ANS-RESTON-AS ANS, Reston, Virginia 1956 1 IBMEVS-AS IBMEVS-AS 1972 1 HPC-NET DARPA 1975 1 UMI-AS University Microfilms, Inc. 1997 1 IBMDES-AS IBM Dallas Engineering & Scientific 2002 1 IBM-PV-AS IBM-PV-AS 9001 1 9005 1 9007 1 ---------------------------------------------------------------------- The fields in each line of the AS path tree are: - dots.. for above listed AS's also traversed to reach this AS. - AS number - BGP origin field, UNKNOWN -> transit across the T1 NSF net (origin is missing) TRANSIT -> No nets originate in this AS, ergo no origin field others are as described in the BGP RFCs ;-) - (net count) Number of networks carried by this AS path - NIC name - one token from asn.txt - Merit DB name - Additional name information from Merit's as-as3.now There are a number of artifacts which limit the completeness of this data: - It was collected from AS 1206 (PSCnet) which does not appear in the list - AS 1206 is dual connected, such that most networks (and AS's) should appear twice - Once via AS 145 and once via AS 690. - AS 1206 is "NSFnet AUP compliant" and does not get CIX or other commercial routes. - Some international routes are excluded as well. - This is collected from a snapshot of live routing tables, and at the time there were are least 3 open tickets at the Merit NOC. - This is only the "spanning tree" used to reach Pittsburgh. Other links do not appear.
- BGPDEPL Minutes mathis