<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:"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;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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">
<div class="WordSection1">
<p class="MsoNormal">I’m not entirely certain these are problems that operators necessarily concern themselves with. Datacenters and specialized service networks, perhaps, but not internet service providers. Mainly because the internet is a relatively lossy
beast with several performance inhibitors that constantly lie outside an operator’s control (i.e. bad filters seem to break the entire United States eastern seaboard at least once a year.) I’d wager most of us are not concerned with the kind of failure scenario
you’re describing simply because there is no demand from our customers for sub-millisecond remediation. At least not from the ones who are willing to pay for it.
<span style="font-family:"Segoe UI Emoji",sans-serif">😉</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">---<o:p></o:p></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal">Chris<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> NANOG <nanog-bounces+chris.wright=commnetbroadband.com@nanog.org>
<b>On Behalf Of </b>Matthew Nance Hall<br>
<b>Sent:</b> Friday, August 5, 2022 12:24 PM<br>
<b>To:</b> nanog@nanog.org<br>
<b>Cc:</b> 'Ramakrishnan Durairajan' <ram@cs.uoregon.edu>; 'PAUL R BARFORD' <pb@cs.wisc.edu>; klaus-tycho.foerster@tu-dortmund.de<br>
<b>Subject:</b> Question re. operator tools - somewhere betwixt fast failover and TE<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" align="left" width="100%" style="width:100.0%">
<tbody>
<tr>
<td style="background:#A6A6A6;padding:5.25pt 1.5pt 5.25pt 1.5pt"></td>
<td width="100%" style="width:100.0%;background:#EAEAEA;padding:5.25pt 3.75pt 5.25pt 11.25pt">
<div>
<p class="MsoNormal" style="mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:9.0pt;font-family:"Segoe UI",sans-serif;color:#212121">You don't often get email from
<a href="mailto:mhall@cs.uoregon.edu">mhall@cs.uoregon.edu</a>. <a href="https://aka.ms/LearnAboutSenderIdentification">
Learn why this is important</a><o:p></o:p></span></p>
</div>
</td>
<td width="75" style="width:56.25pt;background:#EAEAEA;padding:5.25pt 3.75pt 5.25pt 3.75pt;align:left">
</td>
</tr>
</tbody>
</table>
<div>
<p>Hello,<o:p></o:p></p>
<p>I'm Matthew Nance-Hall (Matt), a PhD Candidate at the University of Oregon working with Prof. Ram Durairajan (UO), Prof. Paul Barford (UW-Madison) and Prof. Klaus-Tycho Foerster (TU Dortmund).<o:p></o:p></p>
<p>I was hoping someone could shed operator perspective on a research question we're exploring. We're interested in the timescales and mechanisms used to adjust data paths and wondering where gaps might exist between traffic engineering (TE), fast fail-over,
and routing.<br>
<br>
We're specifically curious about spatio-temporal characteristics where gaps might exist. For example, the topological scope of an event (congestion or outage) and the timescale for adjustments to be made. I'm aware there are operator tools such as fast fail-over
and TE for making changes confined to single links or across the whole network but wonder if there is a place for events that have broader scope (beyond a single link but less than the whole network) where new inquiry and exploration would be welcome.
<br>
<br>
Thank you, <br>
Matt<o:p></o:p></p>
</div>
</div>
</body>
</html>