IETF Logo Mail Archive

Re: [Sidrops] Publication has been requested for draft-ietf-sidrops-lta-use-cases-04

Christopher Morrow <christopher.morrow@gmail.com> Sun, 10 March 2019 22:21 UTC

Return-Path: <christopher.morrow@gmail.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0D7412797A; Sun, 10 Mar 2019 15:21:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AguQ1c6Qlpl5; Sun, 10 Mar 2019 15:21:52 -0700 (PDT)
Received: from mail-it1-x12b.google.com (mail-it1-x12b.google.com [IPv6:2607:f8b0:4864:20::12b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EEFA12D4EB; Sun, 10 Mar 2019 15:21:52 -0700 (PDT)
Received: by mail-it1-x12b.google.com with SMTP id f186so11129921ita.0; Sun, 10 Mar 2019 15:21:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=q2GrltMy7X9BSkghaji58GdDY4nW2HfJ3hrR3Dgfo6w=; b=ALJGUY8hYkFQ93OVPcHq08K0Iby821EDg6GurAjKJhYqOOYIqjqEWLlB6zAp3oHOFu XpkbhSze8L4ds3JMVAlLrVAT28abflCTSOoTr3eHX7mzIewfrKJ7y2a6j2Y96hAcZ9Eg Bgws5au0rc1E1l/wltnjmF/fLFJ5IW5VItQ0y09w10GF0Lz/SQmyjeiLmViCKUBYV/Cf +MC596hih6PDjwwp4bR5OTCQPieOQdCkBiipK53CIEEGZ+4bRniDykRrYsKPadS8rhTN mPFh95RygMo4ghpQK3Rm5i6T2n+3R4FJnry3falivEKiIgDZn/O4wAe32moskyME9mSE ftcg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=q2GrltMy7X9BSkghaji58GdDY4nW2HfJ3hrR3Dgfo6w=; b=spOSKyXjNvPPvV+EJP13A0PU5/pSFNhAj3QBHVEY1dvbyjO4O2bbfzcLUKCYdl4SV2 QCiHlsCYGpYPbhdP/Vli7hnz1shFW/pAv/S9uULZ+2S3WJSYYwOEW+sjv7Q0pD74pKXd vbHwmv97lL1g2LDvQ9QgjaT+vxpmrrZyXh5Qwq3OqQYAqhkcuqkCwdYy+P8PJslCJhnv IUm43EowdyP607ZTBRFWgAtiUpjBWlHeUfa1UwW+C8h7HfVpiT1Iwihg/wieCa0MOOry DdmC0gSuVREzXQzhvi+4mEm40YwBKkHbd86cn18MaY6nGfUwmucCo5GKN+Glq99Xd/Sm mBKw==
X-Gm-Message-State: APjAAAWBg2PAGtgZkGaqe9YjsvdJlrVBfUEkp8DdPDhBfTvnRZXD+ndK be4kMoPTba44xlci/HloqOcEBMZtCkmyXR0CrNM=
X-Google-Smtp-Source: APXvYqxY/fXggUpbHrS3HDv+3wTebLjSFL3TxhCbrATzYEcw+br8ltPXTnBrbe3SUH6dkpB+LuJUYMO7Dguni8pnM38=
X-Received: by 2002:a24:79d1:: with SMTP id z200mr15476979itc.53.1552256511429; Sun, 10 Mar 2019 15:21:51 -0700 (PDT)
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
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Mar 2019 22:22:06 -0000

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,
>
> > 在 2019年1月13日，06:20，Nick Hilliard <nick@foobar.org> 写道：
> >
> > 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 mechanism
> suggested here could also be created to override legitimate announcements,
> e.g. states who wish to control the routing tables of service providers in
> 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 should
> cite SLURM.
>
>
> Di
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops
>

v2.23.0 | Report a Bug | By Email