IETF Logo Mail Archive

Re: [xml2rfc] [rfc-i] Script to generate RFC reference including abstract?

"Andrew G. Malis" <agmalis@gmail.com> Sun, 24 January 2021 21:39 UTC

Return-Path: <agmalis@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 812963A0B9B; Sun, 24 Jan 2021 13:39:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 mpadAIYvt_pf; Sun, 24 Jan 2021 13:39:19 -0800 (PST)
Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (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 D4C893A0B92; Sun, 24 Jan 2021 13:39:18 -0800 (PST)
Received: by mail-qk1-x72d.google.com with SMTP id x81so7922419qkb.0; Sun, 24 Jan 2021 13:39:18 -0800 (PST)
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=9b33rEzdnCTiRLPxbvB1zfeEoULcXrCKQvwFdsrCPpg=; b=nfzKlxV0PYUVhOzqsz7OgADgQX6nz36wbo2GYwr58aO6+6/BGGzMSN7X3qt1S0jUlU imwpi//bVvOVBhOy5sGCkzcq7ko+o0KpW3byixACHx/jmIVnHJ2Tf3kj5eOvTHmxCei9 5iz96nPPO/wkYd9ainhECnncxEBR27yl1U2QHpnN70cN3kM0z2UtJPOmDo6Vh+O+5Hpn u9Vs3Unb9v7OxBdaskDhnzc3a48ER414QfE8WMThLaya6pOxkvFaGAYSdwaZ26txqbcV 7bMLI7jdzg9kwlHaoV7KP13mYsQ75LEI+4n07AtaqAkuLXGW0+v5qBaVXfCpiqXx5RR2 8unw==
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=9b33rEzdnCTiRLPxbvB1zfeEoULcXrCKQvwFdsrCPpg=; b=ixnSRD9JGd7/xsrRjq5sdwjFnT9q8/WaFpaTTYvXr7g4J/TBd5OzEhfN7XRXKEda8U EkXopaX9sFHhBrtio7QjaI2lt7nuBpeKrFgNUUVkf1ug79Egsbrubfdoa89rizLXRQpT 8IH3Dgcff0XdiKzUPbWbb1ndeoA6VogeX7xdJDkTxW9uk1dzEMgLSbgs3obbelIqG0Az 7YogZH4SjQVH3/3h+7V4fokTDC7em7T1jLiN19M2QE+yFICiQeXa8MHf2NOkG3HmryqC /878RYBOcugk9kzrmyARLyPXAyXk8C8gegxgo5azezrrD7vjYintAIFsD7kOMu4W0QYY R7Xg==
X-Gm-Message-State: AOAM530kJwBmmRdQMKeLqNY5uopAkgjl/vHwlg0nefRvkiWiug6BVhY9 PZq6UoazztzfRpWVLDCfGTPd9wAGrWS1bZzjUvs=
X-Google-Smtp-Source: ABdhPJzkOfrS3Ihr3/MGIRzC09dL3slDEMPL3paF0Rv2X71+aN+9s3dsEM1/sWLRk6Pofurft2k18zuxE14gcBvYREk=
X-Received: by 2002:a05:620a:16cd:: with SMTP id a13mr864877qkn.249.1611524357806; Sun, 24 Jan 2021 13:39:17 -0800 (PST)
MIME-Version: 1.0
References: <CAA=duU2nj0G2H9v3Fft5iBAA8bxTX0zNgZsevMpojZY3TZQ6dg@mail.gmail.com> <CANeU+ZC7jZmHUTK==WghKb6W-eFZ9eHhH7UNHN9kSxNZR9N7gw@mail.gmail.com>
In-Reply-To: <CANeU+ZC7jZmHUTK==WghKb6W-eFZ9eHhH7UNHN9kSxNZR9N7gw@mail.gmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Sun, 24 Jan 2021 16:39:02 -0500
Message-ID: <CAA=duU20AivvTbGQFpAZ09n=wnv-sicJj5Xt0Xamuck_kAJa9A@mail.gmail.com>
To: "StJohns, Michael" <msj@nthpermutation.com>
Cc: RFC Interest <rfc-interest@rfc-editor.org>, XML Developer List <xml2rfc-dev@ietf.org>, xml2rfc@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e4de5905b9ac4032"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/bS6ok6HcU-sKDg7LgQ9kVPTmJjE>
Subject: Re: [xml2rfc] [rfc-i] Script to generate RFC reference including abstract?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jan 2021 21:39:21 -0000

Mike,

Thanks, not quite what I was looking for, but it might be useful as a basis
for scripting.

Cheers,
Andy


On Sun, Jan 24, 2021 at 2:21 PM StJohns, Michael <msj@nthpermutation.com>
wrote:

> Maybe try this?
> http://web-harvest.sourceforge.net/manual.php
>
>
>
> On Sun, Jan 24, 2021 at 12:04 Andrew G. Malis <agmalis@gmail.com> wrote:
>
>> Just to save myself a bit of work if this already exists ....
>>
>> Have any of you written a script when, given a list of RFC numbers, will
>> generate an xml2rfc-ish reference and pull out the abstract for each RFC?
>> Something like, when given "8660", will produce:
>>
>>    [RFC8660]  Bashandy, A., Ed., Filsfils, C., Ed., Previdi, S.,
>>               Decraene, B., Litkowski, S., and R. Shakir, "Segment
>>               Routing with the MPLS Data Plane", RFC 8660,
>>               DOI 10.17487/RFC8660, December 2019,
>>               <https://www.rfc-editor.org/info/rfc8660>.
>>
>>    Segment Routing (SR) leverages the source-routing paradigm.  A node
>>    steers a packet through a controlled set of instructions, called
>>    segments, by prepending the packet with an SR header.  In the MPLS
>>    data plane, the SR header is instantiated through a label stack.
>>    This document specifies the forwarding behavior to allow
>>    instantiating SR over the MPLS data plane (SR-MPLS).
>>
>> Thanks,
>> Andy
>>
>> _______________________________________________
>> rfc-interest mailing list
>> rfc-interest@rfc-editor.org
>> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
>>
>

v2.23.0 | Report a Bug | By Email