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

Chris Morrow <morrowc@ops-netman.net> Tue, 17 November 2020 11:59 UTC

Return-Path: <morrowc@ops-netman.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 17BB73A1183; Tue, 17 Nov 2020 03:59:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.099
X-Spam-Level:
X-Spam-Status: No, score=-1.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 9OrM3XVR4oUY; Tue, 17 Nov 2020 03:59:16 -0800 (PST)
Received: from relay.ops-netman.net (relay.ops-netman.net [192.110.255.59]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7FBA3A1131; Tue, 17 Nov 2020 03:59:15 -0800 (PST)
Received: from mail.ops-netman.net (mail.ops-netman.net [199.168.90.119]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by relay.ops-netman.net (Postfix) with ESMTPS id E89363C1E1E; Tue, 17 Nov 2020 11:59:13 +0000 (UTC)
Received: from mailserver.ops-netman.net.ops-netman.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.ops-netman.net (Postfix) with ESMTPSA id BFF4A23D; Tue, 17 Nov 2020 11:59:13 +0000 (UTC)
Date: Tue, 17 Nov 2020 11:59:13 +0000
Message-ID: <87a6vgfb3i.wl-morrowc@ops-netman.net>
From: Chris Morrow <morrowc@ops-netman.net>
To: Di Ma <madi@rpstir.net>
Cc: Christopher Morrow <christopher.morrow@gmail.com>, SIDROps Chairs <sidrops-chairs@ietf.org>, "sidrops-ads@ietf.org" <sidrops-ads@ietf.org>, Guyunan <guyunan@huawei.com>, SIDR Operations WG <sidrops@ietf.org>, Chris Morrow <morrowc@ops-netman.net>, Melchior Aelmans <melchior@aelmans.eu>
In-Reply-To: <3B7B607B-C100-4805-94BE-DC2F597A3CD2@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>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.2 Mule/6.0 (HANACHIRUSATO)
Organization: Operations Network Management, Ltd.
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=ISO-2022-JP
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/PqDelJTMt2P-CmqmTkz7d5VC_QM>
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: Tue, 17 Nov 2020 11:59:21 -0000

On Tue, 17 Nov 2020 08:21:05 +0000,
Di Ma <madi@rpstir.net> wrote:
> 
> Chris,
> 
> We authors have removed AS0 usecase for RUSH re Job’s concern.
> 
> And we also made some editorial change to articulate HTTPs as transport where needed, re Yunan’s suggestion.
> 
> Please consider whether it is ready to be adopted.
> 

ok, awesome.

Can yunan/job speak up if their concerns are NOT met at this time?

If they don't speak up in an hour I think we can consider this adopted
and ask the authors to submit the appropriately re-named draft :)

-chris

> Thanks.
> 
> Di
> 
> 
> > 2020年10月22日 22:42,Christopher Morrow <christopher.morrow@gmail.com> 写道:
> > 
> > Howdy folks,
> > We had 2 authors and 1 not-author reply here... Are there other folks
> > interested in moving this forward? or working on this in the WG over
> > the next few meeting slots/periods?
> > 
> > -chris
> > 
> > On Fri, Oct 9, 2020 at 6:51 AM Di Ma <madi@rpstir.net> wrote:
> >> 
> >> Yunan,
> >> 
> >>> 2020年10月9日 14:41,Guyunan <guyunan@huawei.com> 写道:
> >>> 
> >>> Seems quite useful for local management of validated cache. A small suggestion, maybe the authors can further clarify the use of HTTP and HTTPs, whether HTTPs is mandatory, or it’s optional using either HTTP only or HTTPs.
> >> 
> >> 
> >> A very good catch.
> >> 
> >> I think https is default at least as it is used in the name of this draft literally.
> >> 
> >> But I see a potential that http can work if IPsec has been established between two cache servers.
> >> 
> >> We can discuss it further if adopted as a WG item.
> >> 
> >> Di
> >> 
> >>> 
> >>> Support adoption.
> >>> 
> >>> BR,
> >>> 
> >>> Yunan
> >>> 
> >>> From: Sidrops [mailto:sidrops-bounces@ietf.org] On Behalf Of Melchior Aelmans
> >>> Sent: Thursday, October 1, 2020 12:51 AM
> >>> To: Chris Morrow <morrowc@ops-netman.net>
> >>> Cc: SIDROps Chairs <sidrops-chairs@ietf.org>rg>; SIDR Operations WG <sidrops@ietf.org>rg>; sidrops-ads@ietf.org
> >>> Subject: Re: [Sidrops] WG ADOPTION - draft-madi-sidrops-rush - ENDS 10/12/2020 (Oct 12th)
> >>> 
> >>> As a co-author I support adoption by the WG.
> >>> 
> >>> THanks!
> >>> Melchior
> >>> 
> >>> On Mon, Sep 28, 2020 at 6:38 AM Chris Morrow <morrowc@ops-netman.net> wrote:
> >>> 
> >>> Howdy,
> >>> 
> >>> Please consider this the start of a WG Adoption call for the subject
> >>> draft, the abstract of which is:
> >>> 
> >>>  "This document defines a method for transferring RPKI validated cache
> >>>   update information in JSON object format over HTTPs."
> >>> 
> >>> The URL of which is:
> >>>  https://datatracker.ietf.org/doc/html/draft-madi-sidrops-rush-02
> >>> 
> >>> Please give this a read-through and consider if the work is appropriate
> >>> for the WG to work on.
> >>> 
> >>> thanks!
> >>> -chris
> >>> co-chair-persona
> >>> 
> >>> _______________________________________________
> >>> Sidrops mailing list
> >>> Sidrops@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/sidrops
> >>> _______________________________________________
> >>> Sidrops mailing list
> >>> Sidrops@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/sidrops
> >> 
> >> _______________________________________________
> >> Sidrops mailing list
> >> Sidrops@ietf.org
> >> https://www.ietf.org/mailman/listinfo/sidrops
> > 
> > _______________________________________________
> > Sidrops mailing list
> > Sidrops@ietf.org
> > https://www.ietf.org/mailman/listinfo/sidrops