Re: [xml2rfc] Error: Did not expect element figure
Robert Moskowitz <rgm@htt-consult.com> Fri, 30 June 2023 22:35 UTC
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 E44BEC14CEFC for <xml2rfc@ietfa.amsl.com>; Fri, 30 Jun 2023 15:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G0TfdJrln7_u for <xml2rfc@ietfa.amsl.com>; Fri, 30 Jun 2023 15:35:17 -0700 (PDT)
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 79E1BC1575C6 for <xml2rfc@ietf.org>; Fri, 30 Jun 2023 15:31:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 3BBCF6275A for <xml2rfc@ietf.org>; Fri, 30 Jun 2023 18:31:15 -0400 (EDT)
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 dzaPjbMEKcTw for <xml2rfc@ietf.org>; Fri, 30 Jun 2023 18:31:10 -0400 (EDT)
Received: from [192.168.160.29] (unknown [192.168.160.29]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id F37926247F for <xml2rfc@ietf.org>; Fri, 30 Jun 2023 18:31:09 -0400 (EDT)
Message-ID: <4826b6e0-3a3c-b3e9-e504-947d2c1380c5@htt-consult.com>
Date: Fri, 30 Jun 2023 18:31:28 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0
From: Robert Moskowitz <rgm@htt-consult.com>
To: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
References: <1481bb7d-38fd-4b66-5eb0-be9e06f59bd1@htt-consult.com> <B3558A46-9DBD-4B1A-976D-4573BC62DA1C@tzi.org>
Content-Language: en-US
In-Reply-To: <B3558A46-9DBD-4B1A-976D-4573BC62DA1C@tzi.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/uM6pR9GiGrJMl3Jhw1BoaLp3f90>
Subject: Re: [xml2rfc] Error: Did not expect element figure
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.39
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, 30 Jun 2023 22:35:21 -0000
draft-moskowitz-eddsa-pki-05.xml(944): Error: Did not expect element figure there, at /rfc/middle/section[10]/section[3]/t[2]/figure <t> Thus the only way to provide a SAN is through the config file. And there are two approaches. This document uses an environment variable to provide the SAN value into the config file. Another approach is to use piping as in: <figure anchor="fig_15"> <artwork name="" type="" alt=""> <![CDATA[ openssl req -new -key domain.key\ -subj "/C=US/ST=CA/O=Acme, Inc./CN=foo.com" -reqexts SAN\ -config <(cat /etc/ssl/openssl.cnf\ <(printf "[SAN]\nsubjectAltName=DNS:foo.com,DNS:www.foo.com"))\ -out domain.csr ]]> </artwork> </figure> </t> On 6/30/23 17:56, Carsten Bormann wrote: > Hi Bob, > > the error message talks about a figure element. > You stripped this way down to the CDATA, so we can’t see what’s wrong. > Can you widen the view? > > Grüße, Carsten > > >> On 2023-06-30, at 23:33, Robert Moskowitz <rgm@htt-consult.com> wrote: >> >> I pulled this in from a very old draft, and can't see what the >> problem is: >> >> <![CDATA[ >> openssl req -new -key domain.key\ >> -subj "/C=US/ST=CA/O=Acme, Inc./CN=foo.com" -reqexts SAN\ >> -config <(cat /etc/ssl/openssl.cnf\ >> <(printf "[SAN]\nsubjectAltName=DNS:foo.com,DNS:www.foo.com"))\ >> -out domain.csr >> >> ]]> >> >> >> Please help find the unexpected element. >> >> thanks >> >> _______________________________________________ >> xml2rfc mailing list >> xml2rfc@ietf.org >> https://www.ietf.org/mailman/listinfo/xml2rfc
- [xml2rfc] Error: Did not expect element figure Robert Moskowitz
- Re: [xml2rfc] Error: Did not expect element figure Robert Moskowitz
- Re: [xml2rfc] Error: Did not expect element figure Kesara Rathnayake
- Re: [xml2rfc] Error: Did not expect element figure Carsten Bormann
- Re: [xml2rfc] Error: Did not expect element figure Julian Reschke
- Re: [xml2rfc] Error: Did not expect element figure Robert Moskowitz
- Re: [xml2rfc] Error: Did not expect element figure Carsten Bormann