<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1779526251;
mso-list-template-ids:-1582817986;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word;overflow-wrap: break-word;-webkit-nbsp-mode: space;line-break:after-white-space">
<div class="WordSection1">
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<P style="FONT-SIZE: 10pt; FONT-FAMILY: ARIAL">
<TABLE style="WIDTH: 447px" cellSpacing=0 cellPadding=0 border=0>
<TBODY>
<TR>
<TD
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; WIDTH: 172px; PADDING-TOP: 10px; PADDING-LEFT: 0px"
vAlign=middle align=left><IMG border=0
src="http://images.midcocomm.com/ES_MidcoLogo.png"></TD>
<TD
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; WIDTH: 275px; PADDING-TOP: 10px; PADDING-LEFT: 20px"
vAlign=middle>
<P style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><STRONG
style="FONT-SIZE: 12pt"><SPAN style="FONT-SIZE: 12pt"><STRONG
style="FONT-SIZE: 12pt">Miles McCredie</STRONG>
</SPAN></STRONG><BR>Principal Network Engineer II-Core IP </P>
<P style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Office: 6052755192 <BR><SPAN
style="COLOR: #0072bc">Miles.McCredie@midco.com </SPAN></P>
<P style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><STRONG>Midco.com</STRONG>
</P></TD></TR>
<TR>
<TD
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; WIDTH: 447px; PADDING-TOP: 10px"
vAlign=top colSpan=2></TD></TR>
<TR>
<TD
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; WIDTH: 447px; PADDING-TOP: 5px"
vAlign=top colSpan=2></TD></TR></TBODY></TABLE></P><div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> ARIN-consult <arin-consult-bounces@arin.net> <b>
On Behalf Of </b>John Curran<br>
<b>Sent:</b> Friday, September 15, 2023 7:15 AM<br>
<b>To:</b> Adam Thompson <athompso@athompso.net><br>
<b>Cc:</b> <arin-consult@arin.net> <arin-consult@arin.net><br>
<b>Subject:</b> [EXTERNAL] - Re: [ARIN-consult] Short summary of requirements (was: Re: RPKI/IRR Consultation Reminder and Update)<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p align="center" style="text-align:center"><strong><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:#B20E12">CAUTION:</span></strong><span style="color:#B20E12"> This email originated from outside of
<strong><span style="font-family:"Calibri",sans-serif">MIDCO</span></strong>. <br>
<em><span style="font-family:"Calibri",sans-serif">Do not click links or open attachments unless you recognize the sender and know the content is safe.</span></em></span><o:p></o:p></p>
<div>
<p class="MsoNormal">Adam - <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I believe that would be:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Set aside some time when you can watch your network <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
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. <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Watch your network carefully over the next few hours<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Declare success, and get on with life as usual…<o:p></o:p></li></ul>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The risk involved would be if the route objects that are automatically created don’t match your current set and somehow conflict – <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">but that’s unlikely since only a “least-specific” route-object will be created and any more specifics that you have would take precedence.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">/John<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">John Curran<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">President and CEO<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">American Registry for Internet Numbers<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On Sep 14, 2023, at 10:03 PM, Adam Thompson <athompso@athompso.net> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">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?<br>
Thanks,<br>
-Adam Thompson<br>
<br>
<br>
-----Original Message-----<br>
From: ARIN-consult <arin-consult-bounces@arin.net> On Behalf Of John Curran<br>
Sent: Thursday, September 14, 2023 6:43 PM<br>
To: <arin-consult@arin.net> <arin-consult@arin.net><br>
Subject: [ARIN-consult] Short summary of requirements (was: Re: RPKI/IRR Consultation Reminder and Update)<br>
<br>
Folks - <br>
<br>
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 –
<br>
<br>
– 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<br>
– 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.
<br>
<br>
– New ROAs created with “Auto-Matching-IRR-Objects” set to On would result in the matching route objects being created.<br>
– Customers could manage existing ROAs and turn "Auto-Matching-IRR-Objects” to On, in which case the matching route objects would be created.<br>
<br>
– 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.<br>
– 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.<br>
<br>
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.
<br>
(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.)
<br>
<br>
Are there any particular comments or concerns with the above approach?<br>
<br>
Thanks!<br>
/John<br>
<br>
John Curran<br>
President and CEO<br>
American Registry for Internet Numbers<br>
<br>
<br>
<br>
_______________________________________________<br>
ARIN-Consult<br>
You are receiving this message because you are subscribed to the ARIN Consult Mailing<br>
List (ARIN-consult@arin.net).<br>
Unsubscribe or manage your mailing list subscription at:<br>
https://lists.arin.net/mailman/listinfo/arin-consult Please contact the ARIN Member Services<br>
Help Desk at info@arin.net if you experience any issues.<o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>