IETF Logo Mail Archive

Re: [Sidrops] WG ADOPTION - draft-madi-sidrops-rush - ENDS 10/12/2020 (Oct 12th)

Di Ma <madi@rpstir.net> Wed, 18 November 2020 07:02 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 814113A0B8B; Tue, 17 Nov 2020 23:02:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 lQntdHgUlCGg; Tue, 17 Nov 2020 23:02:57 -0800 (PST)
Received: from out20-73.mail.aliyun.com (out20-73.mail.aliyun.com [115.124.20.73]) (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 5A0EB3A0C0F; Tue, 17 Nov 2020 23:02:50 -0800 (PST)
X-Alimail-AntiSpam: AC=CONTINUE; BC=0.1164834|-1; CH=green; DM=|CONTINUE|false|; DS=CONTINUE|ham_regular_dialog|0.0132064-0.00113803-0.985656; FP=0|0|0|0|0|-1|-1|-1; HT=ay29a033018047201; MF=madi@rpstir.net; NM=1; PH=DS; RN=7; RT=7; SR=0; TI=SMTPD_---.IyCWIoO_1605682964;
Received: from 172.20.10.2(mailfrom:madi@rpstir.net fp:SMTPD_---.IyCWIoO_1605682964) by smtp.aliyun-inc.com(10.147.43.230); Wed, 18 Nov 2020 15:02:46 +0800
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.20.0.2.21\))
From: Di Ma <madi@rpstir.net>
In-Reply-To: <95A9B418-370C-43F5-8466-3FC157C3F914@puck.nether.net>
Date: Wed, 18 Nov 2020 15:02:44 +0800
Cc: "sidrops-ads@ietf.org" <sidrops-ads@ietf.org>, Guyunan <guyunan@huawei.com>, SIDR Operations WG <sidrops@ietf.org>, SIDROps Chairs <sidrops-chairs@ietf.org>, Melchior Aelmans <melchior@aelmans.eu>, Job Snijders <job@ntt.net>
Content-Transfer-Encoding: quoted-printable
Message-Id: <BBAF2E50-87B7-4A03-9512-E7681BB85E91@rpstir.net>
References: <87imbybjne.wl-morrowc@ops-netman.net> <CALxNLBhjU409LB8pU3Dr287hyKDSW8bHbJiLNPjf4yOSnzc2kg@mail.gmail.com> <C01B0098369B2D4391851938DA6700B717C1D699@DGGEML532-MBX.china.huawei.com> <C4FE2995-87D4-4FF5-9F3D-91D5BE44ED33@rpstir.net> <CAL9jLaZAC9soiJKy856dWexjAmh5=brBnnUOrUjeSHLR_CKJTQ@mail.gmail.com> <3B7B607B-C100-4805-94BE-DC2F597A3CD2@rpstir.net> <87a6vgfb3i.wl-morrowc@ops-netman.net> <X7PYnV3pz9QO5NUY@bench.sobornost.net> <D77FB6ED-2288-4E55-8329-27EC52C8BB37@rpstir.net> <95A9B418-370C-43F5-8466-3FC157C3F914@puck.nether.net>
To: Jared Mauch <jared@puck.nether.net>
X-Mailer: Apple Mail (2.3654.20.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/tSZrc2SdKHfNTfYFj69RiO1TqvA>
Subject: Re: [Sidrops] WG ADOPTION - draft-madi-sidrops-rush - ENDS 10/12/2020 (Oct 12th)
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: Wed, 18 Nov 2020 07:03:00 -0000

Jared,

Thanks for your suggestion.

> 2020年11月18日 14:54，Jared Mauch <jared@puck.nether.net> 写道：
> 
> 
> 
>> On Nov 18, 2020, at 1:48 AM, Di Ma <madi@rpstir.net> wrote:
>> 
>> We don’t make decision for operators but offer them a choice that they can outsource valiation if they have no problem with this fashion.
> 
> Is it perhaps better to think about offering validation as a service to people who can’t or are unable to run their own validators?
> 
> (Thinking of how people may decide to use an off-network DNS resolver so they don’t need to operate one themselves).
> 
> Perhaps this is something larger networks may want to offer to their customers, similar to how they may offer NTP, DNS and other services?

I think this is a reasonable usecase which can be added into RUSH document.

And RUSH can also be used within a large ISP to distribute cache to RTR servers deployed in different ASes.

Di

v2.23.0 | Report a Bug | By Email