
From nobody Wed Dec  1 13:54:51 2021
Return-Path: <rgm@htt-consult.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 4A50C3A0B91 for <xml2rfc@ietfa.amsl.com>; Wed,  1 Dec 2021 13:54:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 wAKAP8fNN9Wt for <xml2rfc@ietfa.amsl.com>; Wed,  1 Dec 2021 13:54:47 -0800 (PST)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 D60A83A0B8D for <xml2rfc@ietf.org>; Wed,  1 Dec 2021 13:54:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 4540A625FC for <xml2rfc@ietf.org>; Wed,  1 Dec 2021 16:53:46 -0500 (EST)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id yJCCNVj2kn1O for <xml2rfc@ietf.org>; Wed,  1 Dec 2021 16:53:41 -0500 (EST)
Received: from [192.168.160.11] (unknown [192.168.160.11]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 973AC62574 for <xml2rfc@ietf.org>; Wed,  1 Dec 2021 16:53:41 -0500 (EST)
Message-ID: <c1c7f288-09cb-8624-b33d-8f635f3b56d0@htt-consult.com>
Date: Wed, 1 Dec 2021 16:54:38 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.3.0
Content-Language: en-US
To: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
From: Robert Moskowitz <rgm@htt-consult.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/94rlXUa_90LKMbgqJCDMq0YTaN4>
Subject: [xml2rfc] <figure> support name field?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <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: Wed, 01 Dec 2021 21:54:49 -0000

Can this:

<figure anchor="HHIT_Format">
<name>HHIT Format</name>

be handled something like:

<figure anchor="HHIT_Format" name="HHIT Format">

Obvious not like that cause I get errors when I try it...

I did read the FAQ and the RFC and am not seeing how to do this, "nicely".

thanks

Bob


From nobody Wed Dec  1 14:16:04 2021
Return-Path: <cabo@tzi.org>
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 DB8503A0BE6 for <xml2rfc@ietfa.amsl.com>; Wed,  1 Dec 2021 14:16:02 -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, SPF_HELO_NONE=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 PaC7XI0_7HB8 for <xml2rfc@ietfa.amsl.com>; Wed,  1 Dec 2021 14:15:58 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC81A3A0BE4 for <xml2rfc@ietf.org>; Wed,  1 Dec 2021 14:15:57 -0800 (PST)
Received: from [192.168.217.118] (p5089a436.dip0.t-ipconnect.de [80.137.164.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4J4D1f2t8wz2xQW; Wed,  1 Dec 2021 23:15:50 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <c1c7f288-09cb-8624-b33d-8f635f3b56d0@htt-consult.com>
Date: Wed, 1 Dec 2021 23:15:50 +0100
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
X-Mao-Original-Outgoing-Id: 660089750.016397-578549dffda8351b41f0803be277e644
Content-Transfer-Encoding: quoted-printable
Message-Id: <5D48213B-5BC0-46A5-BE9B-EC20F5C06799@tzi.org>
References: <c1c7f288-09cb-8624-b33d-8f635f3b56d0@htt-consult.com>
To: Robert Moskowitz <rgm@htt-consult.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/gdhYgxvJr6lvAVW0SonZ1nLKxAk>
Subject: Re: [xml2rfc] <figure> support name field?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <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: Wed, 01 Dec 2021 22:16:03 -0000

On 2021-12-01, at 22:54, Robert Moskowitz <rgm@htt-consult.com> wrote:
>=20
> Can this:
>=20
> <figure anchor=3D"HHIT_Format">
> <name>HHIT Format</name>
>=20
> be handled something like:
>=20
> <figure anchor=3D"HHIT_Format" name=3D"HHIT Format">

That attribute is called =E2=80=9Ctitle=E2=80=9D.

(It really should be called caption, as should be the element above, but =
that=E2=80=99s water under the bridge.)

=
https://xml2rfc.tools.ietf.org/xml2rfc-doc-3.11.1.html#name-title-attribut=
e-5
says:

> 2.29.7. "title" Attribute
>=20
> Deprecated. Use the <name> element instead.

Which raises the question why you don=E2=80=99t like the v3 way of using =
<name.
You can=E2=80=99t have markup in an attribute, so how do you get your =
superscripts into your captions?

> Obvious not like that cause I get errors when I try it...
>=20
> I did read the FAQ and the RFC and am not seeing how to do this, =
"nicely".

https://xml2rfc.tools.ietf.org/xml2rfc-doc-3.11.1.html

is what you want to read here; RFCs are less useful at this point.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Dec  8 11:05:58 2021
Return-Path: <rjsparks@nostrum.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 6523A3A094A; Wed,  8 Dec 2021 11:05:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.079
X-Spam-Level: 
X-Spam-Status: No, score=-2.079 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 51B699XscmR5; Wed,  8 Dec 2021 11:05:44 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 DE2E73A094E; Wed,  8 Dec 2021 11:05:44 -0800 (PST)
Received: from c162ff772b9a ([47.186.34.206]) (authenticated bits=0) by nostrum.com (8.17.1/8.16.1) with ESMTPSA id 1B8J5f90086717 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 8 Dec 2021 13:05:41 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1638990342; bh=PD4c8WVC7b9AvFHII1eex95qZXqJwH6+E2GQjObUXss=; h=From:To:Subject:Cc:Date; b=tA6LceO2spfs62U5H2wqZoj14F8MgUmJIKviwSSh0kecHnZSSe93UsNFASEn8fsq1 tp8I/hNSZXjjGiijiCyWlRhZQty06W8R2e+yO24s02y26TqJRyF6YTQLPqihX6lzdB hsEI4yC3/3AHEASllBBuWfzssZs1XufgVdhNLBU4=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.34.206] claimed to be c162ff772b9a
Received: from rjsparks by c162ff772b9a with local (Exim 4.92) (envelope-from <rjsparks@nostrum.com>) id 1mv2G0-00004L-3q; Wed, 08 Dec 2021 19:05:36 +0000
From: rjsparks@nostrum.com
To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Message-Id: <E1mv2G0-00004L-3q@c162ff772b9a>
Date: Wed, 08 Dec 2021 19:05:36 +0000
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/8_S7vkhNyh-OZ7U0QiE8zqsa0_s>
Subject: [xml2rfc] New xml2rfc release: v3.12.0
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <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: Wed, 08 Dec 2021 19:05:50 -0000

Hi,

This is an automatic notification about a new xml2rfc release, 
v3.12.0, generated when running the mkrelease script.

Release notes:

xml2rfc (3.12.0) ietf; urgency=high
  * Security release - disallow includes from local filesystem by default.
    Adds a --allow-local-file-access flag (and associated library
    configuration option) to allow it.

 -- Robert Sparks <rjsparks@nostrum.com>  8 Dec 2021 18:05:03 +0000

The preferred way to install xml2rfc is by doing 'pip install xml2rfc',
and 'pip install --upgrade xml2rfc' to upgrade.  If there are system-
installed python modules which pip will not upgrade, you may have to
use 'pip install --upgrade --no-deps xml2rfc' and install dependencies
manually.

The new version is also available through SVN checkout, with
  'svn checkout https://svn.ietf.org/svn/tools/xml2rfc/tags/cli/3.12.0'

Documentation for this release is built-in, and also available at:
  https://xml2rfc.tools.ietf.org/xml2rfc-doc-3.12.0.html

Regards,

	Robert Sparks
	(via the mkrelease script)


From nobody Thu Dec  9 11:24:38 2021
Return-Path: <Fred.L.Templin@boeing.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 DDED73A0AAD for <xml2rfc@ietfa.amsl.com>; Thu,  9 Dec 2021 11:24:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-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=boeing.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 8FW0tx6VEKa0 for <xml2rfc@ietfa.amsl.com>; Thu,  9 Dec 2021 11:24:31 -0800 (PST)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (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 99ECA3A0AB1 for <xml2rfc@ietf.org>; Thu,  9 Dec 2021 11:24:30 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 1B9JORhX029323; Thu, 9 Dec 2021 14:24:28 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1639077868; bh=oNt99uB7k7m81BIQ+jTjb+/yanP66P5FcplN4kHKocw=; h=From:To:Subject:Date:From; b=Nlzj5YK7FeRQ0MSO+iCy9V+kVpO/3q1Uafy9vStYsSUT/TZd3KS2EwWbbMhn0ulIy HmUMsdL1iDfCaDleHTlygQFm/1R1kSSUf0OoydGPuloejTAbdlk3yRqOgHEiue4cwh tAvcO5Q+K4R+MmbEo/pl9BZJxgt7ebIhfshtiQfrzOPv/PkN6oxkEtQjS5mgdOqIxG 6BExMsGHsr16IA9roqzNCJxBOzrJslzaOZGsHEIeDOt4tVOk0gFIA4py+wJqxLsoQd KzpMssQNLcfMaxaoYkeg9VU8f2wT7H0ExeCwlyT/i+tMHFkfMPuiX5NyxghHSt/Ns9 Gtlol3AOFx4LQ==
Received: from XCH16-07-09.nos.boeing.com (xch16-07-09.nos.boeing.com [144.115.66.111]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 1B9JOGZc029103 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <xml2rfc@ietf.org>; Thu, 9 Dec 2021 14:24:16 -0500
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-09.nos.boeing.com (144.115.66.111) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2308.14; Thu, 9 Dec 2021 11:24:15 -0800
Received: from XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5]) by XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.2308.014; Thu, 9 Dec 2021 11:24:15 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
Thread-Topic: Referencing IEN's in xml2rfc?
Thread-Index: AdftMlhlfVU+17RkTkmgL5Kj6A9oEw==
Date: Thu, 9 Dec 2021 19:24:14 +0000
Message-ID: <48bc50ec76484872a7953093b1db81c0@boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: DEA31A467FB17AA5199D375800A3E5254BBA6187868D9456813AF7D6E783666F2000:8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/XGP8CYhn_FnPS_up5qBFILpNutE>
Subject: [xml2rfc] Referencing IEN's in xml2rfc?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <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: Thu, 09 Dec 2021 19:24:36 -0000

Is it possible to include IEN's in Normative/Informative references? Here i=
s
what I tried, but xml2rfc didn't like it:

    <references title=3D"Informative References">
      <?rfc include=3D"reference.IEN.0048"?>
    </references>

Thanks - Fred


From nobody Fri Dec 10 00:23:26 2021
Return-Path: <julian.reschke@gmx.de>
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 416B23A0A98 for <xml2rfc@ietfa.amsl.com>; Fri, 10 Dec 2021 00:23:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.752
X-Spam-Level: 
X-Spam-Status: No, score=-3.752 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-1.852, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 jWP6i1QL5ryQ for <xml2rfc@ietfa.amsl.com>; Fri, 10 Dec 2021 00:23:19 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 E96453A0A9D for <xml2rfc@ietf.org>; Fri, 10 Dec 2021 00:23:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1639124594; bh=DI6wOqz0Qh5PaYEPxE4pSSwh/rvptn7noi+cjpb21TE=; h=X-UI-Sender-Class:Date:Subject:To:References:From:In-Reply-To; b=hXWrhBgwrSCBn7TcjCeP1+uMAU42l4YunuYI69F4yQvjRBkC6p80BPQuZmndrYqx7 wECyqq4bjaVlQaeHWDGvlpxC6GjepWlnGsvckD4CNyW0qq4wg4oHPhlWjC3UZVXDKP wBGFL6avu+vks08o6Ujkff/nbxWaxtWhlf2H3zso=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.179] ([84.171.153.143]) by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MNsw4-1nB4hO111U-00OChf for <xml2rfc@ietf.org>; Fri, 10 Dec 2021 09:23:14 +0100
Message-ID: <a83bd685-40a4-da88-3e72-92971f453d79@gmx.de>
Date: Fri, 10 Dec 2021 09:23:11 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.3.2
To: xml2rfc@ietf.org
References: <48bc50ec76484872a7953093b1db81c0@boeing.com>
From: Julian Reschke <julian.reschke@gmx.de>
In-Reply-To: <48bc50ec76484872a7953093b1db81c0@boeing.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:pHVfB3qHvYy+lb8XuWpmEklf4Qsk3CQDd+O2N4Ta1ZmZdlATY2g F9q8ZmKHGG+MyMHN9f8hXYzfSKouPBGMlLqqrOrYmltTerIsBLi39TGIOrYa1MAkpjaQ/k/ W6Cc7rMda4E2HifMNK6aFgBMtIi+sNlqvBTkX3lS8biWxKXE6R0Ts1E7+4k6i53k/5eCzCS OEJEtCz3wkjFvR3tZ5M4w==
X-UI-Out-Filterresults: notjunk:1;V03:K0:W9dELCSa0m0=:eus+wVfVZZnm1sqhnGv0Q4 r5Lj5L5D3z3eiyDOkShUlGKDIjQdyp9L1bgUxH4TP/GxUcyYF/Z4YrszYQ0+afF7zoR5MLBhH CHNTIee4AoVE+eMFyqPYuG5apcTw2aRwGDlMVMGiTx135v3RGzQHI/VySMiMApTyz+BYNYBPr jdxpn8EPd2a232fd0A7zeogIl7hfWOzv6wO0PaSazSiuz6YBF45VF6mK8z2bMdNj143bFxp9Z gNVGvphdELt8mjNfd458tBCxCBuD8tKooYeUuoajoAVEDtVfSoiO9/iToIV6lPBOnrISsSbv9 NF9OhNZ7NwHEidVjJniGAEiyexsTij3iYChk/6/fe2rF6VtXKvW7P6QzpW8JvGRUX60NSl3r9 skt8+xUbyvwBKOu6VjdzsEGe6u01DmRZ90Sejb3lC+2t1JcuIecFoMerjnh+7vlh7iErHIzQ/ xFYkbrBV383ovM1AbhF5IyC1sngEP6+TW5FEgfvo5W0ehmBeg9LCjiAycr0CJMyjOxNQ3QPQb o3YE2/1UrI9KaaHbi3kwjynUeTTHH7rdhJajiVzOv/x5rzgWKYbDZu6qoHuZkeDALu//4Bl7C 9AeHvizl6dngDZc6CQBJ/9pPPFcHcDWll6T32WHk8DoB0zvreP0FeqdxGllpwjXYDKeccjEU+ o3UEi37svcOE7cy6AIJ5YvBU4U8N+pgNtVpnEpi3jxON4Nl0C+0T2B4gD/UOGEuxcMAXeNDsg WSXC0myTCsk+te3p/knfhMhhCg5dmvYFpu/rKENOnlHZwrKTRaWPlIXA1OUx196yIaXjrzwOq rjsMomXoy8/yryTlOupdBjYoueVNxaG794usd0otQwz2XvXZNQTh99qtXVnENY6YJqvWCC2wx PPYqEj7NS/t5ZvrNE0WmnaJ8E8EhSUnu30UO3ah+z4f6jKS49V4+WjUce7FaV5GHL9J+E3Ojx U+FduDmu4pxDkUyJ/qq/ixWENdDkcb/7nanAbBBtoro3LFFW5QQ7Alg7gPQu7nGAJ3miJ9j5f OIniwqOVn+7vIVHRQ4nsO/UfBmwrlZBRh87tShkSpZnHesI+X6uffFLCD6IztDqDvRqzs1HrT j7VDW8DmAVFD/I=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/cfsrd3K2guU0Kn8mz1f0_LGva-s>
Subject: Re: [xml2rfc] Referencing IEN's in xml2rfc?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <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: Fri, 10 Dec 2021 08:23:24 -0000

Am 09.12.2021 um 20:24 schrieb Templin (US), Fred L:
> Is it possible to include IEN's in Normative/Informative references? Her=
e is
> what I tried, but xml2rfc didn't like it:
>
>      <references title=3D"Informative References">
>        <?rfc include=3D"reference.IEN.0048"?>
>      </references>
>
> Thanks - Fred

Is it possible? Definitively. References and the include mechanism
(superseded in V3 by x:include) are generic. What you need to find is an
online resource to include from.

Best regards, Julian


From nobody Fri Dec 10 00:55:05 2021
Return-Path: <cabo@tzi.org>
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 3A0C23A0C8A for <xml2rfc@ietfa.amsl.com>; Fri, 10 Dec 2021 00:55:03 -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, SPF_HELO_NONE=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 XC2raodNAL7F for <xml2rfc@ietfa.amsl.com>; Fri, 10 Dec 2021 00:54:59 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DADC13A0C5D for <xml2rfc@ietf.org>; Fri, 10 Dec 2021 00:54:58 -0800 (PST)
Received: from [192.168.217.118] (p5089a436.dip0.t-ipconnect.de [80.137.164.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4J9PqL0nd5zDCgl; Fri, 10 Dec 2021 09:54:54 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <48bc50ec76484872a7953093b1db81c0@boeing.com>
Date: Fri, 10 Dec 2021 09:54:53 +0100
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
X-Mao-Original-Outgoing-Id: 660819293.722351-95db1f958570a54f087a32b1f28a77d5
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A2DD079-EA07-4AF4-B2FC-015BB1D24A44@tzi.org>
References: <48bc50ec76484872a7953093b1db81c0@boeing.com>
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/6LKsvTzJmXdZ-8blfgSKAbsgPHc>
Subject: Re: [xml2rfc] Referencing IEN's in xml2rfc?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <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: Fri, 10 Dec 2021 08:55:03 -0000

On 2021-12-09, at 20:24, Templin (US), Fred L =
<Fred.L.Templin@boeing.com> wrote:
>=20
> Is it possible to include IEN's in Normative/Informative references?

I don=E2=80=99t know about normative (I don=E2=80=99t think any IEN is =
on the downref list), but informative can of course be done:

informative:
  IEN48:
    author:
      - name: Vint  Cerf
        org: DARPA/IPTO
    date: July 1978
    title: >
      The Catenet Model for Internetworking
    seriesinfo:
      Internet Experiment Note: 48

kramdown-rfc generates this bibxml snippet in its informative references =
section:

<reference anchor=3D"IEN48" >
  <front>
    <title>The Catenet Model for Internetworking</title>
    <author initials=3D"V." surname=3D"Cerf" fullname=3D"Vint  Cerf">
      <organization>DARPA/IPTO</organization>
    </author>
    <date year=3D"1978" month=3D"July"/>
  </front>
  <seriesInfo name=3D"Internet Experiment Note" value=3D"48"/>
</reference>

=E2=80=A6and xml2rfc (which ignores the organization info) formats that =
into:

   [IEN48]    Cerf, V., "The Catenet Model for Internetworking",
              Internet Experiment Note 48, July 1978.

> Here is
> what I tried, but xml2rfc didn't like it:
>=20
>    <references title=3D"Informative References">
>      <?rfc include=3D"reference.IEN.0048"?>
>    </references>

You don=E2=80=99t need to reference a reference to include that =
reference in an RFCXML document.  (I=E2=80=99m not aware of a repository =
of such bibxml snippets for IENs, so you=E2=80=99ll need to roll your =
own as shown above.)

Gr=C3=BC=C3=9Fe, Carsten

