Re: [rfc-i] whose on first

Carsten Bormann <cabo@tzi.org> Fri, 19 February 2021 22:36 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D16873A0C44; Fri, 19 Feb 2021 14:36:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.648
X-Spam-Level:
X-Spam-Status: No, score=-7.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-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 iB3atzmEed0m; Fri, 19 Feb 2021 14:36:16 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 600393A0C59; Fri, 19 Feb 2021 14:36:16 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id AF086F40721; Fri, 19 Feb 2021 14:36:10 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 66F71F40721 for <rfc-interest@rfc-editor.org>; Fri, 19 Feb 2021 14:36:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NAdTr1klBknc for <rfc-interest@rfc-editor.org>; Fri, 19 Feb 2021 14:36:05 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) by rfc-editor.org (Postfix) with ESMTPS id 61E66F406DB for <rfc-interest@rfc-editor.org>; Fri, 19 Feb 2021 14:36:05 -0800 (PST)
Received: from [192.168.217.118] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Dj5yd2MMbzyWt; Fri, 19 Feb 2021 23:36:09 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <3F9B1FDA-20C6-4112-83B2-44EB9C64DBFE@psg.com>
Date: Fri, 19 Feb 2021 23:36:08 +0100
X-Mao-Original-Outgoing-Id: 635466968.82022-fcbec5b28b586a84ffc9fdef12a0fa03
Message-Id: <3267FC6B-932B-4036-9EC4-DA14F0A04616@tzi.org>
References: <m2wnv3n1sz.wl-randy@psg.com> <CA975ECC-B70A-4856-8760-443740DB5531@tzi.org> <3F9B1FDA-20C6-4112-83B2-44EB9C64DBFE@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Subject: Re: [rfc-i] whose on first
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: XML2RFC Interest Group <xml2rfc@ietf.org>, RFC Interest Group <rfc-interest@rfc-editor.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>

On 2021-02-19, at 23:32, Randy Bush <randy@psg.com> wrote:
> 
> hi carsten,
> 
> my rsync does not get it

I don’t think we can rsync bibxml from the datatracker yet.
Might be interesting to pull something together that does the equivalent over HTTP so one can then rsync from that…  But the datatracker is not very fast, so this might overload it.

Grüße, Carsten

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest