[as112-ops] ROA for AS112 prefixes

[Warren Kumari]

On Mon, Jul 5, 2021 at 9:39 PM Rob Seastrom <rs-lists at seastrom.com> wrote:
>
>
> So is there a problem here or not?  I forwarded this off to my colleagues on the ARIN AC, and there are now two of us there who think it should be possible to just issue a ROA like any other prefix (and it seems that Joe is substantially in agreement?).

Yup, as far as I can see, there just needs to be a ROA for AS112 to
announce the AS112 space, but perhaps I'm missing something obvious?

E.g:
wkumari at rtr1.pao> show route 192.175.48.0/24

inet.0: 857958 destinations, 1036603 routes (857953 active, 0
holddown, 5 hidden)
@ = Routing Use Only, # = Forwarding Use Only
+ = Active Route, - = Last Active, * = Both

192.175.48.0/24    *[BGP/170] 2w2d 16:42:30, MED 0, localpref 200,
from 206.80.238.253
                      AS path: 112 I, validation-state: unknown
                    >  to 206.80.238.252 via ge-2/0/2.0
                       to 216.218.236.9 via ge-2/0/1.0
                    [BGP/170] 2w2d 16:42:27, MED 0, localpref 200,
from 206.80.238.254
                      AS path: 112 I, validation-state: unknown
                    >  to 206.80.238.252 via ge-2/0/2.0
                    [BGP/170] 2w2d 16:42:37, localpref 100
                      AS path: 6939 112 I, validation-state: unknown
                    >  to 216.218.236.9 via ge-2/0/1.0


A ROA for 192.175.48.0/24 , AS112 would do exactly what we want, no?
W

W

>
> -r
>
>
> On Jul 5, 2021, at 1:53 PM, Joe Abley <jabley at hopcount.ca> wrote:
>
> On 5 Jul 2021, at 08:43, Aleksi Suhonen <as112-ops at trex.fi> wrote:
>
> This issue has been revisited about once a year, and I believe DNS-OARC is slowly working on some solution. However, there is a big problem:
>
> Most AS112 addresses are assigned directly by IANA, but ROAs can only be created for address space assigned by RIRs.
>
>
> From RFC 7534 section 7.1:
>
>    The autonomous system number 112, the IPv4 prefix 192.175.48.0/24,
>    and the IPv6 prefix 2620:4f:8000::/48 were assigned by ARIN.
>
>    The IPv4 prefix 192.31.196.0/24 and the IPv6 prefix 2001:4:112::/48,
>    used for DNAME redirection AS112 service, were assigned by the IANA
>    [RFC7535].
>
> Confirmation of the assertions in the first paragraph are easy to verify via whois.arin.net.
>
> I am not aware of any relative measurements of popularity of the delegation (RFC 7534) and redirection (RFC 7535) approaches, but since the reverse mappings for RFC 1918 nets use delegation I would imagine that that's where the majority of the traffic is.
>
> Since the two routes associated with that approach (192.175.48.0/24 and 2620:4f:8000::/48) were both assigned by ARIN, since the origin AS was also assigned by ARIN and since all three of those number resources are registered at ARIN as being managed by DNS-OARC, I don't see many obstacles here.
>
>
> Joe
> _______________________________________________
> as112-ops mailing list
> as112-ops at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/as112-ops
> as112.net administrative requests
> ops at as112.net
>
>
> _______________________________________________
> as112-ops mailing list
> as112-ops at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/as112-ops
> as112.net administrative requests
> ops at as112.net



-- 
The computing scientist’s main challenge is not to get confused by the
complexities of his own making.
  -- E. W. Dijkstra