Send ARIN-consult mailing list submissions to
arin-consult@arin.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.arin.net/mailman/listinfo/arin-consult
or, via email, send a message with subject or body 'help' to
arin-consult-requ...@arin.net
You can reach the person managing the list at
arin-consult-ow...@arin.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of ARIN-consult digest..."
Today's Topics:
1. Re: [EXTERNAL] - Re: Short summary of requirements (was: Re:
RPKI/IRR Consultation Reminder and Update) (John Curran)
2. Re: Short summary of requirements (was: Re: RPKI/IRR
Consultation Reminder and Update) (Hauge, Chuck P)
----------------------------------------------------------------------
Message: 1
Date: Fri, 15 Sep 2023 12:54:32 +0000
From: John Curran <jcur...@arin.net>
To: Miles McCredie <miles.mccre...@midco.com>
Cc: "<arin-consult@arin.net>" <arin-consult@arin.net>
Subject: Re: [ARIN-consult] [EXTERNAL] - Re: Short summary of
requirements (was: Re: RPKI/IRR Consultation Reminder and Update)
Message-ID: <64428a75-5a03-440e-9e38-08bfcec40...@arin.net>
Content-Type: text/plain; charset="utf-8"
Miles -
Excellent point - we?ll make sure to clarify such at the close of the
consultation.
Thanks!
/John
John Curran
President and CEO
American Registry for Internet Numbers
On Sep 15, 2023, at 8:44 AM, Miles McCredie <miles.mccre...@midco.com> wrote:
One thing that I have been assuming in this discussion that would be good to
make explicit ? any new ROA or route(6) attributes should be exposed and
manageable via API, not just via ARIN Online.
[http://images.midcocomm.com/ES_MidcoLogo.png]
Miles McCredie
Principal Network Engineer II-Core IP
Office: 6052755192
miles.mccre...@midco.com<mailto:miles.mccre...@midco.com>
Midco.com<http://midco.com/>
From: ARIN-consult
<arin-consult-boun...@arin.net<mailto:arin-consult-boun...@arin.net>> On Behalf
Of John Curran
Sent: Friday, September 15, 2023 7:15 AM
To: Adam Thompson <athom...@athompso.net<mailto:athom...@athompso.net>>
Cc: <arin-consult@arin.net<mailto:arin-consult@arin.net>>
<arin-consult@arin.net<mailto:arin-consult@arin.net>>
Subject: [EXTERNAL] - Re: [ARIN-consult] Short summary of requirements (was:
Re: RPKI/IRR Consultation Reminder and Update)
CAUTION: This email originated from outside of MIDCO.
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
Adam -
I believe that would be:
* Set aside some time when you can watch your network
* Go into ARIN Online, and for each ROA, toggle ?Auto-Matching-IRR-Objects?
to On for each ROA ? this will cause automatic generation of matching IRR route
objects.
* Watch your network carefully over the next few hours
* Declare success, and get on with life as usual?
The risk involved would be if the route objects that are automatically created
don?t match your current set and somehow conflict ?
but that?s unlikely since only a ?least-specific? route-object will be created
and any more specifics that you have would take precedence.
Thanks!
/John
John Curran
President and CEO
American Registry for Internet Numbers
On Sep 14, 2023, at 10:03 PM, Adam Thompson <athom...@athompso.net> wrote:
One thing I'm still unclear on after reading many, many words is: if *want*
ARIN to manage everything for me automatically to the maximum extent possible,
but I've already manually created both ROAs and IRR objects, is there a
non-disruptive, non-service-affecting, path to get from my current state into
this brave new fully-automated world?
Thanks,
-Adam Thompson
-----Original Message-----
From: ARIN-consult <arin-consult-boun...@arin.net> On Behalf Of John Curran
Sent: Thursday, September 14, 2023 6:43 PM
To: <arin-consult@arin.net> <arin-consult@arin.net>
Subject: [ARIN-consult] Short summary of requirements (was: Re: RPKI/IRR
Consultation Reminder and Update)
Folks -
Based on the discussion to date, I believe the following approach for
synchronized route object creation for RPKI ROAs in ARIN Online would cover
most of the expressed requirements ?
? In addition to the present ?Auto-renewing? attribute for a ROA, there would
be ?Auto-Matching-IRR-Objects? attribute for ROAs that could be set during ROA
Creation or Manage ROA in ARIN Online
? The ?Auto-Matching-IRR-Objects? attribute could be On or Off, and would
initially be set to the Organizational ?Automatic Matching IRR Object Creation
for ROAs? default value ? which would be On unless/until changed otherwise by
the organization.
? New ROAs created with ?Auto-Matching-IRR-Objects? set to On would result in
the matching route objects being created.
? Customers could manage existing ROAs and turn "Auto-Matching-IRR-Objects? to
On, in which case the matching route objects would be created.
? Existing ROAs with ?Auto-Matching-IRR-Objects? set to On that are then
changed to Off would result in matching route objects being deleted ? but only
if the route objects in question were automatically created.
? Existing ROAs that are deleted or that expire with ?Auto-Matching-IRR-Objects
set to On would result in matching route objects being deleted - but only if
the route objects in question were automatically created.
ARIN would not change the ?Auto-Matching-IRR-Objects? for any existing ROAs,
and these would be set to Off by default ? so as to avoid routing changes that
would otherwise occur at time of matching route object feature rollout.
(Customers with existing ROAs who wished automatic matching route objects to be
created would just have to log into ARIN Online, and manage toggle
Auto-Matching-IRR-Objects to On for each ROA.)
Are there any particular comments or concerns with the above approach?
Thanks!
/John
John Curran
President and CEO
American Registry for Internet Numbers
_______________________________________________
ARIN-Consult
You are receiving this message because you are subscribed to the ARIN Consult
Mailing
List (ARIN-consult@arin.net).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-consult Please contact the ARIN
Member Services
Help Desk at i...@arin.net if you experience any issues.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.arin.net/pipermail/arin-consult/attachments/20230915/ff2513ee/attachment-0001.htm>
------------------------------
Message: 2
Date: Fri, 15 Sep 2023 13:11:58 +0000
From: "Hauge, Chuck P" <chuck.ha...@charter.com>
To: "arin-consult@arin.net" <arin-consult@arin.net>
Subject: Re: [ARIN-consult] Short summary of requirements (was: Re:
RPKI/IRR Consultation Reminder and Update)
Message-ID:
<ch3pr15mb6283ba751547d9f2c677ca49e8...@ch3pr15mb6283.namprd15.prod.outlook.com>
Content-Type: text/plain; charset="iso-8859-1"
I have just one point regarding the below statement, if this strategy is used,
a per RPKI ROA matching IRR Route object toggle combined with default set to
off for existing ROAs. We have 7K+ ROAs over 4 ORGID's, there will need to be
an API created (or extended functionality of existing API) so that we could
edit the ROA record (not actually editing the ROA, that is prefix, AS, and ML
are not changed) to enable/disable this toggle for each ROA. When the API
enables/disables the toggle, an IRR route object will be generated/removed.
ARIN would not change the ?Auto-Matching-IRR-Objects? for any existing
ROAs, and these would be set to Off by default ? so as to avoid routing changes
that would otherwise occur at time of matching route object feature rollout.
(Customers with existing ROAs who wished automatic matching route
objects to be created would just have to log into ARIN Online, and manage
toggle Auto-Matching-IRR-Objects to On for each ROA.)
Regards,
-------------------------------------------------------------------------------------------------------------------------------------
CHUCK HAUGE | CCNP, MBA | IP Management - Systems Engineer IV | c. 303.915.5512
| o. 303.323.6056
? 6175 South Willow Drive |? Greenwood Village, CO? 80111
-------------------------------------------------------------------------------------------------------------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
ARIN-consult mailing list
ARIN-consult@arin.net
https://lists.arin.net/mailman/listinfo/arin-consult
------------------------------
End of ARIN-consult Digest, Vol 100, Issue 8
********************************************
