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

Di Ma <madi@rpstir.net> Sat, 12 January 2019 22:43 UTC

Return-Path: <madi@rpstir.net>
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 B686C131133; Sat, 12 Jan 2019 14:43:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 epJDY6rnFmYE; Sat, 12 Jan 2019 14:43:48 -0800 (PST)
Received: from out20-86.mail.aliyun.com (out20-86.mail.aliyun.com [115.124.20.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 776F5131132; Sat, 12 Jan 2019 14:43:46 -0800 (PST)
X-Alimail-AntiSpam: AC=CONTINUE; BC=0.09190307|-1; CH=green; FP=0|0|0|0|0|-1|-1|-1; HT=e01l07391; MF=madi@rpstir.net; NM=1; PH=DS; RN=6; RT=6; SR=0; TI=SMTPD_---.DksGQ4W_1547333017;
Received: from 192.168.3.18(mailfrom:madi@rpstir.net fp:SMTPD_---.DksGQ4W_1547333017) by smtp.aliyun-inc.com(10.147.43.230); Sun, 13 Jan 2019 06:43:38 +0800
Content-Type: text/plain; charset=gb2312
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Di Ma <madi@rpstir.net>
In-Reply-To: <3321b6de-ef69-5d3c-b4b0-31865ddca224@foobar.org>
Date: Sun, 13 Jan 2019 06:43:35 +0800
Cc: Warren Kumari <warren@kumari.net>, Chris Morrow <morrowc@ops-netman.net>, SIDROps Chairs <sidrops-chairs@ietf.org>, sidrops@ietf.org, IESG_Secretary <iesg-secretary@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <096ED0B2-1FBC-4CDC-B73D-28D61F08AC24@rpstir.net>
References: <154656623575.29677.9867680687994360294.idtracker@ietfa.amsl.com> <CAHw9_iLku6x8Yy=uTb_s9f8=gL2YwppgJS7wVdGXK-sHqADCyQ@mail.gmail.com> <3321b6de-ef69-5d3c-b4b0-31865ddca224@foobar.org>
To: Nick Hilliard <nick@foobar.org>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/gdE0aETKiqsyfyTL7U4lVLFgAx8>
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: Sat, 12 Jan 2019 22:43:54 -0000

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