MIME-Version: 1.0
References: <154656623575.29677.9867680687994360294.idtracker@ietfa.amsl.com>
 <CAHw9_iLku6x8Yy=uTb_s9f8=gL2YwppgJS7wVdGXK-sHqADCyQ@mail.gmail.com>
 <3321b6de-ef69-5d3c-b4b0-31865ddca224@foobar.org>
 <096ED0B2-1FBC-4CDC-B73D-28D61F08AC24@rpstir.net>
In-Reply-To: <096ED0B2-1FBC-4CDC-B73D-28D61F08AC24@rpstir.net>
From: Christopher Morrow <christopher.morrow@gmail.com>
Date: Sun, 10 Mar 2019 18:21:40 -0400
Message-ID: <CAL9jLabwSG=0i0B3c6o2GXX4Z2rZs4k43t4Cp9N-8TMeBnnH7A@mail.gmail.com>
To: Di Ma <madi@rpstir.net>
Cc: Nick Hilliard <nick@foobar.org>, Chris Morrow <morrowc@ops-netman.net>, 
 SIDROps Chairs <sidrops-chairs@ietf.org>, SIDR Operations WG <sidrops@ietf.org>,
 IESG_Secretary <iesg-secretary@ietf.org>, Warren Kumari <warren@kumari.net>
Content-Type: multipart/alternative; boundary="000000000000f6d37c0583c4e131"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/KrqOK1DVwNI6luVe4H6PghkTfbc>
Subject: Re: [Sidrops] Publication has been requested for
 draft-ietf-sidrops-lta-use-cases-04
Precedence: list

--000000000000f6d37c0583c4e131
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

howdy! I think the authors/objectors reached a conclusion on their
differences... That is reflected in today's draft update to drafting system=
:
   https://tools.ietf.org/html/draft-ietf-sidrops-lta-use-cases - v05

Let's poke/poke the buttons and move this back into IESG hands (which I'm
doing now).

On Sat, Jan 12, 2019 at 5:44 PM Di Ma <madi@rpstir.net> wrote:

> Nick,
>
> > =E5=9C=A8 2019=E5=B9=B41=E6=9C=8813=E6=97=A5=EF=BC=8C06:20=EF=BC=8CNick=
 Hilliard <nick@foobar.org> =E5=86=99=E9=81=93=EF=BC=9A
> >
> > Warren Kumari wrote on 12/01/2019 18:49:
> >> I'm returning this document to the Working Group because I do not see
> sufficient evidence of consensus.
> >> With no hats - I personally believe that documenting the use cases is
> useful, and would like to see this / a document describe the operational
> practices of having a local TA.
> >
> > this is likely to be useful from the point of view of dealing with long
> term concerns about centralisation of control of the global routing
> infrastructure, that have been aired from time to time in various fora,
> both private and public.  The three example cases are realistic (cf: RIPE
> NCC court order regarding registration of resources in 2011).
> >
> > It would also be important to note that the local trust anchor mechanis=
m
> suggested here could also be created to override legitimate announcements=
,
> e.g. states who wish to control the routing tables of service providers i=
n
> their legal jurisdiction.  Knives make no judgement about what they cut
> through.
> >
> > I support publication of the draft.  It may need more content, e.g.
> description of methods to implement the ideas that it suggests.
>
>
> There is a standardized way to do so, as specified by RFC 8416, called
> SLURM, which by the way has been supported by some RP software such as
> Routinator and RPSTIR.
>
> I agree with what Steve suggested, draft-ietf-sidrops-lta-use-cases shoul=
d
> cite SLURM.
>
>
> Di
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops
>

--000000000000f6d37c0583c4e131
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">howdy! I think the authors/objectors reac=
hed a conclusion on their differences... That is reflected in today&#39;s d=
raft update to drafting system:<br>=C2=A0 =C2=A0<a href=3D"https://tools.ie=
tf.org/html/draft-ietf-sidrops-lta-use-cases">https://tools.ietf.org/html/d=
raft-ietf-sidrops-lta-use-cases</a> - v05</div><div dir=3D"ltr"><br></div><=
div>Let&#39;s poke/poke the buttons and move this back into IESG hands (whi=
ch I&#39;m doing now).</div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Sat, Jan 12, 2019 at 5:44 PM Di Ma &lt;<a =
href=3D"mailto:madi@rpstir.net">madi@rpstir.net</a>&gt; wrote:<br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex">Nick,<br>
<br>
&gt; =E5=9C=A8 2019=E5=B9=B41=E6=9C=8813=E6=97=A5=EF=BC=8C06:20=EF=BC=8CNic=
k Hilliard &lt;<a href=3D"mailto:nick@foobar.org" target=3D"_blank">nick@fo=
obar.org</a>&gt; =E5=86=99=E9=81=93=EF=BC=9A<br>
&gt; <br>
&gt; Warren Kumari wrote on 12/01/2019 18:49:<br>
&gt;&gt; I&#39;m returning this document to the Working Group because I do =
not see sufficient evidence of consensus.<br>
&gt;&gt; With no hats - I personally believe that documenting the use cases=
 is useful, and would like to see this / a document describe the operationa=
l practices of having a local TA.<br>
&gt; <br>
&gt; this is likely to be useful from the point of view of dealing with lon=
g term concerns about centralisation of control of the global routing infra=
structure, that have been aired from time to time in various fora, both pri=
vate and public.=C2=A0 The three example cases are realistic (cf: RIPE NCC =
court order regarding registration of resources in 2011).<br>
&gt; <br>
&gt; It would also be important to note that the local trust anchor mechani=
sm suggested here could also be created to override legitimate announcement=
s, e.g. states who wish to control the routing tables of service providers =
in their legal jurisdiction.=C2=A0 Knives make no judgement about what they=
 cut through.<br>
&gt; <br>
&gt; I support publication of the draft.=C2=A0 It may need more content, e.=
g. description of methods to implement the ideas that it suggests.<br>
<br>
<br>
There is a standardized way to do so, as specified by RFC 8416, called SLUR=
M, which by the way has been supported by some RP software such as Routinat=
or and RPSTIR.<br>
<br>
I agree with what Steve suggested, draft-ietf-sidrops-lta-use-cases should =
cite SLURM.<br>
<br>
<br>
Di<br>
_______________________________________________<br>
Sidrops mailing list<br>
<a href=3D"mailto:Sidrops@ietf.org" target=3D"_blank">Sidrops@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sidrops" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/sidrops</a><br>
</blockquote></div>

--000000000000f6d37c0583c4e131--