LISTSERV mailing list manager LISTSERV 16.0

Help for MICE-DISCUSS Archives


MICE-DISCUSS Archives

MICE-DISCUSS Archives


MICE-DISCUSS@LISTS.IPHOUSE.NET


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

MICE-DISCUSS Home

MICE-DISCUSS Home

MICE-DISCUSS  December 2017

MICE-DISCUSS December 2017

Subject:

Re: [routing-wg] a new source for authoritative routing data: ARIN WHOIS

From:

Andrew Hoyos <[log in to unmask]>

Reply-To:

MICE Discuss <[log in to unmask]>

Date:

Wed, 20 Dec 2017 10:43:22 -0600

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (191 lines)

Not necessarily. Any sane IRR filtering solution would match against some sort of IRR DB that mirrors ARIN/RIPE/RADB/etc.

I think David is getting at more about which IRR to use to register your objects.

--
Andrew Hoyos
[log in to unmask]



> On Dec 20, 2017, at 10:38 AM, DeLong, Owen <[log in to unmask]> wrote:
> 
> This assumes that all prefixes advertised at MICE are issued by ARIN.
> 
> Owen
> 
>> On Dec 19, 2017, at 14:54 , David Farmer <[log in to unmask]> wrote:
>> 
>> FYI,
>> 
>> A very interesting development in light of our discussions about doing route filtering at MICE.
>> 
>> With this development I enthusiastically support moving forward with route filtering because it provides an easy answer to Richards question about which IRR to use, you don't have to use any of them you can do it all in ARIN ONLINE.
>> 
>> Thanks.
>> 
>> ---------- Forwarded message ----------
>> From: Job Snijders <[log in to unmask]>
>> Date: Tue, Dec 19, 2017 at 4:37 PM
>> Subject: [routing-wg] a new source for authoritative routing data: ARIN WHOIS
>> To: [log in to unmask]
>> 
>> 
>> Dear RIPE WG,
>> 
>> I'm sharing a copy of what I sent to NANOG. This is specifically of
>> interest to networks and route server operators that have customers who
>> also operate in the ARIN region.
>> 
>> In the RIPE region we've always had the convenience that the "WHOIS"
>> ('inetnum') and "IRR" ('route/route6') components of the database were
>> interleaved. Only the IP block's owner can create or authorise others
>> regarding creation of route-objects. This coupling of WHOIS and IRR
>> doesn't exist at rr.arin.net vs whois.arin.net - so I consider the
>> following a significant improvement.
>> 
>> Kind regards,
>> 
>> Job
>> 
>> ----- Forwarded message from Job Snijders <[log in to unmask]> -----
>> 
>> Date: Tue, 19 Dec 2017 22:18:20 +0000
>> From: Job Snijders <[log in to unmask]>
>> To: [log in to unmask]
>> Subject: a new source for authoritative routing data: ARIN WHOIS
>> 
>> Dear NANOG,
>> 
>> I'd like to share an update on some routing security activities that
>> ARIN, NTT Communications, YYCIX (Calgary Internet Exchange), the NLNOG
>> Foundation, and the arouteserver project have been collaborating on.
>> Quite some puzzles pieces were brought together! :)
>> 
>> Traditionally, there are two commonly-used methods to signal to your
>> peers or upstream providers what Origin ASN(s) are allowed to originate
>> a given IP prefix. As an operator, you can either create a "route
>> object" in the IRR, or you can compose a Letter Of Agency (LOA) and send
>> that to your upstream providerfor manual verification.
>> 
>> When it comes to manual verification of routing data (such a LOA), one
>> of the big questions is "what data source is actually authoritative for
>> the verification?". In the ARIN registry the so-called "OriginAS"
>> attribute can be used for this purpose. The OriginAS attribute can only
>> be set or modified by authorized accounts (such as the holder of the IP
>> space). This makes the OriginAS attribute a very reliable source of
>> truth! ARIN shared some notes on LOAs & OriginAS in the following article:
>> https://teamarin.net/2016/07/07/origin-as-an-easier-way-to-validate-letters-of-authority/
>> 
>> That teamarin posting got me thinking: clearly there is a lot of
>> valuable routing information in the ARIN WHOIS registry. What if we make
>> the process such that you don't have to email in a LOA, and, have the
>> recipient verify it against against the web interface output (which you
>> updated before sending in the LOA). What if the prefix-filter generation
>> software could just programmatically fetch all (CIDR, OriginAS) tuples
>> from the ARIN WHOIS registry and load that into the list of prefixes a
>> customer is allowed to announce. Just like we do with IRR objects!
>> 
>> A few weeks ago I approached John Curran from ARIN asking whether we
>> could work out a mechanism to somehow obtain a computer parsable
>> rendering of the CIDR/OriginAS data in the ARIN WHOIS registry. The path
>> forward turned out to be an agreement between the NLNOG Foundation and
>> ARIN, which authorises NLNOG to publish a subset of the bulk whois data
>> in the convenient format (JSON) for operational purposes. The ARIN WHOIS
>> (CIDR, OriginAS) tuples can be downloaded in JSON format here:
>> http://irrexplorer.nlnog.net/static/dumps/arin-whois-originas.json.bz2
>> 
>> Because of the JSON dump, the ARIN WHOIS data can now be easily consumed
>> by software programs. For example, the JSON file is now loaded into IRR
>> Explorer as can be seen here: http://irrexplorer.nlnog.net/search/AS22512
>> You can see the 'arin-whois' column which lists what ASN(s) are
>> authorized to announce the blocks (this, in addition to what is signaled
>> in IRR or RPKI).
>> 
>> The novel thing here is that JSON file not only allows you to look up an
>> OriginAS using the IP prefix as a lookup key, but the reverse can now
>> also be done: lookup what IP prefixes an ASN is allowed to originate
>> (based on ARIN WHOIS data).
>> 
>> Deployment Experience YYCIX:
>> 
>> At this point you may be wondering - what does any of the above have to
>> do with an Internet Exchange in Alberta, Canada (https://www.yycix.ca/)
>> or a python-based IXP Route Server management software from Italian
>> origins (http://arouteserver.readthedocs.io/en/latest/) ? :-)
>> 
>> As an experiment to explore real world use of the ARIN WHOIS data and
>> prove its value, I worked with Pier Carlo Chiodi (arouteserver) and Theo
>> de Raadt (YYCIX) to consume the ARIN WHOIS data as an additional source
>> in the prefix filter generation process governing the YYCIX route
>> servers. The YYCIX route servers see roughly 80,000 prefixes.
>> 
>> The results are fantastic: ~ 1,700 IPv4 prefixes that were previously
>> rejected by the YYCIX route servers (because no IRR route object
>> exists), are now accepted because those announcements can be verified
>> against data from ARIN's WHOIS registry. This resolved roughly 23% of
>> invalid path announcements sent to the YYCIX route servers.
>> 
>> Deployment Experience NTT:
>> 
>> Based on the above positive results, starting today, NTT is also
>> accepting ARIN WHOIS OriginAS information in conjunction with IRR route
>> objects. Our implementation fetches the ARIN WHOIS data, transforms it
>> into RPSL format, and imports it into our IRRd instance at rr.ntt.net as
>> IRR objects. This way we don't need to update our toolchain to make use
>> of this new data source. An example is here:
>> 
>>     job@vurt:~$ whois -h rr.ntt.net -- "-sARIN-WHOIS 204.209.252.0/23"
>>     route:      204.209.252.0/23
>>     descr:      NET-204-209-252-0-1
>>     origin:     AS22512
>>     remarks:    This route object represents authoritative data retrieved from ARIN's WHOIS service.
>>     remarks:    The original data can be found here: https://whois.arin.net/rest/net/NET-204-209-252-0-1
>>     remarks:    This route object is the result of an automated WHOIS-to-IRR conversion process.
>>     mnt-by:     MAINT-JOB
>>     changed:    [log in to unmask] 20090220
>>     source:     ARIN-WHOIS
>> 
>> NTT also observed a substantial number (similar to YYCIX) of BGP
>> announcements from its customers that were previously rejected because
>> of the lack of an IRR object, but now are validated via ARIN WHOIS.
>> 
>> Conclusion:
>> 
>> It is great to be able to offer network operators a choice: either
>> register your BGP announcements as route objects in RPSL format in IRR,
>> or use the ARIN WHOIS web interface, (or both) - either way, as IP
>> transit carrier, we can now pick up your attestations in an automated
>> fashion. This which improves accuracy and reduces red tape! :)
>> 
>> Hopefully more carriers and IXPs will embrace the ARIN WHOIS data source
>> in their automation toolchain. The code & procedures to make use of this
>> source are open. I'm happy to help you both on-list and off-list.
>> 
>> Kind regards,
>> 
>> Job
>> 
>> ----- End forwarded message -----
>> 
>> 
>> 
>> 
>> -- 
>> ===============================================
>> David Farmer               Email:[log in to unmask]
>> Networking & Telecommunication Services
>> Office of Information Technology
>> University of Minnesota   
>> 2218 University Ave SE        Phone: 612-626-0815
>> Minneapolis, MN 55414-3029   Cell: 612-812-9952
>> ===============================================
>> 
>> To unsubscribe from the MICE-DISCUSS list, click the following link:
>> http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
>> 
> 
> 
> To unsubscribe from the MICE-DISCUSS list, click the following link:
> http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
> 

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010

ATOM RSS1 RSS2



LISTS.IPHOUSE.NET

CataList Email List Search Powered by the LISTSERV Email List Manager