Question about mismatch of origin ASN in parent and more specific route object

• Subject: Question about mismatch of origin ASN in parent and more specific route object
• From: me at anuragbhatia.com (Anurag Bhatia)
• Date: Thu, 19 Sep 2019 04:04:52 +0530

Hello everyone


Trying to understand the case from operators here who generate IRR based
filters.



Say if a given example:

AS X originating 2001:DB8::/32 with IRR route object having AS X in the
origin
AS X originating 2001:DB8::/48 with IRR route object having AS Y in the
origin


Now for folks who are generating filters, will your tools filter
2001:DB8::/48 because there's a more specific IRR route object which says
AS Y while prefix is coming from AS X?
Or since generation is based on ASNs (as known directly or resolved via AS
SETs) your tools will just generate filter for AS X allowing 2001:DB8::/32
(upto say /48) and won't really for mismatching route object for
2001:DB8::/48?



Thanks.

-- 


Anurag Bhatia
anuragbhatia.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190919/06da3a69/attachment.html>

• Follow-Ups:
  • Question about mismatch of origin ASN in parent and more specific route object
    • From: jared at puck.nether.net (Jared Mauch)

• Prev by Date: Elad Cohen
• Next by Date: Question about mismatch of origin ASN in parent and more specific route object
• Previous by thread: Contact at OLM LLC or Windstream Communications
• Next by thread: Question about mismatch of origin ASN in parent and more specific route object
• Index(es):
  • Date
  • Thread