[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Level 3's IRR Database

Subject: Level 3's IRR Database
From: randy at psg.com (Randy Bush)
Date: Mon, 31 Jan 2011 23:16:28 +0900
In-reply-to: <m2wrll5g2t.wl%[email protected]>
References: <[email protected]> <[email protected]> <[email protected]> <m2sjwa84td.wl%[email protected]> <[email protected]> <m21v3t8rtd.wl%[email protected]> <[email protected]> <m2wrll5g2t.wl%[email protected]>

> when there is no roa for the arriving prefix, a roa for the covering
> prefix is used.  see draft-pmohapat-sidr-pfx-validate-07.txt.

which, btw, is why draft-ietf-sidr-rpki-origin-ops-04.txt warns

   Before issuing a ROA for a block, an operator MUST ensure that any
   sub-allocations from that block which are announced by others (e.g.
   customers) have ROAs in play.  Otherwise, issuing a ROA for the
   super-block will cause the announcements of sub-allocations with no
   ROAs to be Invalid.

randy

References:
- Level 3's IRR Database
  - From: aa at tenet.ac.za (Andrew Alston)
- Level 3's IRR Database
  - From: carlosm3011 at gmail.com (Carlos Martinez-Cagnazzo)
- Level 3's IRR Database
  - From: nick at foobar.org (Nick Hilliard)
- Level 3's IRR Database
  - From: randy at psg.com (Randy Bush)
- Level 3's IRR Database
  - From: randy at psg.com (Randy Bush)
- Level 3's IRR Database
  - From: jbates at brightok.net (Jack Bates)
- Level 3's IRR Database
  - From: randy at psg.com (Randy Bush)

Prev by Date: Level 3's IRR Database
Next by Date: Level 3's IRR Database
Previous by thread: Level 3's IRR Database
Next by thread: Level 3's IRR Database
Index(es):
- Date
- Thread