
From nobody Thu Jan  2 11:58:47 2020
Return-Path: <brian.e.carpenter@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 3D472120026 for <xml2rfc@ietfa.amsl.com>; Thu,  2 Jan 2020 11:58:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 U8SfLLZspR5G for <xml2rfc@ietfa.amsl.com>; Thu,  2 Jan 2020 11:58:43 -0800 (PST)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (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 DE48B1207FD for <xml2rfc@ietf.org>; Thu,  2 Jan 2020 11:58:43 -0800 (PST)
Received: by mail-pg1-x532.google.com with SMTP id q127so22393984pga.4 for <xml2rfc@ietf.org>; Thu, 02 Jan 2020 11:58:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=to:from:subject:organization:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=tqzEne4hNrPAuyHSMWomb6Lx1hAWGJnu/wsgYl7B+GE=; b=LEZSRKsXLdll7HzarbedS7otaLG6IzF7YtR5njD8SvSWTbF0y3qbk5hCzBp5IZUUTo LYcAE9YEk1xnd15mUssTJ/Y59/wCesbnTMZtFsP8hnWxNruXKevBk4SolScTYs/2eIuj FRv/byRERSFen/FFeq0RzFyRcwNXwMd8ZDPoQwQmHcCce+SZ+awViOWnvZLnqKen5VI5 UwLE5H9AakWxm+ChLYGa0EwMBvh6wPM9bil8OLRKOOpuU1XIryER7bqyZlKJY2BUp0X5 exRZRqy/hcyz1raDyJ+haym4UBQHEC9P9Sxrng65C4SNe6rwlvEnJvqZezvkTpuHi5qU ngRQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:organization:message-id:date :user-agent:mime-version:content-language:content-transfer-encoding; bh=tqzEne4hNrPAuyHSMWomb6Lx1hAWGJnu/wsgYl7B+GE=; b=paQ54+p9oEC0luxljUV6Gqn5H4KJYkmFB1TidzJl6narOMVmXmjYlplbVRykaEcuy3 QKpEtieB6SgNmEws4/88hYVdn7cR7/YZU42z8ddFkesssss1ZcuLNjiJ7YDD7S6iTUcv cf4B5Z7uEM1Gg11xscvDMRgyyXWFo3fh2KT+FO5D/FgEzh8kacdR6mfYKaWGq79I1kw/ ivhHFguWdrg131Al5re3j/aOV0y/ZT5hV09MTSlaC1a8ar5CKN6WVEl1uhjBuLtt4IeF elVTt94THPmSPfVpj/NEMdQCVi/vDUMwCv3Z+WNe9VUegiRp4G9F5s2nUWOj+onXQi58 4hjg==
X-Gm-Message-State: APjAAAWLT76U29xxeKVoeJm6pu/lhXRj1MkqE/j2ZpLe1wAuUAaDwpNR fiJ6p+oclAIHEQmm9W6hFDJvI2/1
X-Google-Smtp-Source: APXvYqxp8Mn5AzdwUA4VSmFuHiTO5Xcd9tA9boqRR5kbApOmCz/tzywBTKbQdxZeS7WkvOTCyTHkxg==
X-Received: by 2002:a63:6c86:: with SMTP id h128mr75175540pgc.200.1577995123088;  Thu, 02 Jan 2020 11:58:43 -0800 (PST)
Received: from [192.168.178.30] (228.147.69.111.dynamic.snap.net.nz. [111.69.147.228]) by smtp.gmail.com with ESMTPSA id z64sm64432516pfz.23.2020.01.02.11.58.41 for <xml2rfc@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Jan 2020 11:58:42 -0800 (PST)
To: xml2rfc@ietf.org
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <918df451-55de-9bd2-688b-37d2d83762b5@gmail.com>
Date: Fri, 3 Jan 2020 08:58:40 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/H1GqOqg6ZMFg2uOnrI8gk6Enod0>
Subject: [xml2rfc] <country> in v3
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: Thu, 02 Jan 2020 19:58:45 -0000

For some reason, it appears that <country>P.R. China</country> causes problems in v3, but <country>China</country> is OK.

The problem I see is that <country> is simply ignored, and <code> is also ignored,
when the "P.R" was included. 

I think there is a similar issue with commas included in <street>.

For both, RFC7991 says "Content model: only text content." I don't see that this
should exclude punctuation marks.

Regards
   Brian Carpenter


From nobody Thu Jan  2 23:36:49 2020
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 8841B120072 for <xml2rfc@ietfa.amsl.com>; Thu,  2 Jan 2020 23:36:47 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=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 oApmZQidBUDW for <xml2rfc@ietfa.amsl.com>; Thu,  2 Jan 2020 23:36:45 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (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 2286A120019 for <xml2rfc@ietf.org>; Thu,  2 Jan 2020 23:36:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1578037001; bh=jeD/yNWOI3/fAB6rdzzxsy7Bsgs2aMIAzGIwjfZC+Lk=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=eU1OYmouSyO/Zm8JxH/ZYG4gUkyfUuT6ODsbCY0wVnwHj74inJCPGvAJEIU5hnkrC lhOH+zpTY4k51vi4ssleQl4b6WQpYD4+F0TthOMpi8Jg/ecke2AnsC/WcpkhP7Sd2x NGlBSdH5PVt76FeJxwsJSIQpjAZxN/SM0SHXthVU=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([84.171.158.129]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MsYqv-1jbNzP443X-00u1Ji; Fri, 03 Jan 2020 08:36:41 +0100
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, xml2rfc@ietf.org
References: <918df451-55de-9bd2-688b-37d2d83762b5@gmail.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <d8763b85-2a6c-e927-b50b-1d6fa9a8f361@gmx.de>
Date: Fri, 3 Jan 2020 08:36:40 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1
MIME-Version: 1.0
In-Reply-To: <918df451-55de-9bd2-688b-37d2d83762b5@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:40lAPZNQR3ZIsC3WZmNKv4nteDE+9a4FhuVlOWbq+v23o7Q9Q0r u2SfET0zzX4kMlvdQr0tU5st5FmcHL761tCI3pIQZfAw8xRUoe5pMTYf2pSjx5/Qco3tz+e oCe3TSOsn7CVJpKy6O8fyvhF0yAoxfv0cBWb0x4ipQQyZcTp8G0zWkdK9XstoB2fGR0y5yi 0V341CuWM/sJ2rNnZIA+g==
X-UI-Out-Filterresults: notjunk:1;V03:K0:QgZKRFPwjRE=:NGVE2ApTzTuBc3LTUi44KX Le9sZuMsUvJrNgaB6hbe+t+bgK7QJLuVUeOFUp/7lausSpCsKie5+alQj+WFRKXHUXS7mNT1/ fMePcEuFJswd40/WQVFrjMZyGDpwLBLsHdyU9WG8h+b+QeezTJQV+K16vokzyLc5Z5+H9w72U YtRr8eG4rpi358iLMdGZQ9cT5jJOtR/jyyABK7rEooX07jaPaFUhBIhboaDSUiIOR4pUtnfMP rfKEPVWDDlG/Md0Fyf1GwUazBBFHYKGzdnSDfM6jUtuwQ4BUe6hd3aII6FaL3AxKwucTT1wLS 1vEjWz4JiUfj0mq4RVLDYuG+5SJZlyOLSoNUQl3tI0xP8d9Jut+8UhUxrMQj54Xo+F7MIBs9D Q8G0Xe8ep6iX4cwQVwZVKA/oTZi2UJVUWLyfwj2V/jbWKIqP0khfG6yP4YiTHe4OdB6zy2jXA uVZT75aqU6q/lwlUzv5IUzkOfHLSbMVynHs1ZuVxjjv34busPQ0o1YAfoYDH2l9K/n+FCwnlU nERCyFiljsrf1+K6P7e1m0K1CBtxXXKq/xbwoFHQjkYpYfpqiyomgAuUUYDe8lzlle20LpSql W6TFa8viLKwpokIxlJ7OtLT5Y9HAKcc9NTpHN7wvQtPw6pFq0yMQQhm6pzSNhyOXBXv+mynFW /1Q0+GTufe0itq8/7Tfcv7vnwrq3KQHa8I1Jk26lySFB45o5+cp3SCMd3DHAcFAYHDKsb9nUS UX4n9cAKJCYdMqIS++hv1wYND60Y5SjbRjR1AVanX/1z2BxwZzRIIHA6dLNdJ94J8rEtqAnSS lde8H5r+7lIrNrT1JjDi9HYSw1oUBCwj6AlhxCKVak34Yy7xPH6vdakjMYGzENlVdGdOBVq7E 6NaNPxZksc2vr/ugBRbQFq6va9jaCJkpSM4511/1ByPH4eFWDVnqVBYbh/TA1ZyEv88XZsitA VwXOQRpyO300WRo+RjBQoOWlyThRTN2WBCvODRWEWa8qmgl1S54IGyi6RzHMDnUcn+7NpLsa4 aMnJOsToTBkrKYdwILLovbEVFxUPsMvys0N1H9/O6FR8KuyKNi4bENwtwmBC934yqQMF8rKCb mwe2OkV6DJ8RnUCaIk5JBkOoB0Mnicb0zgQciXHMUoHPArEY9tEB0rwQ1DIc7lSkhNFmOceKM 5il6f0zVBBSIx/0M7yQoTTfuPovMkeXYsPaDsxcj6zeL0cix/hlDlDZAqu31cWxFh7EeUlyoF UJXgdtysd2NzxNMxhnzYTpIg4hxCxICsP/q4Meg/vV0IqfNZOiXwj0/55vzc=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/jggwDI55auShfNSwyrxI8ooFnrk>
Subject: Re: [xml2rfc] <country> in v3
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: Fri, 03 Jan 2020 07:36:47 -0000

On 02.01.2020 20:58, Brian E Carpenter wrote:
> For some reason, it appears that <country>P.R. China</country> causes pr=
oblems in v3, but <country>China</country> is OK.
>
> The problem I see is that <country> is simply ignored, and <code> is als=
o ignored,
> when the "P.R" was included.
>
> I think there is a similar issue with commas included in <street>.
>
> For both, RFC7991 says "Content model: only text content." I don't see t=
hat this
> should exclude punctuation marks.
>
> Regards
>     Brian Carpenter

xml2rfc wants an "ISO short name" here (see
<https://www.iso.org/obp/ui#search> for a lookup UI).

Another issue here is that it has unintended consequences with respect
to Taiwanese users, as they would have to use "Taiwan (Province of China)"=
.

IMHO the changes with respect to postal formatting (see
<https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-not=
es-10#section-3.1.13>)
are overly complex and should be backed out. And yes, I'm saying this
after having it reverse engineered and partly implemented in my XSLT code.

Best regards, Julian


From nobody Fri Jan  3 11:43:16 2020
Return-Path: <brian.e.carpenter@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 2DD2712002F for <xml2rfc@ietfa.amsl.com>; Fri,  3 Jan 2020 11:43:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 WYuWHAQ4oIXV for <xml2rfc@ietfa.amsl.com>; Fri,  3 Jan 2020 11:43:11 -0800 (PST)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (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 7DE7A120013 for <xml2rfc@ietf.org>; Fri,  3 Jan 2020 11:43:11 -0800 (PST)
Received: by mail-pg1-x532.google.com with SMTP id z124so23823298pgb.13 for <xml2rfc@ietf.org>; Fri, 03 Jan 2020 11:43:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=S236SBeeNWy+6Mgn1p1us0MRohoFa4BS9FXtMzwbRAQ=; b=r8FnPZFWZYgUMvfrxc85qGa1bbYHKflStZ5hM+vPW7cFpRJYeRk0C7scsB6V98IdNB QMPZIiA/BNbXpPOjpWiS1xzpVr5liX64SR8mrBQceMOi2JuD32RCp3ubVssp4vC5MHeL V7mwynKSw5C9GK7yDJG76rY7sHUcqI6ASaemem9MM+f6SQ9aKiU8F8Tytb72XEADRIr2 A13tacBTaL5t2FTwR4k2GNmaAF/ALwvdcXJS8rMKB+0Ot4vLAqmstIgKkT2cYAUgGA0T 4oOB+xO/42QnLWDPFvUoBwwU6Q0oBEn89k8LLOrZk5Li4F8mrMdzy0GSMpO9JXCMGyHD JIvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=S236SBeeNWy+6Mgn1p1us0MRohoFa4BS9FXtMzwbRAQ=; b=PH2mJ88WMAmAWfget+aZ/ijPow33CUZfsjBByyrjrdc9tIzjUQk9vNPTM4fWlCq9JG EPHWPPtdWvkltdib95nW3D5ecIDnAM9+HvTjTq5S9ioH4JWvGJksNqWrQS8bWRrmU6JK t+qxf64vet2uGOqtHtB6lBk+rgC0Si/0KCvfDe2yuyakI7jEtuys5tpMrsmH6szpjnLw WKDJNMSuEBkfLlzBo3g+kCfAKr8Hcr1r5P8sLusQfpQ7pv0QvinbxzltglXdTs7wnHf5 oh6MvWnDbDLisKDcYvaCjJRS7oZhuw872ZTCJ4GnzhtVnoF1cVaiHpNtSYi2MTbicEX1 aENQ==
X-Gm-Message-State: APjAAAXn1x2ohlJpg3B3qRYF8yV4sVWVaetzZJz64LgvqTXpELlQPSu2 5fJAH8au2cF28YFvkz/n56/H91P6
X-Google-Smtp-Source: APXvYqwVj9/kNyH8KwECt5EkD/JJ0Ovd5GM4QLHdqGgJpOCZ0IztKjsdiDLIs5KPBhwl9gIJBnheoQ==
X-Received: by 2002:a63:1007:: with SMTP id f7mr32669129pgl.397.1578080590669;  Fri, 03 Jan 2020 11:43:10 -0800 (PST)
Received: from [192.168.178.30] (228.147.69.111.dynamic.snap.net.nz. [111.69.147.228]) by smtp.gmail.com with ESMTPSA id 199sm71729834pfv.81.2020.01.03.11.43.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 Jan 2020 11:43:10 -0800 (PST)
To: Julian Reschke <julian.reschke@gmx.de>, xml2rfc@ietf.org
References: <918df451-55de-9bd2-688b-37d2d83762b5@gmail.com> <d8763b85-2a6c-e927-b50b-1d6fa9a8f361@gmx.de>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <1b6c8b07-df98-6b8e-9144-c203d23f632c@gmail.com>
Date: Sat, 4 Jan 2020 08:43:06 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <d8763b85-2a6c-e927-b50b-1d6fa9a8f361@gmx.de>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/XOGCOCr_zKLsOWqGy28GNgjvVgQ>
Subject: Re: [xml2rfc] <country> in v3
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: Fri, 03 Jan 2020 19:43:15 -0000

On 03-Jan-20 20:36, Julian Reschke wrote:
> On 02.01.2020 20:58, Brian E Carpenter wrote:
>> For some reason, it appears that <country>P.R. China</country> causes problems in v3, but <country>China</country> is OK.
>>
>> The problem I see is that <country> is simply ignored, and <code> is also ignored,
>> when the "P.R" was included.
>>
>> I think there is a similar issue with commas included in <street>.
>>
>> For both, RFC7991 says "Content model: only text content." I don't see that this
>> should exclude punctuation marks.
>>
>> Regards
>>     Brian Carpenter
> 
> xml2rfc wants an "ISO short name" here (see
> <https://www.iso.org/obp/ui#search> for a lookup UI).

I really hope it doesn't "want" an ISO code, since RFC7991 says nothing about
that. It's very convenient that they are available, though.

It takes some cheating to produce:

Dilbert Engineer
Pointy Haired Products LLC
42 Deepinit Street
Mudgrad 7991
Elbonia
Email: dilbert@example.com

> Another issue here is that it has unintended consequences with respect
> to Taiwanese users, as they would have to use "Taiwan (Province of China)".

That's a serious problem. But they can simply omit <country>.

> IMHO the changes with respect to postal formatting (see
> <https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-notes-10#section-3.1.13>)
> are overly complex and should be backed out. And yes, I'm saying this
> after having it reverse engineered and partly implemented in my XSLT code.

Fortunately <street> isn't picky, so one can do anything:

    <author fullname="Dilbert Engineer" initials="D." surname="Engineer">
      <organization abbrev="Pointy LLC"/>
      <address>
        <postal>
          <street>Pointy Haired Products LLC</street>
          <street>42 Deepinit Street</street>
          <street>Mudgrad 7991</street>
          <street>Elbonia</street>
          <country/>
        </postal>
        <email>dilbert@example.com</email>
      </address>
    </author>

Regards
   Brian
 


From nobody Fri Jan  3 12:24:32 2020
Return-Path: <henrik@levkowetz.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 DBEA91200C7 for <xml2rfc@ietfa.amsl.com>; Fri,  3 Jan 2020 12:24:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 moJVi9HH118e for <xml2rfc@ietfa.amsl.com>; Fri,  3 Jan 2020 12:24:28 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54CF6120045 for <xml2rfc@ietf.org>; Fri,  3 Jan 2020 12:24:28 -0800 (PST)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:56911 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1inTUg-0006iR-In; Fri, 03 Jan 2020 12:24:27 -0800
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, xml2rfc@ietf.org
References: <918df451-55de-9bd2-688b-37d2d83762b5@gmail.com> <d8763b85-2a6c-e927-b50b-1d6fa9a8f361@gmx.de> <1b6c8b07-df98-6b8e-9144-c203d23f632c@gmail.com>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <f7615a5e-a4bb-bc0d-6cb4-5f1297c24c23@levkowetz.com>
Date: Fri, 3 Jan 2020 21:24:11 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <1b6c8b07-df98-6b8e-9144-c203d23f632c@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="B4eRP5xd0I8B2qL5TRFXOBeg4PIKC5IPn"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: xml2rfc@ietf.org, brian.e.carpenter@gmail.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/dydlc51ootcNKIqbUjwApgIzGv0>
Subject: Re: [xml2rfc] <country> in v3
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: Fri, 03 Jan 2020 20:24:30 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--B4eRP5xd0I8B2qL5TRFXOBeg4PIKC5IPn
Content-Type: multipart/mixed; boundary="lhtiKBaX15FIwJhlLrNhjJ9a6op7uwSNO";
 protected-headers="v1"
From: Henrik Levkowetz <henrik@levkowetz.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, xml2rfc@ietf.org
Message-ID: <f7615a5e-a4bb-bc0d-6cb4-5f1297c24c23@levkowetz.com>
Subject: Re: [xml2rfc] <country> in v3
References: <918df451-55de-9bd2-688b-37d2d83762b5@gmail.com>
 <d8763b85-2a6c-e927-b50b-1d6fa9a8f361@gmx.de>
 <1b6c8b07-df98-6b8e-9144-c203d23f632c@gmail.com>
In-Reply-To: <1b6c8b07-df98-6b8e-9144-c203d23f632c@gmail.com>

--lhtiKBaX15FIwJhlLrNhjJ9a6op7uwSNO
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Brian,

On 2020-01-03 20:43, Brian E Carpenter wrote:
> On 03-Jan-20 20:36, Julian Reschke wrote:
>> On 02.01.2020 20:58, Brian E Carpenter wrote:
>>> For some reason, it appears that <country>P.R. China</country> causes=
 problems in v3, but <country>China</country> is OK.
>>>
>>> The problem I see is that <country> is simply ignored, and <code> is =
also ignored,
>>> when the "P.R" was included.
>>>
>>> I think there is a similar issue with commas included in <street>.
>>>
>>> For both, RFC7991 says "Content model: only text content." I don't se=
e that this
>>> should exclude punctuation marks.
>>>
>>> Regards
>>>     Brian Carpenter
>>=20
>> xml2rfc wants an "ISO short name" here (see
>> <https://www.iso.org/obp/ui#search> for a lookup UI).
>=20
> I really hope it doesn't "want" an ISO code, since RFC7991 says nothing=
 about
> that. It's very convenient that they are available, though.

xml2rfc recognizes the ISO 3166 2-letter, 3-letter, official, and common =
names
of countries.  In cases where a name or abbreviation in common use isn't
recognized, I'm happy to add extra entries.  I've already done so for 'UK=
',
and will do so for "P.R. China" in the next release.

>=20
> It takes some cheating to produce:
>=20
> Dilbert Engineer
> Pointy Haired Products LLC
> 42 Deepinit Street
> Mudgrad 7991
> Elbonia
> Email: dilbert@example.com
>=20
>> Another issue here is that it has unintended consequences with respect=

>> to Taiwanese users, as they would have to use "Taiwan (Province of Chi=
na)".
>=20
> That's a serious problem. But they can simply omit <country>.

I'll see what I can do to address this, too, in the next release.

Best regards,

	Henrik

>> IMHO the changes with respect to postal formatting (see
>> <https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation=
-notes-10#section-3.1.13>)
>> are overly complex and should be backed out. And yes, I'm saying this
>> after having it reverse engineered and partly implemented in my XSLT c=
ode.
>=20
> Fortunately <street> isn't picky, so one can do anything:
>=20
>     <author fullname=3D"Dilbert Engineer" initials=3D"D." surname=3D"En=
gineer">
>       <organization abbrev=3D"Pointy LLC"/>
>       <address>
>         <postal>
>           <street>Pointy Haired Products LLC</street>
>           <street>42 Deepinit Street</street>
>           <street>Mudgrad 7991</street>
>           <street>Elbonia</street>
>           <country/>
>         </postal>
>         <email>dilbert@example.com</email>
>       </address>
>     </author>
>=20
> Regards
>    Brian
> =20
>=20
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc
>=20


--lhtiKBaX15FIwJhlLrNhjJ9a6op7uwSNO--

--B4eRP5xd0I8B2qL5TRFXOBeg4PIKC5IPn
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl4PousACgkQTptXS4+7
FxphmA//barXNGh5rpRf4MzeBbeVHp9e2pXoIwIzI4x6MnyHBT5S1f26+EH6u8iO
wlAJKYb7xpOS0a9LtF9OWkbNycI0WTUHCq+XW1ddop0rBEWRPerOj1JyHeVEFTXr
XYJL0XmRrgq/tNDNEkgds5nf5wBgaljy3UV831jF0CwTvwXk+NMeHzQ8QdsBveUV
7aZBKse/eqXiM0KMtGeGMDkzRF1KFMSF5rLWElXW8jWmi4vxVqiUQalV6xfJ9o+m
49aExg0j4Mj0hkqd5tYsUNig2EOyZ4I3dM/6qDQ28ugv/ggQlfy1hpoGxtCX6LFA
/t+FY7S1BE0oowWLajPJyd+EatusXSQbCI/AfSUihKPXTOfHYzlPX5hHgBBVnCNh
9AkW2wLBor00N+fKAPP9B/kUi8EMGjdchGLVdZ89eL6vkw0mvGgdGfzrnEO7cMpM
hOy8ZTTqiWiXIosIrWPzCisroXnDahIxbKfwcS5/cTWgXorqZB4VSaREjPxNcNlq
nSGkHaLvbk/kTcl9RB5WMZl7GHSv4zmCflXk7zgs7TtZ4eU+w4bOP185J+EoO2CP
YaYyAkzECnaTmD1sqRlfXiNiIHGt7BhhL679R8aLRndIpoFQAxFV49uKTCc1VBlv
lNasj+5EbSinV7Ogbje2Xh05+DYdiU7gsxkJaC1rmmYKC5Xp8tE=
=4HmZ
-----END PGP SIGNATURE-----

--B4eRP5xd0I8B2qL5TRFXOBeg4PIKC5IPn--


From nobody Fri Jan  3 12:36:26 2020
Return-Path: <henrik@levkowetz.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 6E84C120099 for <xml2rfc@ietfa.amsl.com>; Fri,  3 Jan 2020 12:36:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 IEBKTTL9AFXg for <xml2rfc@ietfa.amsl.com>; Fri,  3 Jan 2020 12:36:24 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2F7A120045 for <xml2rfc@ietf.org>; Fri,  3 Jan 2020 12:36:23 -0800 (PST)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:56963 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1inTgE-00049Z-VN; Fri, 03 Jan 2020 12:36:23 -0800
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, xml2rfc@ietf.org
References: <918df451-55de-9bd2-688b-37d2d83762b5@gmail.com> <d8763b85-2a6c-e927-b50b-1d6fa9a8f361@gmx.de> <1b6c8b07-df98-6b8e-9144-c203d23f632c@gmail.com> <f7615a5e-a4bb-bc0d-6cb4-5f1297c24c23@levkowetz.com>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <9badd4e6-0fd0-25aa-c2c0-9038b06b7549@levkowetz.com>
Date: Fri, 3 Jan 2020 21:36:12 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <f7615a5e-a4bb-bc0d-6cb4-5f1297c24c23@levkowetz.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="5MtHUlba7SCh0VnWlfaqTsQ9tbnqTCL4f"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: xml2rfc@ietf.org, brian.e.carpenter@gmail.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/AAjh3CFsRpqVcmVBQtYYu3ko63M>
Subject: Re: [xml2rfc] <country> in v3
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: Fri, 03 Jan 2020 20:36:26 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--5MtHUlba7SCh0VnWlfaqTsQ9tbnqTCL4f
Content-Type: multipart/mixed; boundary="OKha0UVicUMwfCC49CHKrPa15wgbeXb6j";
 protected-headers="v1"
From: Henrik Levkowetz <henrik@levkowetz.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, xml2rfc@ietf.org
Message-ID: <9badd4e6-0fd0-25aa-c2c0-9038b06b7549@levkowetz.com>
Subject: Re: [xml2rfc] <country> in v3
References: <918df451-55de-9bd2-688b-37d2d83762b5@gmail.com>
 <d8763b85-2a6c-e927-b50b-1d6fa9a8f361@gmx.de>
 <1b6c8b07-df98-6b8e-9144-c203d23f632c@gmail.com>
 <f7615a5e-a4bb-bc0d-6cb4-5f1297c24c23@levkowetz.com>
In-Reply-To: <f7615a5e-a4bb-bc0d-6cb4-5f1297c24c23@levkowetz.com>

--OKha0UVicUMwfCC49CHKrPa15wgbeXb6j
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Follow-up:

On 2020-01-03 21:24, Henrik Levkowetz wrote:

>>=20
>> I really hope it doesn't "want" an ISO code, since RFC7991 says nothin=
g about
>> that. It's very convenient that they are available, though.
>=20
> xml2rfc recognizes the ISO 3166 2-letter, 3-letter, official, and commo=
n names
> of countries.  In cases where a name or abbreviation in common use isn'=
t
> recognized, I'm happy to add extra entries.  I've already done so for '=
UK',
> and will do so for "P.R. China" in the next release.

Added in my code.

>>=20
>> It takes some cheating to produce:
>>=20
>> Dilbert Engineer
>> Pointy Haired Products LLC
>> 42 Deepinit Street
>> Mudgrad 7991
>> Elbonia
>> Email: dilbert@example.com
>>=20
>>> Another issue here is that it has unintended consequences with respec=
t
>>> to Taiwanese users, as they would have to use "Taiwan (Province of Ch=
ina)".
>>=20
>> That's a serious problem. But they can simply omit <country>.

I cannot reproduce the problem above.  Using <country>Taiwan</country>
works fine when I test it with xml2rfc 2.37.0.

Regards,

	Henrik


--OKha0UVicUMwfCC49CHKrPa15wgbeXb6j--

--5MtHUlba7SCh0VnWlfaqTsQ9tbnqTCL4f
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl4Ppb0ACgkQTptXS4+7
FxoAYw/+NCOr2uV4kg2s6DVEnKEGlkjLlw6E6fvP5DgF5Biwt1RUtSpNw2939om3
s46yvjA3579zkW0xZQmo7XWNYCsb/FwYIU3QgaKEcG0gtk6P/KAq3BsB3CWD9LhJ
95gaD2QhpgRaqR5JIEraT4Fk6ga+cqZ01oyZR/7siHQt7XIcrOxTYNAEePywTPRV
s6zZ3ZS/mrEuF1K2AV8G7L/3un+Pol2NcTZ9Pj4oRdBsSQNhXQX7zSEHs/Ycx6Tg
AYJV1Ex8Blo7C/AiyCov2uMQL1tXHt5Bhk64nQUG0BL/PA7cIRloTxipHAXtJoaE
Cpqn1tDCuczheesR4FgvjJvEchJuMj0krGOENOaprk+SL5HrS8pV7nZGPR5oFeb7
8gpy/s4lZPrGwzxXPzwJUYhFFWcDHZSGr+tl52QwwU993lpZVf/8aRtQN5lCJUHE
8/oA0N8YeaRmwPV1VFUpp0KN6SX+YmZEdsMZx36e3HMXSMYKDWvSBgepZpF73i9q
zOOPrzK/PJDtQkCBUVQA6YTyQjrh7BQQw8fdta/iKwd8QUOx86HjnBk67DL0phjN
lUvefYFaocxiobXB9ZIblxuu3wrgeF/Dm5dbALgrQuFd6uFDxq+x8UCCY88jEKav
nvANP/gmfaVyIhEMnhyykKk+r7uxIwSg89lpWRus77Z2Ijor5wk=
=qMe7
-----END PGP SIGNATURE-----

--5MtHUlba7SCh0VnWlfaqTsQ9tbnqTCL4f--


From nobody Fri Jan  3 23:24:09 2020
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 43B29120124 for <xml2rfc@ietfa.amsl.com>; Fri,  3 Jan 2020 23:24:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=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 (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 QJxjpwCduMtq for <xml2rfc@ietfa.amsl.com>; Fri,  3 Jan 2020 23:24:06 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 2F1E912011F for <xml2rfc@ietf.org>; Fri,  3 Jan 2020 23:24:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1578122629; bh=BBSdXFMljkbSHUID6DkyCsUq4NdB5Kbu3IjXtkdf0+0=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=LAFaMgAWtPYyboh1GV9qQl4k26Li0fD+Nk/v2I8YP5Mj99/pZeB7Xtn3iZOiQG8Jg SYzXz32XKCMubMM9tjilcLaOc+BOqO2gJOnU/9BenFyvUQyf9+FiThvNpsQFGGOc+S rmRYqKXQiE0sCiwKvHlXNQ6NI050565YLR1GZBu8=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([91.61.53.194]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MO9zH-1j3MC41h2v-00OWqQ; Sat, 04 Jan 2020 08:23:49 +0100
To: Henrik Levkowetz <henrik@levkowetz.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, xml2rfc@ietf.org
References: <918df451-55de-9bd2-688b-37d2d83762b5@gmail.com> <d8763b85-2a6c-e927-b50b-1d6fa9a8f361@gmx.de> <1b6c8b07-df98-6b8e-9144-c203d23f632c@gmail.com> <f7615a5e-a4bb-bc0d-6cb4-5f1297c24c23@levkowetz.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <143ad0e7-3112-7db7-8e85-e9d24ddecbcc@gmx.de>
Date: Sat, 4 Jan 2020 08:23:48 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1
MIME-Version: 1.0
In-Reply-To: <f7615a5e-a4bb-bc0d-6cb4-5f1297c24c23@levkowetz.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:HPm1ihA74KOp5fRKQgNl92WylGe95PwA3sSpOpwWO0HHgopXxHU N8HqEOmMAQxGPpFUqP1O3+QXkBnP6ZBhP8aGxmQuw/KrvOcia4az5nboLF6/tEeJSOYmnmm Ma/pXrWwUcAd5jju88rRNuaFv94Iu2GG/+f2mQobkYtIJChatta6PoivELMo8zE8m0xJWtv aycSPxelwQ1AwNrP97GRA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:yhm7H8YlePE=:xqWdzzXygOlc14f1+ofF1z NiZVAqJgy392ZxVs7+JdJia7BqodF3CYYQ+PUNEUpv8A5Ck7fIcQX+D9XWUpZzDryctJ4Sr7y QJ3Tauz9afvOrA9+54k7KkhJ4nLCeNhYvimC2FrfZARQ2iHmc/8bNIRSvsZQQlPFIoTxBpWda u1apaDN3uo6MClfPaCQUa2tU9T7N2ONO2Obdjdhhw8ecHh5SIX3+5l5rg+K+gB22UcG+gqJbm OdayaCwanVTN9joMOXgsXswaaTzol6W4AA8nFk5Xm++ntMMfi1Re1UwHCRuog1RPRX8yP8gjy 1/tM1b6njEux/ioBEB6Fjax3eiCj6ERtfkxbJOdmMozK1DZQ1/Nvuaki5A8+euTUamRysFoNM SN2tkkAeha2IkCnT6vfJoz52xr2TQ8xSBtxMU5dyQmm28WDZiHqji96B66maiVnEdBiEVHmrF lG/4GQT6mek+R86E25ZTuNYk783yfTPx/Y/oUqFl5CSkVHwnlUDgjap9bMehFVO9MgVVOXwbQ BtglhQ9ZXiXeJmYDgkzCUGMYJVQUy6tWE9uQVjAQkMoA41Us54l8cgdchebuq/CmnuKoSWX37 56TQ7ifUKiG/s9UDm62DDL9V2wSEy3tf1cXzc7fLcybSVFPJSTf3ww1MHD0MHTTASMtJRSCg/ uXyvtZuz5zXVDUs7PGLkVicLSSTtUOcEVEFw/cD9vNEkMT8Xxo8y2+eDhxrxAjtE0zQO7crvV sEDyOBQ6WFmWsUU+lu9zg0T0/wnbDfaLCM7g94lno5zPrrgYs871e3jjWXHG0oQRFwbMUD+KH nlKdpgZdNsR+dF8gx6MrZ5LAfSPCqPCqtOInrfu9HJ8G49TQsHcooOZqLoHL3d4Bvq+aEnx0A RpWCU1sCYVqNLeq5DAuhExuFz4fheBw1FQNfdLyhxqU7uTuUva1V7kXMXWrnVzo5k61y7zHIu R2ekyPUw0GVqPIyyLmcRpaWtGNi+tAeUDGRSe6gIr8Y93CLcyGawBriImhyvMniQzTLHGxml+ kmSXx53sWz21r0fkMwOY5mzYKfiNkqqSMbnm5F4OXvTYRRC8EguRs50yYXM5XNJugIlCOtuHC eNpxq0X4E29HYl5r+M/8b1CtCo7UBxzNl1p3zN60G64NP7blCEKwuSu8kZEQOCa/yvkrC8qHj V3Of5gELqLWZF25VYZJitrgruPakh7eOR8lMckSfsPTzcu43iQcVHDsYN+njztVuvtQwWlgLP FNOyIENvSD6rFUvjs8YQ7V9/WqNHReL8rZX97e+toB6QCrlp9wUEkD51N3iQ=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/AYY-LCfalkhcVs1g4iIzae9YzgM>
Subject: Re: [xml2rfc] <country> in v3
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: Sat, 04 Jan 2020 07:24:08 -0000

On 03.01.2020 21:24, Henrik Levkowetz wrote:
> Hi Brian,
>
> On 2020-01-03 20:43, Brian E Carpenter wrote:
>> On 03-Jan-20 20:36, Julian Reschke wrote:
>>> On 02.01.2020 20:58, Brian E Carpenter wrote:
>>>> For some reason, it appears that <country>P.R. China</country> causes=
 problems in v3, but <country>China</country> is OK.
>>>>
>>>> The problem I see is that <country> is simply ignored, and <code> is =
also ignored,
>>>> when the "P.R" was included.
>>>>
>>>> I think there is a similar issue with commas included in <street>.
>>>>
>>>> For both, RFC7991 says "Content model: only text content." I don't se=
e that this
>>>> should exclude punctuation marks.
>>>>
>>>> Regards
>>>>      Brian Carpenter
>>>
>>> xml2rfc wants an "ISO short name" here (see
>>> <https://www.iso.org/obp/ui#search> for a lookup UI).
>>
>> I really hope it doesn't "want" an ISO code, since RFC7991 says nothing=
 about
>> that. It's very convenient that they are available, though.
>
> xml2rfc recognizes the ISO 3166 2-letter, 3-letter, official, and common=
 names
> of countries.  In cases where a name or abbreviation in common use isn't
> recognized, I'm happy to add extra entries.  I've already done so for 'U=
K',
> and will do so for "P.R. China" in the next release.
> ...

If this is the case, it should be properly documented (otherwise we
don't have a spec but just a single implementation that has some
heuristics that affect the generated RFC text). In particular, extra
entries would need to be documented.

Looking at the Taiwan case:

>       <author surname=3D"Taiwan" initials=3D"T." fullname=3D"Tai Taiwan"=
>
>          <address>
>             <postal>
>                <extaddr>EXTADDR-1</extaddr>
>                <extaddr>EXTADDR-2</extaddr>
>                <extaddr>EXTADDR-3</extaddr>
>                <street>STREET-1</street>
>                <street>STREET-2</street>
>                <street>STREET-3</street>
>                <pobox>POBOX</pobox>
>                <sortingcode>SORTINGCODE</sortingcode>
>                <code>CODE</code>
>                <cityarea>CITYAREA</cityarea>
>                <city>CITY</city>
>                <region>REGION</region>
>                <country>Taiwan</country>
>             </postal>
>          </address>
>       </author>

produces

>    Tai Taiwan
>    EXTADDR-1
>    EXTADDR-2
>    EXTADDR-3
>    STREET-1
>    STREET-2
>    STREET-3
>    POBOX
>    CITY, REGION CODE
>    Taiwan

So it falls back to US address formatting, but doesn't generate any warnin=
g.

Now,

>       <author surname=3D"Taiwan" initials=3D"T." fullname=3D"Tai Taiwan2=
">
>          <address>
>             <postal>
>                <extaddr>EXTADDR-1</extaddr>
>                <extaddr>EXTADDR-2</extaddr>
>                <extaddr>EXTADDR-3</extaddr>
>                <street>STREET-1</street>
>                <street>STREET-2</street>
>                <street>STREET-3</street>
>                <pobox>POBOX</pobox>
>                <sortingcode>SORTINGCODE</sortingcode>
>                <code>CODE</code>
>                <cityarea>CITYAREA</cityarea>
>                <city>CITY</city>
>                <region>REGION</region>
>                <country>Taiwan (Province of China)</country>
>             </postal>
>          </address>
>       </author>

yields:

>    Tai Taiwan
>    EXTADDR-1
>    EXTADDR-2
>    EXTADDR-3
>    STREET-1
>    STREET-2
>    STREET-3
>    POBOX
>    CITY

So the country name is simply dropped, again without warning.

(I would open a ticket, but it seems that tickets opened by me are
ignored anyway)

Using TW or TWN as country names gets me:

>    Tai Taiwan
>    EXTADDR-1
>    EXTADDR-2
>    EXTADDR-3
>    STREET-1
>    STREET-2
>    STREET-3
>    POBOX
>    CITY, REGION CODE
>    Taiwan, Province of China

which indicates that the expected short name is "Taiwan, Province of
China", not "Taiwan (Province of China)" (which is what I get from
<https://www.iso.org/obp/ui#search> which agrees with
<https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes>").

I continue to believe that we are wasting time and energy here. There's
a reason why RFC 7991 has "postalLine"; it allows authors to format
their postal address exactly the way they want it; and that should be
sufficient. We should just get rid of any requirements made by the HTML
spec with respect to HCARD annotations and be done with it.

Best regards, Julian





From nobody Mon Jan  6 06:06:19 2020
Return-Path: <alexandre.petrescu@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 046DD120122 for <xml2rfc@ietfa.amsl.com>; Mon,  6 Jan 2020 06:06:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.069
X-Spam-Level: 
X-Spam-Status: No, score=0.069 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, 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 BI6Pib2Jd1-s for <xml2rfc@ietfa.amsl.com>; Mon,  6 Jan 2020 06:06:16 -0800 (PST)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 F048612008A for <xml2rfc@ietf.org>; Mon,  6 Jan 2020 06:06:15 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 006E6Dlv031946 for <xml2rfc@ietf.org>; Mon, 6 Jan 2020 15:06:13 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id B916B2043E7 for <xml2rfc@ietf.org>; Mon,  6 Jan 2020 15:06:13 +0100 (CET)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id A64E02043E5 for <xml2rfc@ietf.org>; Mon,  6 Jan 2020 15:06:13 +0100 (CET)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 006E6DjL027569 for <xml2rfc@ietf.org>; Mon, 6 Jan 2020 15:06:13 +0100
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: xml2rfc@ietf.org
References: <e8a25961-5ac9-d35e-77dd-bf86f45cd077@gmail.com>
Message-ID: <57cffb7d-85ce-9a2b-3e8a-fad99116ccd2@gmail.com>
Date: Mon, 6 Jan 2020 15:06:13 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1
MIME-Version: 1.0
In-Reply-To: <e8a25961-5ac9-d35e-77dd-bf86f45cd077@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/XI5kyaaB7XFyoE8y-z-LukzgnW4>
Subject: [xml2rfc] right place to discuss xml2rfc.tools.ietf.org?
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: Mon, 06 Jan 2020 14:06:18 -0000

Hi,

Is this the right place to discuss the GUI of 
https://xml2rfc.tools.ietf.org ?

(I am looking for how to generate
draft-blah-blah.pdf instead of the current
draft-blah-blah.txt.pdf)

Alex


From nobody Wed Jan  8 14:41:22 2020
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 9147C12010C for <xml2rfc@ietfa.amsl.com>; Wed,  8 Jan 2020 14:41:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level: 
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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 BX98-Vhzf2S9 for <xml2rfc@ietfa.amsl.com>; Wed,  8 Jan 2020 14:41:19 -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 13EB71200C7 for <xml2rfc@ietf.org>; Wed,  8 Jan 2020 14:41:19 -0800 (PST)
Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 008MfGDY063130 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 8 Jan 2020 16:41:17 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1578523277; bh=fDOrJwk9CEZOoaD0OtBtTtKbfME1TGol1UHmFlFWsJ8=; h=Subject:To:References:From:Date:In-Reply-To; b=ah90njnSOBndZp8Xt//L4WJoVDG2PBNAnJFejYul9r1eyVWD7DPKnOs56IOSspSrL dfvbQRdxj0URMg1wxTUob+FztErHDUB6j2foIFMzUaBX4NOAv07jEWqVKsMIrZi9Iw u7MEpp3ZcQQflXxAz4Os2GcOzA/gFyDwtpQ1Olmk=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, xml2rfc@ietf.org
References: <e8a25961-5ac9-d35e-77dd-bf86f45cd077@gmail.com> <57cffb7d-85ce-9a2b-3e8a-fad99116ccd2@gmail.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <385181f8-33e8-a881-6722-b4fe9f3d8feb@nostrum.com>
Date: Wed, 8 Jan 2020 16:41:16 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <57cffb7d-85ce-9a2b-3e8a-fad99116ccd2@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/9GVFo69_R76QgkfSFBoLdkAGC1I>
Subject: Re: [xml2rfc] right place to discuss xml2rfc.tools.ietf.org?
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: Wed, 08 Jan 2020 22:41:21 -0000

Hi Alex -

This list will reach the right people, but a better place might be 
tools-discuss@ since this is really a question about how the web-service 
wrapping that GUI works (which runs at tools.ietf.org) rather than how 
xml2rfc itself works.

RjS

On 1/6/20 8:06 AM, Alexandre Petrescu wrote:
> Hi,
>
> Is this the right place to discuss the GUI of 
> https://xml2rfc.tools.ietf.org ?
>
> (I am looking for how to generate
> draft-blah-blah.pdf instead of the current
> draft-blah-blah.txt.pdf)
>
> Alex
>
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc


From nobody Tue Jan 14 10:36:28 2020
Return-Path: <henrik@levkowetz.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 AC3AF120B93; Tue, 14 Jan 2020 10:36:20 -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 LJ-ciL4X4AMd; Tue, 14 Jan 2020 10:36:16 -0800 (PST)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F023312096B; Tue, 14 Jan 2020 10:36:15 -0800 (PST)
Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1irR31-0000Sv-RH; Tue, 14 Jan 2020 10:36:15 -0800
To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
Message-Id: <E1irR31-0000Sv-RH@durif.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Tue, 14 Jan 2020 10:36:15 -0800
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Rcpt-To: rfc-markdown@ietf.org, xml2rfc-dev@ietf.org, xml2rfc@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on durif.tools.ietf.org); SAEximRunCond expanded to false
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/16ypUK5qTn0JgPSn0yTA1F3MjZg>
Subject: [xml2rfc] New xml2rfc release: v2.38.0
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: Tue, 14 Jan 2020 18:36:21 -0000

Hi,

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

Release notes:

xml2rfc (2.38.0) ietf; urgency=medium

  * Tweaked the preptool handling of <xref> in <toc>.  Further addresses
    issue #466, fixing an issue that could occur if a section used for
    instance <sub> or <sup>.

  * Fixed an off-by-one error in list indexing during text wrapping of
    first page header content.  Fixes issue #483.

  * Tweaked the output for <xref format='title'> when refering to Reference 
    entries.

  * Fixed a Py2/Py3 code compatibility issue

  * Tweaked the handling of <artwork type='ascii-art'> to insert '(Artwork 
    only available as ...)' text also for text content which is only whitespace.

  * Changed utils.isblock() to use a list of element tags derived from the 
    schema instead of a static list, to avoid discrepancies between schema
    and code.

  * Changed the parser's handling of inter-element blank text to keep instead 
    of remove, in order to not drop intentional blank space between for 
    instance <xref> instances.

  * Reverted the silencing of warnings related to postal address input.  
    Addresses issue #437.

  * Added code to deal better with <iref> as a direct child of <section>.  
    Fixes issue #479.

  * Fixed a bug where text after <iref> was lost by the text formatter.  
    Fixes issue #480

  * Added an option to list recognised country names for use with 
    <country>, and changed the note() emitted for unrecognized countries to a 
    warning.  Added some new alternative country strings.

  * Updated test masters

  * Fixed a problem with <author> entries with only <organization> 
    information.  Fixes issue #424.

  * Added a minimum width setting for tables, in order to avoid table 
    captions rendering in very narrow space when the table itself is narrow.  
    Fixes issue #482.

  * Avoid double space after initial when <contact> is rendered inline.  
    Fixes issue #478.

  * Added code to recognise another case of inconsistent table row cell 
    counts and report the issue.

  * Added 'P.R. China' as a recognized country name.

  * From Python 3.2 and later, cgi.encode() is deprecated.  Changed to use
    html.encode() instead.

 -- Henrik Levkowetz <henrik@levkowetz.com>  14 Jan 2020 18:08:08 +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 http://svn.tools.ietf.org/svn/tools/xml2rfc/tags/cli/2.38.0'

Regards,

	Henrik
	(via the mkrelease script)


From nobody Mon Jan 20 07:34:00 2020
Return-Path: <henrik@levkowetz.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 B75C012082B; Mon, 20 Jan 2020 07:33:47 -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 3ZcsD23KrNJh; Mon, 20 Jan 2020 07:33:43 -0800 (PST)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F2E4120837; Mon, 20 Jan 2020 07:33:43 -0800 (PST)
Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1itZ3Q-0003b8-Q5; Mon, 20 Jan 2020 07:33:40 -0800
To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
Message-Id: <E1itZ3Q-0003b8-Q5@durif.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Mon, 20 Jan 2020 07:33:28 -0800
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Rcpt-To: rfc-markdown@ietf.org, xml2rfc-dev@ietf.org, xml2rfc@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on durif.tools.ietf.org); SAEximRunCond expanded to false
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/osDoNPeL_j0xZnKM-xyBLKExdgQ>
Subject: [xml2rfc] New xml2rfc release: v2.38.1
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: Mon, 20 Jan 2020 15:33:54 -0000

Hi,

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

Release notes:

xml2rfc (2.38.1) ietf; urgency=medium

  * Added a preptool check for numbered sections occurring after or under
    unnumbered sections, and changed the code for Reference sections to
    not emit section numbers if the previous section was unnumbered.  
    Fixes issue #433

  * Refactored the code for reference anchor to display string mapping,
    locating it in a base class method.  Updated it to honour the symRefs
    setting.  Fixes issue #476.

  * Added installation of Python 3.8 to Dockerfile, and updated the minor
    version numbers for the other Python installation stanzas.

  * Fixed a problem rendering multiple authors with organization 
    showOnFrontPage='false'.  Further addresses issue #483.

  * Added a switch --no-external-js, and some other --no-* switches to 
    invert boolean settings.  Fixes issue #486.

  * Added an early return from cache() when repeated attempts to fetch an 
    URL fails.

 -- Henrik Levkowetz <henrik@levkowetz.com>  20 Jan 2020 15:29:17 +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 http://svn.tools.ietf.org/svn/tools/xml2rfc/tags/cli/2.38.1'

Regards,

	Henrik
	(via the mkrelease script)


From nobody Mon Jan 20 10:33:58 2020
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 2A11F120800; Mon, 20 Jan 2020 10:33:47 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 LW-NjYBYsRTM; Mon, 20 Jan 2020 10:33:41 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 5B694120041; Mon, 20 Jan 2020 10:33:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1579545217; bh=rDQFKlD3F85v82bS3Dgz632ByoRIXBqvthhbf6KNXzo=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=dcwQs+H8a0nA4LtywHkkSoAVSnMoeLDYzvOLvx8KJhExZftJ38oE+PNW29syM46KM Yf7zQ1rXxsKGDk0hhG+47zuSNhlflx5PuzZFopuulSfAt7AZ0Qp455KT2Y/MYhj49N V9jujG9OQQ/P1JTRrLAckngliI0ogb6jFLkckJMA=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([91.61.63.42]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MfYPi-1jZGDR1uW0-00fzxz; Mon, 20 Jan 2020 19:33:37 +0100
To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
References: <E1itZ3Q-0003b8-Q5@durif.tools.ietf.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <973bc456-19af-76e8-d8e5-ef506f587fe7@gmx.de>
Date: Mon, 20 Jan 2020 19:33:32 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <E1itZ3Q-0003b8-Q5@durif.tools.ietf.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:8ObCG/dRoLRZ2LhAFcINeBgPGGI86tdC7Jn0dY2m4UcqCxJzw+y kDwUEFv/OM/BhNMFVmBiQt1NRdT/OhlfZiZRKvUi3LlHVq2pwWvuuYSbqA8+/tcI+r6ul1U r1xDZnECWjlYy5tRD7SsS7bNTfdlAD8ZqolZo8PkhqBUgRbFZhU2rcXGGCBZE7+ExflCI0s QsR1HaEfIepSVR1jpqRpQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:T/7Xw3CAPFw=:mEF+WXHCzrBsOGY+l2Dx89 oWbdl9qoumj8fmXki8MmHjyhyz1FfmSBm1bTBH77DXMWJOrsJqBr+kOS/KYEkUy5Hyd5/0PNh /ifNGB3jA1BDfBZhnj11/ms7J4z+C6GUDu8XiDCQwGJTA52fAKpO+LX6XxdX9ttE5Vp1ONCYf p3SRQNdT7RMg/GgUd5s71eApkrFg2E4W8SgKsnkf1Gbf54iNXk2KSFwXyucFb7P/cgoB9b0TS YP1PAqujzU+9295QFjXpk92fD8EY4+der0BLR3CeUV7zIuEoh6R5VHRp+khVKFu3ajvbVlhmt 0b/ub47LqlDjefrMUzNcoRSkj8leisAKUqHRdTb56/lOLdvkb++Fjfg30dDFkj2YCa5T+niLx QG4FJW3iRLTOOuj5CSc5B3ca8bIXoQO3mVnf0Auk/7MQgQHOeRAK+kbRGCbOfSYgefOvTRBKj npE3WXHnCa+GzRiI6WEK1/xr1mqGw/192CLOj4UnI/Oej6vBeAtO55n0Ow6BKLt8MPYQD6TMv aCjqek05KmIVEuAuZfJ926I0b4OVTzx/6TwPKtSpHuZyFcFAGmGGG9XTsMgsBcAZj4yhB5TGi cbjG6RO+xYf+JVjjLSrCTI8OzV8s0kqd2dEaNFciZ4tGI1nmxK/IJF3bOJ6oVzAaBjuqGfy06 d+AZ2r/d/fgVhYxEDpzPXE0GY1gVvSD/yjy3IMeqm54eJNERdq7T7q267TZOYKV/3KNza0o8t Hdy8SRjtYtK/D1a0ijqSJTDJvI62hj+Ps9xGbmNp1fsgB17jjsaYiUTMRZGfu2Rlq9hgygioD SaQseUtU7L6ZGPKkRCKzAkJDMmVC5fvlr/Ze0hASHVf7maS17FZb2XPNTQCi8IK2WYaIntqpu jmk9l5yW1Mlul1U/qQKKFIyxqbCqKhL9HVztO+1QVcM2xlv7cJWGlUAt4W1KYRFuo63XkUUFd sJhZh3kkNt3atx0s2xk58KpCo5EFZCMhyJH/rhxHka+OVyDjNf1rVcrafHXbdIsEKDcdsYA2/ sRbeo3B0eNJ+jn1UKQax6hBkU3InqySNGJnwa3BZih7D8fyVhd54mA39zXOrDjTTmPcjJPQVT hG59Ue75/qry4/CPxPPLgRjrssIokVqWHYtZI6iXzhUPkPvVeIID9fdhnxCScvBdmhLuQ1/xs g11WvxQhoncu4JAstwils4mwGVLx+SYJnCGid3rsouuSgO7IgO8lH9rwmtiRynzCMrcyHWmMV EofvJMaGCsAKiw9jvBen3xchc/XruEL912AEnWYbPGoGQQQjWR/mB+wR2wVo=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/5AX7ECdvAqTy5J-zRpE98iRCFzE>
Subject: Re: [xml2rfc] [xml2rfc-dev] New xml2rfc release: v2.38.1
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: Mon, 20 Jan 2020 18:33:47 -0000

On 20.01.2020 16:33, Henrik Levkowetz wrote:
>
> Hi,
>
> This is an automatic notification about a new xml2rfc release,
> v2.38.1, generated when running the mkrelease script.
>
> Release notes:
>
> xml2rfc (2.38.1) ietf; urgency=3Dmedium
>
>    * Added a preptool check for numbered sections occurring after or und=
er
>      unnumbered sections, and changed the code for Reference sections to
>      not emit section numbers if the previous section was unnumbered.
>      Fixes issue #433
>
>    * Refactored the code for reference anchor to display string mapping,
>      locating it in a base class method.  Updated it to honour the symRe=
fs
>      setting.  Fixes issue #476.
> ...

The above may have broken <xref>s to children of <reference-group>. See
<https://trac.tools.ietf.org/tools/xml2rfc/trac/attachment/ticket/487/>.

Best regards, Julian


From nobody Mon Jan 20 12:00:51 2020
Return-Path: <daveoran@orandom.net>
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 6EE0D12082C for <xml2rfc@ietfa.amsl.com>; Mon, 20 Jan 2020 12:00:42 -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, HTML_MESSAGE=0.001, 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 cnb5pJXosY06 for <xml2rfc@ietfa.amsl.com>; Mon, 20 Jan 2020 12:00:36 -0800 (PST)
Received: from spark.crystalorb.net (spark.crystalorb.net [IPv6:2607:fca8:1530::c]) (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 96A731208AD for <xml2rfc@ietf.org>; Mon, 20 Jan 2020 12:00:36 -0800 (PST)
Received: from [192.168.15.102] ([IPv6:2601:184:407f:80ce:3498:cbc1:44fd:d28c]) (authenticated bits=0) by spark.crystalorb.net (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id 00KK0VOH009554 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO) for <xml2rfc@ietf.org>; Mon, 20 Jan 2020 12:00:33 -0800
From: "David R. Oran" <daveoran@orandom.net>
To: xml2rfc@ietf.org
Date: Mon, 20 Jan 2020 15:00:26 -0500
X-Mailer: MailMate (1.13.1r5676)
Message-ID: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_1ED7FB47-97D0-48E5-AF8C-5FC249BD1924_="
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/08tM38FXPkaNDS_oy8MjzJybmx0>
Subject: [xml2rfc] Novice bad user on device, or Catch-22?
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: Mon, 20 Jan 2020 20:00:49 -0000

--=_MailMate_1ED7FB47-97D0-48E5-AF8C-5FC249BD1924_=
Content-Type: text/plain; charset="UTF-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit

I have a new Internet Draft to write, so I decided to bite the bullet 
and do it in V3. Rather than write in V2 and try the converter, I 
started out right away with V3 syntax. I didn’t get very far. I tried 
both the most recent xml2rfc by installing it on my machine, and the web 
tool and got identical errors.

If I follow the described syntax in RFC7991, the RFC Editor FAQ in 
https://ftp.ripe.net/rfc/v3test/FAQ-2019-02.html and the example in 
draft-hoffman-rfcexamples-latest as below:

	<?xml version="1.0" encoding="US-ASCII"?>
	<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>

	<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
	<?rfc strict="yes" ?>
	<?rfc toc="yes"?>
	<?rfc tocdepth="4"?>
	<?rfc symrefs="yes" ?>
	<?rfc sortrefs="yes" ?>
	<?rfc compact="yes" ?>
	<?rfc subcompact="no" ?>
	<rfc
		version=‘3’
		ipr='trust200902'
		category='exp'
		submissionType='IRTF'
		docName='draft-oran-icnrg-reflexive-forwarding-00'
		xml:lang='en' xmlns:xi="https://www.w3.org/2001/XInclude">

	<front>
		<seriesInfo name='Internet-Draft' 
value='draft-oran-icnrg-reflexive-forwarding-00'/>
	    <title abbrev='ICN Reflexive Forwarding'>Reflexive Forwarding for 
CCNx and NDN Protocols
	    </title>



I get

	% xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
	Incompatible schema information: found "rfc2629.dtd" in <DOCTYPE> of a 
version 3 file.

If I leave off the “version=‘3’, as below

	<?xml version="1.0" encoding="US-ASCII"?>
	<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>
	<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
	<?rfc strict="yes" ?>
	<?rfc toc="yes"?>
	<?rfc tocdepth="4"?>
	<?rfc symrefs="yes" ?>
	<?rfc sortrefs="yes" ?>
	<?rfc compact="yes" ?>
	<?rfc subcompact="no" ?>

	<rfc
		ipr='trust200902'
		category='exp'
		submissionType='IRTF'
		docName='draft-oran-icnrg-reflexive-forwarding-00'
		xml:lang='en' xmlns:xi="https://www.w3.org/2001/XInclude">

	<front>
		<seriesInfo name='Internet-Draft' 
value='draft-oran-icnrg-reflexive-forwarding-00'/>
	    <title abbrev='ICN Reflexive Forwarding'>Reflexive Forwarding for 
CCNx and NDN Protocols
	    </title>

I get:

		xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
		Error: Unable to validate the XML document: 
draft-oran-icnrg-reflexive-forwarding.xml
		 <string>: Line 23: No declaration for attribute xmlns:xi of element 
rfc
		 <string>: Line 25: Element front content does not follow the DTD, 
expecting (title , author+ , date , area* , workgroup* , keyword* , 
abstract? , note*), got (seriesInfo title author author date area 
workgroup keyword keyword abstract )
		 <string>: Line 81: Element section content does not follow the DTD, 
expecting ((t | figure | texttable | iref)* , section*), got (name t )
		 <string>: Line 81: Element section does not carry attribute title
		 <string>: Line 81: No declaration for element name
		 <string>: Line 85: Element section content does not follow the DTD, 
expecting ((t | figure | texttable | iref)* , section*), got (name t )
		 <string>: Line 85: Element section does not carry attribute title
		 <string>: Line 85: No declaration for element name
		 <string>: Line 94: Element section content does not follow the DTD, 
expecting ((t | figure | texttable | iref)* , section*), got (name t 
section section )
		 <string>: Line 94: Element section does not carry attribute title
		 <string>: Line 94: No declaration for element name
		 <string>: Line 97: Element section content does not follow the DTD, 
expecting ((t | figure | texttable | iref)* , section*), got (name t 
table )
		 <string>: Line 97: Element section does not carry attribute title
		 <string>: Line 97: No declaration for element name
		 <string>: Line 98: No declaration for attribute keepWithNext of 
element t
		 <string>: Line 99: No declaration for element table
		 <string>: Line 99: No declaration for attribute title of element 
table

Clue bat please?

DaveO

--=_MailMate_1ED7FB47-97D0-48E5-AF8C-5FC249BD1924_=
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">I have a new Internet Draft to write, so I decided to bit=
e the bullet and do it in V3. Rather than write in V2 and try the convert=
er, I started out right away with V3 syntax. I didn=E2=80=99t get very fa=
r. I tried both the most recent xml2rfc by installing it on my machine, a=
nd the web tool and got identical errors.</p>

<p dir=3D"auto">If I follow the described syntax in RFC7991, the RFC Edit=
or FAQ in <a href=3D"https://ftp.ripe.net/rfc/v3test/FAQ-2019-02.html" st=
yle=3D"color:#3983C4">https://ftp.ripe.net/rfc/v3test/FAQ-2019-02.html</a=
> and the example in draft-hoffman-rfcexamples-latest as below:</p>

<pre style=3D"background-color:#F7F7F7; border-radius:5px 5px 5px 5px; ma=
rgin-left:15px; margin-right:15px; max-width:90vw; overflow-x:auto; paddi=
ng:5px" bgcolor=3D"#F7F7F7"><code style=3D"background-color:#F7F7F7; bord=
er-radius:3px; margin:0; padding:0" bgcolor=3D"#F7F7F7">&lt;?xml version=3D=
"1.0" encoding=3D"US-ASCII"?&gt;
&lt;!DOCTYPE rfc SYSTEM 'rfc2629.dtd'&gt;

&lt;?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?&gt;
&lt;?rfc strict=3D"yes" ?&gt;
&lt;?rfc toc=3D"yes"?&gt;
&lt;?rfc tocdepth=3D"4"?&gt;
&lt;?rfc symrefs=3D"yes" ?&gt;
&lt;?rfc sortrefs=3D"yes" ?&gt;
&lt;?rfc compact=3D"yes" ?&gt;
&lt;?rfc subcompact=3D"no" ?&gt;
&lt;rfc
    version=3D=E2=80=983=E2=80=99
    ipr=3D'trust200902'
    category=3D'exp'
    submissionType=3D'IRTF'
    docName=3D'draft-oran-icnrg-reflexive-forwarding-00'
    xml:lang=3D'en' xmlns:xi=3D"https://www.w3.org/2001/XInclude"&gt;

&lt;front&gt;
    &lt;seriesInfo name=3D'Internet-Draft' value=3D'draft-oran-icnrg-refl=
exive-forwarding-00'/&gt;
    &lt;title abbrev=3D'ICN Reflexive Forwarding'&gt;Reflexive Forwarding=
 for CCNx and NDN Protocols
    &lt;/title&gt;
</code></pre>

<p dir=3D"auto">I get</p>

<pre style=3D"background-color:#F7F7F7; border-radius:5px 5px 5px 5px; ma=
rgin-left:15px; margin-right:15px; max-width:90vw; overflow-x:auto; paddi=
ng:5px" bgcolor=3D"#F7F7F7"><code style=3D"background-color:#F7F7F7; bord=
er-radius:3px; margin:0; padding:0" bgcolor=3D"#F7F7F7">% xml2rfc draft-o=
ran-icnrg-reflexive-forwarding.xml
Incompatible schema information: found "rfc2629.dtd" in &lt;DOCTYPE&gt; o=
f a version 3 file.
</code></pre>

<p dir=3D"auto">If I leave off the =E2=80=9Cversion=3D=E2=80=983=E2=80=99=
, as below</p>

<pre style=3D"background-color:#F7F7F7; border-radius:5px 5px 5px 5px; ma=
rgin-left:15px; margin-right:15px; max-width:90vw; overflow-x:auto; paddi=
ng:5px" bgcolor=3D"#F7F7F7"><code style=3D"background-color:#F7F7F7; bord=
er-radius:3px; margin:0; padding:0" bgcolor=3D"#F7F7F7">&lt;?xml version=3D=
"1.0" encoding=3D"US-ASCII"?&gt;
&lt;!DOCTYPE rfc SYSTEM 'rfc2629.dtd'&gt;
&lt;?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?&gt;
&lt;?rfc strict=3D"yes" ?&gt;
&lt;?rfc toc=3D"yes"?&gt;
&lt;?rfc tocdepth=3D"4"?&gt;
&lt;?rfc symrefs=3D"yes" ?&gt;
&lt;?rfc sortrefs=3D"yes" ?&gt;
&lt;?rfc compact=3D"yes" ?&gt;
&lt;?rfc subcompact=3D"no" ?&gt;

&lt;rfc
    ipr=3D'trust200902'
    category=3D'exp'
    submissionType=3D'IRTF'
    docName=3D'draft-oran-icnrg-reflexive-forwarding-00'
    xml:lang=3D'en' xmlns:xi=3D"https://www.w3.org/2001/XInclude"&gt;

&lt;front&gt;
    &lt;seriesInfo name=3D'Internet-Draft' value=3D'draft-oran-icnrg-refl=
exive-forwarding-00'/&gt;
    &lt;title abbrev=3D'ICN Reflexive Forwarding'&gt;Reflexive Forwarding=
 for CCNx and NDN Protocols
    &lt;/title&gt;
</code></pre>

<p dir=3D"auto">I get:</p>

<pre style=3D"background-color:#F7F7F7; border-radius:5px 5px 5px 5px; ma=
rgin-left:15px; margin-right:15px; max-width:90vw; overflow-x:auto; paddi=
ng:5px" bgcolor=3D"#F7F7F7"><code style=3D"background-color:#F7F7F7; bord=
er-radius:3px; margin:0; padding:0" bgcolor=3D"#F7F7F7">    xml2rfc draft=
-oran-icnrg-reflexive-forwarding.xml
    Error: Unable to validate the XML document: draft-oran-icnrg-reflexiv=
e-forwarding.xml
     &lt;string&gt;: Line 23: No declaration for attribute xmlns:xi of el=
ement rfc
     &lt;string&gt;: Line 25: Element front content does not follow the D=
TD, expecting (title , author+ , date , area* , workgroup* , keyword* , a=
bstract? , note*), got (seriesInfo title author author date area workgrou=
p keyword keyword abstract )
     &lt;string&gt;: Line 81: Element section content does not follow the=
 DTD, expecting ((t | figure | texttable | iref)* , section*), got (name =
t )
     &lt;string&gt;: Line 81: Element section does not carry attribute ti=
tle
     &lt;string&gt;: Line 81: No declaration for element name
     &lt;string&gt;: Line 85: Element section content does not follow the=
 DTD, expecting ((t | figure | texttable | iref)* , section*), got (name =
t )
     &lt;string&gt;: Line 85: Element section does not carry attribute ti=
tle
     &lt;string&gt;: Line 85: No declaration for element name
     &lt;string&gt;: Line 94: Element section content does not follow the=
 DTD, expecting ((t | figure | texttable | iref)* , section*), got (name =
t section section )
     &lt;string&gt;: Line 94: Element section does not carry attribute ti=
tle
     &lt;string&gt;: Line 94: No declaration for element name
     &lt;string&gt;: Line 97: Element section content does not follow the=
 DTD, expecting ((t | figure | texttable | iref)* , section*), got (name =
t table )
     &lt;string&gt;: Line 97: Element section does not carry attribute ti=
tle
     &lt;string&gt;: Line 97: No declaration for element name
     &lt;string&gt;: Line 98: No declaration for attribute keepWithNext o=
f element t
     &lt;string&gt;: Line 99: No declaration for element table
     &lt;string&gt;: Line 99: No declaration for attribute title of eleme=
nt table
</code></pre>

<p dir=3D"auto">Clue bat please?</p>

<p dir=3D"auto">DaveO</p>
</div>
</div>
</body>
</html>

--=_MailMate_1ED7FB47-97D0-48E5-AF8C-5FC249BD1924_=--


From nobody Mon Jan 20 12:11:15 2020
Return-Path: <henrik@levkowetz.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 1AEF5120825 for <xml2rfc@ietfa.amsl.com>; Mon, 20 Jan 2020 12:11:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 T-ZZkt7ip3QY for <xml2rfc@ietfa.amsl.com>; Mon, 20 Jan 2020 12:11:07 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1EB1120809 for <xml2rfc@ietf.org>; Mon, 20 Jan 2020 12:11:07 -0800 (PST)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:59046 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1itdO6-0001iQ-EW; Mon, 20 Jan 2020 12:11:07 -0800
To: "David R. Oran" <daveoran@orandom.net>, xml2rfc@ietf.org
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com>
Date: Mon, 20 Jan 2020 21:10:58 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="WTfbIgLPEeuPjhnjxq6E852WCofX5ePgL"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: xml2rfc@ietf.org, daveoran@orandom.net
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/iJFmH__4BuB709Iwkgk3l4GG0Pg>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
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: Mon, 20 Jan 2020 20:11:13 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--WTfbIgLPEeuPjhnjxq6E852WCofX5ePgL
Content-Type: multipart/mixed; boundary="Or0HvuVePtL6xRCEwiaV7mfctK5hF7bgm";
 protected-headers="v1"
From: Henrik Levkowetz <henrik@levkowetz.com>
To: "David R. Oran" <daveoran@orandom.net>, xml2rfc@ietf.org
Message-ID: <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net>
In-Reply-To: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net>

--Or0HvuVePtL6xRCEwiaV7mfctK5hF7bgm
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi David,

You should simply remove "<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>" if your
<rfc/> element contains the "version=3D'3'" attribute.

Regards,

	Henrik

On 2020-01-20 21:00, David R. Oran wrote:
> I have a new Internet Draft to write, so I decided to bite the bullet=20
> and do it in V3. Rather than write in V2 and try the converter, I=20
> started out right away with V3 syntax. I didn=E2=80=99t get very far. I=
 tried=20
> both the most recent xml2rfc by installing it on my machine, and the we=
b=20
> tool and got identical errors.
>=20
> If I follow the described syntax in RFC7991, the RFC Editor FAQ in=20
> https://ftp.ripe.net/rfc/v3test/FAQ-2019-02.html and the example in=20
> draft-hoffman-rfcexamples-latest as below:
>=20
> 	<?xml version=3D"1.0" encoding=3D"US-ASCII"?>
> 	<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>
>=20
> 	<?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?>
> 	<?rfc strict=3D"yes" ?>
> 	<?rfc toc=3D"yes"?>
> 	<?rfc tocdepth=3D"4"?>
> 	<?rfc symrefs=3D"yes" ?>
> 	<?rfc sortrefs=3D"yes" ?>
> 	<?rfc compact=3D"yes" ?>
> 	<?rfc subcompact=3D"no" ?>
> 	<rfc
> 		version=3D=E2=80=983=E2=80=99
> 		ipr=3D'trust200902'
> 		category=3D'exp'
> 		submissionType=3D'IRTF'
> 		docName=3D'draft-oran-icnrg-reflexive-forwarding-00'
> 		xml:lang=3D'en' xmlns:xi=3D"https://www.w3.org/2001/XInclude">
>=20
> 	<front>
> 		<seriesInfo name=3D'Internet-Draft'=20
> value=3D'draft-oran-icnrg-reflexive-forwarding-00'/>
> 	    <title abbrev=3D'ICN Reflexive Forwarding'>Reflexive Forwarding fo=
r=20
> CCNx and NDN Protocols
> 	    </title>
>=20
>=20
>=20
> I get
>=20
> 	% xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
> 	Incompatible schema information: found "rfc2629.dtd" in <DOCTYPE> of a=
=20
> version 3 file.
>=20
> If I leave off the =E2=80=9Cversion=3D=E2=80=983=E2=80=99, as below
>=20
> 	<?xml version=3D"1.0" encoding=3D"US-ASCII"?>
> 	<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>
> 	<?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?>
> 	<?rfc strict=3D"yes" ?>
> 	<?rfc toc=3D"yes"?>
> 	<?rfc tocdepth=3D"4"?>
> 	<?rfc symrefs=3D"yes" ?>
> 	<?rfc sortrefs=3D"yes" ?>
> 	<?rfc compact=3D"yes" ?>
> 	<?rfc subcompact=3D"no" ?>
>=20
> 	<rfc
> 		ipr=3D'trust200902'
> 		category=3D'exp'
> 		submissionType=3D'IRTF'
> 		docName=3D'draft-oran-icnrg-reflexive-forwarding-00'
> 		xml:lang=3D'en' xmlns:xi=3D"https://www.w3.org/2001/XInclude">
>=20
> 	<front>
> 		<seriesInfo name=3D'Internet-Draft'=20
> value=3D'draft-oran-icnrg-reflexive-forwarding-00'/>
> 	    <title abbrev=3D'ICN Reflexive Forwarding'>Reflexive Forwarding fo=
r=20
> CCNx and NDN Protocols
> 	    </title>
>=20
> I get:
>=20
> 		xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
> 		Error: Unable to validate the XML document:=20
> draft-oran-icnrg-reflexive-forwarding.xml
> 		 <string>: Line 23: No declaration for attribute xmlns:xi of element =

> rfc
> 		 <string>: Line 25: Element front content does not follow the DTD,=20
> expecting (title , author+ , date , area* , workgroup* , keyword* ,=20
> abstract? , note*), got (seriesInfo title author author date area=20
> workgroup keyword keyword abstract )
> 		 <string>: Line 81: Element section content does not follow the DTD, =

> expecting ((t | figure | texttable | iref)* , section*), got (name t )
> 		 <string>: Line 81: Element section does not carry attribute title
> 		 <string>: Line 81: No declaration for element name
> 		 <string>: Line 85: Element section content does not follow the DTD, =

> expecting ((t | figure | texttable | iref)* , section*), got (name t )
> 		 <string>: Line 85: Element section does not carry attribute title
> 		 <string>: Line 85: No declaration for element name
> 		 <string>: Line 94: Element section content does not follow the DTD, =

> expecting ((t | figure | texttable | iref)* , section*), got (name t=20
> section section )
> 		 <string>: Line 94: Element section does not carry attribute title
> 		 <string>: Line 94: No declaration for element name
> 		 <string>: Line 97: Element section content does not follow the DTD, =

> expecting ((t | figure | texttable | iref)* , section*), got (name t=20
> table )
> 		 <string>: Line 97: Element section does not carry attribute title
> 		 <string>: Line 97: No declaration for element name
> 		 <string>: Line 98: No declaration for attribute keepWithNext of=20
> element t
> 		 <string>: Line 99: No declaration for element table
> 		 <string>: Line 99: No declaration for attribute title of element=20
> table
>=20
> Clue bat please?
>=20
> DaveO
>=20
>=20
>=20
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc
>=20


--Or0HvuVePtL6xRCEwiaV7mfctK5hF7bgm--

--WTfbIgLPEeuPjhnjxq6E852WCofX5ePgL
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl4mCVMACgkQTptXS4+7
FxqVfxAAn5uSC/b1iDGZrWBG/50m1UN7oAmuteQxmBzsiHMAT9UTbG6fHYC/DfHA
YT6VeF3DvXvG6EGqEDP7ajvxIBToViwyO+ZrzCI5Y4j4suAk/ieCK/eVToRldaMy
uqStFoc8yid/mF+g/hL1ZJuWZ7oD8gE2JF9F7xqXS+XBps2aUdonsCcclUYtsdcl
2d0RSoXFsKJwEY257tz3oFa0Nr3MUMphGKngE3N0WulhEYYv41pnjC/YJN2KUauW
fL0aWL+DGHaAa7hObIDUKtoe4aBDYerXEPyyI7PwsAwa3kAYgX98yoeZrd888tb6
A3yR4dTVDeBy0RN4cmhSQ+Vezr11+dKO9t3dum+8NoU5A4La64/THOpjkFZ6ZkIg
w+IKa7uevnjViU4MFGYgbDbGrXODwiVR1w4yyHWV8T2RI+nkK4BL8Fc1btR5e8Ed
qPrX7WKj5oTj4l99KUwI9NplS8OzxrLHNaKluFOA8hhnissLd47GE8CUGL3UkWwg
R+w2OkTpvYNbMjmqGcTtuFugCUuO6Cst+nlx8uDwuQrNFsuRIdFbRP2Ua3GZTEr+
fJprJ+KaTos7YwEFKrInLlzvbYh/N3Z/G1OHAjI6WarKTGpXRRZJ9R77Ke0nVAKB
fl7oom1kcM8ZbUnLkw51hpqiEOEznhh5QkEGS19gUcOfvXPzeNs=
=6dhf
-----END PGP SIGNATURE-----

--WTfbIgLPEeuPjhnjxq6E852WCofX5ePgL--


From nobody Mon Jan 20 12:55:25 2020
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 61EC912013D for <xml2rfc@ietfa.amsl.com>; Mon, 20 Jan 2020 12:55:24 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 H0oaVVWc_2aU for <xml2rfc@ietfa.amsl.com>; Mon, 20 Jan 2020 12:55:22 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (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 BEAA612001A for <xml2rfc@ietf.org>; Mon, 20 Jan 2020 12:55:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1579553676; bh=BAUvbuYkb5hp18STVDmTNLXQskvZfiDbSHW/NCpPXfo=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=P2HCCLY8PG13WfH+TePoUi6vxfnF2Dqeb4hzQWUrnVLjmT93YIcLZMzOJNGdR86fI Zn2y631Y4/cy7UIdC19XUNj2BKY+4pikiQJAzWn3/kvm8GHmgVR7g51l1HdIvXlvKL pQSGB/iD2YxvOrnFOfCm7PHRqQSAl5q+qu59KVmk=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([91.61.63.42]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MMGRA-1j9fJa2QrO-00JMnX; Mon, 20 Jan 2020 21:54:36 +0100
To: "David R. Oran" <daveoran@orandom.net>, xml2rfc@ietf.org
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <5bb374e6-182d-dd47-802e-28e437e3f7f8@gmx.de>
Date: Mon, 20 Jan 2020 21:54:35 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:wWJQHz/IB+IcazrLlBq+Ns5Sa775xnd8DfUOZwQVBXBmhre+gYd T28+Bi4ym6TB7WxZU0rsZPb6W04AHA/HEi2iLGEXco0GXiUZQp+H1jqv24pESfgBbq3+Pdl 2ZdndU7gEPGCsPsKrgzU1XQptB9kAww535oi9jRfWZR2COw+SERiZMZjVQx+dOUtwkXRQFU jBjGEV9m2QLgJvg5BMccw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:V3dOSVaEhJI=:c5bCJs9vQVVjWbj3e3l3vc vhN5v/qYYVmumYq8WABzaDslNlbN6WiW/o5nGrv8geH5WvT88WmXgaB+xFQQ/XQDJEqbA+ylI vZm7ETLuIaRkafhqJB6b6DdvA4xeayZG1cgQhxxQTbl3dKzzsp3ZRVer3I2Qo68BRuQLaH4U7 so/yblM03AZimVPBV9yIW715n+ipxyTl8HfYFIXbxAC4Qrnl1ahqDeZvJ19YCe22go0Mx6EX3 ErE5VljVDvrk55J+UpRpAt4QgL7VLBsdb9N6DBhLqP44CuTxrgUgvKhXHWGI0+PL/6CQuAosC kADxnieINecDaW5yqvjIhc6wiwcro7ZGMDVyTGFKnOClVG3pY6Ze2LuC/blYMbgg3kMRlmJSy dCyyY70beYXLO81slvZP/qOVE1jTwx/lc7UppJkxg+xPoU2cwN6i4qlZ2aoDU7/Wox2FBXBc6 WYV8VyrmsXKF/mUBBQBuUfVv7QaAlVfxW3O9kqJlIdQZWInxBPbo37IrWBodT0qQu5R8MxkCd m6sVbaZ0TjYmeppqUoRjn2ZHe2GRq/7NPY9LENhUb4Pa3HYBSTMdwMYhEzMdxMS6dLGyq17oK /1Iw5qhDgdLdH/lO3VYVy9w2rnNDTRBxAbczRim9Y5pWZYxrcpSOwXX7DH4tLbl1frID45CnI ZbWSzXLG/geIWOgnqYyBXD+XwVYsKrY99RCU1ug+t+5mx3bSOmtrcJYyTpfsSjM9qzzz8Cih0 DYA28CjuzeH6UrqVnvlnq3Qcw79pLliRz2E03PI65ksC9haeJBg3ZKGqORjfQkZpJYy9Dvo5Y HBlojIR//qQ7bgvIO9GcDFlg67i0SvJeln3NtUgtzehMzVPSRcAbOpGfZ9KR0v8oqMrRjzs7h vErI75reeyeXJjnJWMEm6HDzKCmPGi8L78ANIqFgMiB9p6Gyw69MJgzbCjWPcFrbHPdrgcd7S iqNaptFsEuFFuvPVBxtsesvqgy1aaWooHFaw2s2+8T/ExhUO4QbRaMsuJeRGv1V1B5OQHU9qf xuhaYvn0iodfAAdAEN9KSzKkWVXE22evmsIFO9kmL/ZJ0WUepICkTnb2ctb2bc97/TiGf/Au0 LyXuXx9iX+xGWMPdg/e3kRODodNmPJDOm13AIPHjVcHEsrlJ4L/+5qrGj01bvRk5Ly4l+r1NN rG+8l10gi3SURnjs9kl8jmAjveykxgIZ5TbGbJheqlSxyU1D4jXN2YA0Igw9eo7XTpxNP9LOl zf19OEb4N6yxqudRlFNPXbRbc4sX1rrWvSVFo7BA4sPCuIU8wJY9xO63SNHM=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/9D2xkSvnfjRnEFC6UFwWg0EolGc>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
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: Mon, 20 Jan 2020 20:55:25 -0000

On 20.01.2020 21:00, David R. Oran wrote:
> I have a new Internet Draft to write, so I decided to bite the bullet
> and do it in V3. Rather than write in V2 and try the converter, I
> started out right away with V3 syntax. I didn=E2=80=99t get very far. I =
tried
> both the most recent xml2rfc by installing it on my machine, and the web
> tool and got identical errors.
>
> If I follow the described syntax in RFC7991, the RFC Editor FAQ in
> https://ftp.ripe.net/rfc/v3test/FAQ-2019-02.html and the example in
> draft-hoffman-rfcexamples-latest as below:
>
> |<?xml version=3D"1.0" encoding=3D"US-ASCII"?> <!DOCTYPE rfc SYSTEM
> 'rfc2629.dtd'> <?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' =
?>
> <?rfc strict=3D"yes" ?> <?rfc toc=3D"yes"?> <?rfc tocdepth=3D"4"?> <?rfc
> symrefs=3D"yes" ?> <?rfc sortrefs=3D"yes" ?> <?rfc compact=3D"yes" ?> <?=
rfc
> subcompact=3D"no" ?> <rfc version=3D=E2=80=983=E2=80=99 ipr=3D'trust2009=
02' category=3D'exp'
> submissionType=3D'IRTF' docName=3D'draft-oran-icnrg-reflexive-forwarding=
-00'
> xml:lang=3D'en' xmlns:xi=3D"https://www.w3.org/2001/XInclude"> <front>
> <seriesInfo name=3D'Internet-Draft'
> value=3D'draft-oran-icnrg-reflexive-forwarding-00'/> <title abbrev=3D'IC=
N
> Reflexive Forwarding'>Reflexive Forwarding for CCNx and NDN Protocols
> </title> |
>
> I get
>
> |% xml2rfc draft-oran-icnrg-reflexive-forwarding.xml Incompatible schema
> information: found "rfc2629.dtd" in <DOCTYPE> of a version 3 file. |
> ...

That message is indeed not very helpful. First of all, it doesn't say
what to do; and then, it *assumes* what the contents of rfc2629.dtd
might be, without really knowing.

FWIW, you don't need a DTD declaration; just get rid of it (the same was
already true in v2 times).

Best regards, Julian


From nobody Mon Jan 20 13:04:12 2020
Return-Path: <daveoran@orandom.net>
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 BF69D12087E for <xml2rfc@ietfa.amsl.com>; Mon, 20 Jan 2020 13:04:06 -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, HTML_MESSAGE=0.001, 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 dW64hpJXRzUD for <xml2rfc@ietfa.amsl.com>; Mon, 20 Jan 2020 13:04:02 -0800 (PST)
Received: from spark.crystalorb.net (spark.crystalorb.net [IPv6:2607:fca8:1530::c]) (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 2A48612086D for <xml2rfc@ietf.org>; Mon, 20 Jan 2020 13:04:02 -0800 (PST)
Received: from [192.168.15.102] ([IPv6:2601:184:407f:80ce:349f:2df:2bdc:d2ac]) (authenticated bits=0) by spark.crystalorb.net (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id 00KL3wLa011359 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Mon, 20 Jan 2020 13:04:00 -0800
From: "David R. Oran" <daveoran@orandom.net>
To: "Henrik Levkowetz" <henrik@levkowetz.com>
Cc: xml2rfc@ietf.org
Date: Mon, 20 Jan 2020 16:03:53 -0500
X-Mailer: MailMate (1.13.1r5676)
Message-ID: <DA4F22F5-5A43-4671-B69B-EDF61F976623@orandom.net>
In-Reply-To: <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com>
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net> <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_B32868AA-F20E-4EBD-B003-00A8CA3679EF_="; micalg=pgp-sha1; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/J6vONRo41Ek5zmHA96T_b_Rc_ZM>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
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: Mon, 20 Jan 2020 21:04:12 -0000

This is an OpenPGP/MIME signed message (RFC 3156 and 4880).

--=_MailMate_B32868AA-F20E-4EBD-B003-00A8CA3679EF_=
Content-Type: multipart/alternative;
 boundary="=_MailMate_2E0948DE-6FF8-48D0-9343-E234ED05BEDC_="


--=_MailMate_2E0948DE-6FF8-48D0-9343-E234ED05BEDC_=
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On 20 Jan 2020, at 15:10, Henrik Levkowetz wrote:

> Hi David,
>
> You should simply remove "<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>" if your
> <rfc/> element contains the "version=3D'3'" attribute.
>
If I do that xml2rfc crashes (both the one on my machine and the web tool=
:

xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
Traceback (most recent call last):
  File "/usr/local/bin/xml2rfc", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python2.7/site-packages/xml2rfc/run.py", line 612,=
 in main
    xmlrfc =3D parser.parse(remove_comments=3DFalse, quiet=3DTrue, add_xm=
lns=3DTrue)
  File "/usr/local/lib/python2.7/site-packages/xml2rfc/parser.py", line 5=
48, in parse
    for action, element in context:
  File "src/lxml/iterparse.pxi", line 208, in lxml.etree.iterparse.__next=
__ (src/lxml/lxml.etree.c:148588)
  File "<string>", line 22
lxml.etree.XMLSyntaxError: Attribute xmlns:xi redefined, line 22, column =
59

> Regards,
>
> 	Henrik
>
> On 2020-01-20 21:00, David R. Oran wrote:
>> I have a new Internet Draft to write, so I decided to bite the bullet
>> and do it in V3. Rather than write in V2 and try the converter, I
>> started out right away with V3 syntax. I didn=E2=80=99t get very far. =
I tried
>> both the most recent xml2rfc by installing it on my machine, and the w=
eb
>> tool and got identical errors.
>>
>> If I follow the described syntax in RFC7991, the RFC Editor FAQ in
>> https://ftp.ripe.net/rfc/v3test/FAQ-2019-02.html and the example in
>> draft-hoffman-rfcexamples-latest as below:
>>
>> 	<?xml version=3D"1.0" encoding=3D"US-ASCII"?>
>> 	<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>
>>
>> 	<?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?>
>> 	<?rfc strict=3D"yes" ?>
>> 	<?rfc toc=3D"yes"?>
>> 	<?rfc tocdepth=3D"4"?>
>> 	<?rfc symrefs=3D"yes" ?>
>> 	<?rfc sortrefs=3D"yes" ?>
>> 	<?rfc compact=3D"yes" ?>
>> 	<?rfc subcompact=3D"no" ?>
>> 	<rfc
>> 		version=3D=E2=80=983=E2=80=99
>> 		ipr=3D'trust200902'
>> 		category=3D'exp'
>> 		submissionType=3D'IRTF'
>> 		docName=3D'draft-oran-icnrg-reflexive-forwarding-00'
>> 		xml:lang=3D'en' xmlns:xi=3D"https://www.w3.org/2001/XInclude">
>>
>> 	<front>
>> 		<seriesInfo name=3D'Internet-Draft'
>> value=3D'draft-oran-icnrg-reflexive-forwarding-00'/>
>> 	    <title abbrev=3D'ICN Reflexive Forwarding'>Reflexive Forwarding f=
or
>> CCNx and NDN Protocols
>> 	    </title>
>>
>>
>>
>> I get
>>
>> 	% xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
>> 	Incompatible schema information: found "rfc2629.dtd" in <DOCTYPE> of =
a
>> version 3 file.
>>
>> If I leave off the =E2=80=9Cversion=3D=E2=80=983=E2=80=99, as below
>>
>> 	<?xml version=3D"1.0" encoding=3D"US-ASCII"?>
>> 	<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>
>> 	<?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?>
>> 	<?rfc strict=3D"yes" ?>
>> 	<?rfc toc=3D"yes"?>
>> 	<?rfc tocdepth=3D"4"?>
>> 	<?rfc symrefs=3D"yes" ?>
>> 	<?rfc sortrefs=3D"yes" ?>
>> 	<?rfc compact=3D"yes" ?>
>> 	<?rfc subcompact=3D"no" ?>
>>
>> 	<rfc
>> 		ipr=3D'trust200902'
>> 		category=3D'exp'
>> 		submissionType=3D'IRTF'
>> 		docName=3D'draft-oran-icnrg-reflexive-forwarding-00'
>> 		xml:lang=3D'en' xmlns:xi=3D"https://www.w3.org/2001/XInclude">
>>
>> 	<front>
>> 		<seriesInfo name=3D'Internet-Draft'
>> value=3D'draft-oran-icnrg-reflexive-forwarding-00'/>
>> 	    <title abbrev=3D'ICN Reflexive Forwarding'>Reflexive Forwarding f=
or
>> CCNx and NDN Protocols
>> 	    </title>
>>
>> I get:
>>
>> 		xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
>> 		Error: Unable to validate the XML document:
>> draft-oran-icnrg-reflexive-forwarding.xml
>> 		 <string>: Line 23: No declaration for attribute xmlns:xi of element=

>> rfc
>> 		 <string>: Line 25: Element front content does not follow the DTD,
>> expecting (title , author+ , date , area* , workgroup* , keyword* ,
>> abstract? , note*), got (seriesInfo title author author date area
>> workgroup keyword keyword abstract )
>> 		 <string>: Line 81: Element section content does not follow the DTD,=

>> expecting ((t | figure | texttable | iref)* , section*), got (name t )=

>> 		 <string>: Line 81: Element section does not carry attribute title
>> 		 <string>: Line 81: No declaration for element name
>> 		 <string>: Line 85: Element section content does not follow the DTD,=

>> expecting ((t | figure | texttable | iref)* , section*), got (name t )=

>> 		 <string>: Line 85: Element section does not carry attribute title
>> 		 <string>: Line 85: No declaration for element name
>> 		 <string>: Line 94: Element section content does not follow the DTD,=

>> expecting ((t | figure | texttable | iref)* , section*), got (name t
>> section section )
>> 		 <string>: Line 94: Element section does not carry attribute title
>> 		 <string>: Line 94: No declaration for element name
>> 		 <string>: Line 97: Element section content does not follow the DTD,=

>> expecting ((t | figure | texttable | iref)* , section*), got (name t
>> table )
>> 		 <string>: Line 97: Element section does not carry attribute title
>> 		 <string>: Line 97: No declaration for element name
>> 		 <string>: Line 98: No declaration for attribute keepWithNext of
>> element t
>> 		 <string>: Line 99: No declaration for element table
>> 		 <string>: Line 99: No declaration for attribute title of element
>> table
>>
>> Clue bat please?
>>
>> DaveO
>>
>>
>>
>> _______________________________________________
>> xml2rfc mailing list
>> xml2rfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>

DaveO

--=_MailMate_2E0948DE-6FF8-48D0-9343-E234ED05BEDC_=
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">On 20 Jan 2020, at 15:10, Henrik Levkowetz wrote:</p>

</div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir=3D"auto">H=
i David,<br>
<br>
You should simply remove "&lt;!DOCTYPE rfc SYSTEM 'rfc2629.dtd'&gt;" if y=
our<br>
&lt;rfc/&gt; element contains the "version=3D'3'" attribute.<br>
</p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">If I do that xml2rfc crashes (both the one on my machine =
and the web tool:</p>

<p dir=3D"auto">xml2rfc draft-oran-icnrg-reflexive-forwarding.xml<br>
Traceback (most recent call last):<br>
  File "/usr/local/bin/xml2rfc", line 8, in &lt;module&gt;<br>
    sys.exit(main())<br>
  File "/usr/local/lib/python2.7/site-packages/xml2rfc/run.py", line 612,=
 in main<br>
    xmlrfc =3D parser.parse(remove_comments=3DFalse, quiet=3DTrue, add_xm=
lns=3DTrue)<br>
  File "/usr/local/lib/python2.7/site-packages/xml2rfc/parser.py", line 5=
48, in parse<br>
    for action, element in context:<br>
  File "src/lxml/iterparse.pxi", line 208, in lxml.etree.iterparse.<stron=
g>next</strong> (src/lxml/lxml.etree.c:148588)<br>
  File "&lt;string&gt;", line 22<br>
lxml.etree.XMLSyntaxError: Attribute xmlns:xi redefined, line 22, column =
59</p>

</div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir=3D"auto">R=
egards,<br>
<br>
	Henrik<br>
<br>
On 2020-01-20 21:00, David R. Oran wrote:</p>
<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 5=
px; padding-left:5px; border-left-color:#999"><p dir=3D"auto">I have a ne=
w Internet Draft to write, so I decided to bite the bullet<br>
and do it in V3. Rather than write in V2 and try the converter, I<br>
started out right away with V3 syntax. I didn=E2=80=99t get very far. I t=
ried<br>
both the most recent xml2rfc by installing it on my machine, and the web<=
br>
tool and got identical errors.<br>
<br>
If I follow the described syntax in RFC7991, the RFC Editor FAQ in<br>
<a href=3D"https://ftp.ripe.net/rfc/v3test/FAQ-2019-02.html" style=3D"col=
or:#999">https://ftp.ripe.net/rfc/v3test/FAQ-2019-02.html</a> and the exa=
mple in<br>
draft-hoffman-rfcexamples-latest as below:<br>
<br>
	&lt;?xml version=3D"1.0" encoding=3D"US-ASCII"?&gt;<br>
	&lt;!DOCTYPE rfc SYSTEM 'rfc2629.dtd'&gt;<br>
<br>
	&lt;?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?&gt;<br>
	&lt;?rfc strict=3D"yes" ?&gt;<br>
	&lt;?rfc toc=3D"yes"?&gt;<br>
	&lt;?rfc tocdepth=3D"4"?&gt;<br>
	&lt;?rfc symrefs=3D"yes" ?&gt;<br>
	&lt;?rfc sortrefs=3D"yes" ?&gt;<br>
	&lt;?rfc compact=3D"yes" ?&gt;<br>
	&lt;?rfc subcompact=3D"no" ?&gt;<br>
	&lt;rfc<br>
		version=3D=E2=80=983=E2=80=99<br>
		ipr=3D'trust200902'<br>
		category=3D'exp'<br>
		submissionType=3D'IRTF'<br>
		docName=3D'draft-oran-icnrg-reflexive-forwarding-00'<br>
		xml:lang=3D'en' xmlns:xi=3D"<a href=3D"https://www.w3.org/2001/XInclude=
" style=3D"color:#999">https://www.w3.org/2001/XInclude</a>"&gt;<br>
<br>
	&lt;front&gt;<br>
		&lt;seriesInfo name=3D'Internet-Draft'<br>
value=3D'draft-oran-icnrg-reflexive-forwarding-00'/&gt;<br>
	    &lt;title abbrev=3D'ICN Reflexive Forwarding'&gt;Reflexive Forwardin=
g for<br>
CCNx and NDN Protocols<br>
	    &lt;/title&gt;<br>
<br>
<br>
<br>
I get<br>
<br>
	% xml2rfc draft-oran-icnrg-reflexive-forwarding.xml<br>
	Incompatible schema information: found "rfc2629.dtd" in &lt;DOCTYPE&gt; =
of a<br>
version 3 file.<br>
<br>
If I leave off the =E2=80=9Cversion=3D=E2=80=983=E2=80=99, as below<br>
<br>
	&lt;?xml version=3D"1.0" encoding=3D"US-ASCII"?&gt;<br>
	&lt;!DOCTYPE rfc SYSTEM 'rfc2629.dtd'&gt;<br>
	&lt;?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?&gt;<br>
	&lt;?rfc strict=3D"yes" ?&gt;<br>
	&lt;?rfc toc=3D"yes"?&gt;<br>
	&lt;?rfc tocdepth=3D"4"?&gt;<br>
	&lt;?rfc symrefs=3D"yes" ?&gt;<br>
	&lt;?rfc sortrefs=3D"yes" ?&gt;<br>
	&lt;?rfc compact=3D"yes" ?&gt;<br>
	&lt;?rfc subcompact=3D"no" ?&gt;<br>
<br>
	&lt;rfc<br>
		ipr=3D'trust200902'<br>
		category=3D'exp'<br>
		submissionType=3D'IRTF'<br>
		docName=3D'draft-oran-icnrg-reflexive-forwarding-00'<br>
		xml:lang=3D'en' xmlns:xi=3D"<a href=3D"https://www.w3.org/2001/XInclude=
" style=3D"color:#999">https://www.w3.org/2001/XInclude</a>"&gt;<br>
<br>
	&lt;front&gt;<br>
		&lt;seriesInfo name=3D'Internet-Draft'<br>
value=3D'draft-oran-icnrg-reflexive-forwarding-00'/&gt;<br>
	    &lt;title abbrev=3D'ICN Reflexive Forwarding'&gt;Reflexive Forwardin=
g for<br>
CCNx and NDN Protocols<br>
	    &lt;/title&gt;<br>
<br>
I get:<br>
<br>
		xml2rfc draft-oran-icnrg-reflexive-forwarding.xml<br>
		Error: Unable to validate the XML document:<br>
draft-oran-icnrg-reflexive-forwarding.xml<br>
		 &lt;string&gt;: Line 23: No declaration for attribute xmlns:xi of elem=
ent<br>
rfc<br>
		 &lt;string&gt;: Line 25: Element front content does not follow the DTD=
,<br>
expecting (title , author+ , date , area* , workgroup* , keyword* ,<br>
abstract? , note*), got (seriesInfo title author author date area<br>
workgroup keyword keyword abstract )<br>
		 &lt;string&gt;: Line 81: Element section content does not follow the D=
TD,<br>
expecting ((t | figure | texttable | iref)* , section*), got (name t )<br=
>
		 &lt;string&gt;: Line 81: Element section does not carry attribute titl=
e<br>
		 &lt;string&gt;: Line 81: No declaration for element name<br>
		 &lt;string&gt;: Line 85: Element section content does not follow the D=
TD,<br>
expecting ((t | figure | texttable | iref)* , section*), got (name t )<br=
>
		 &lt;string&gt;: Line 85: Element section does not carry attribute titl=
e<br>
		 &lt;string&gt;: Line 85: No declaration for element name<br>
		 &lt;string&gt;: Line 94: Element section content does not follow the D=
TD,<br>
expecting ((t | figure | texttable | iref)* , section*), got (name t<br>
section section )<br>
		 &lt;string&gt;: Line 94: Element section does not carry attribute titl=
e<br>
		 &lt;string&gt;: Line 94: No declaration for element name<br>
		 &lt;string&gt;: Line 97: Element section content does not follow the D=
TD,<br>
expecting ((t | figure | texttable | iref)* , section*), got (name t<br>
table )<br>
		 &lt;string&gt;: Line 97: Element section does not carry attribute titl=
e<br>
		 &lt;string&gt;: Line 97: No declaration for element name<br>
		 &lt;string&gt;: Line 98: No declaration for attribute keepWithNext of<=
br>
element t<br>
		 &lt;string&gt;: Line 99: No declaration for element table<br>
		 &lt;string&gt;: Line 99: No declaration for attribute title of element=
<br>
table<br>
<br>
Clue bat please?<br>
<br>
DaveO<br>
<br>
<br>
<br>
_______________________________________________<br>
xml2rfc mailing list<br>
xml2rfc@ietf.org<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/xml2rfc" style=3D"color:=
#999">https://www.ietf.org/mailman/listinfo/xml2rfc</a><br>
</p>
</blockquote></blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">DaveO</p>
</div>
</div>
</body>
</html>

--=_MailMate_2E0948DE-6FF8-48D0-9343-E234ED05BEDC_=--

--=_MailMate_B32868AA-F20E-4EBD-B003-00A8CA3679EF_=
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename=signature.asc
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iQJJBAEBAgAzFiEEroJBCc9z/EJK1xs/eu0uvThCv/AFAl4mFbkVHGRhdmVvcmFu
QG9yYW5kb20ubmV0AAoJEHrtLr04Qr/wwBcP/1IfBmEHAAKZaTNREiMCPFOFrhKP
ZknTXpP4pXsH8y5sd/wU9ClxpyrENWIeXjMyNkeTBWHcPoQAbZhwAjpqw4455NNK
/THQoUYQQxEOLGA3aqKOPdfm7VIjHgUR+5ooBsdgtsfGDLmCp71Mo1fLR5VBOrb7
8usNmcLjMwawXjQEec2uIHiggo5DFZtchDgkAPhMzJvMKNttHCGKi1FfEy5oCV0G
85oP5Fcl51LAW5l8mA8oWXciEY1tMQv1Sxqze/lNSiZ36iyE3Wr0xcfgk6fFTHoU
jJVdxTfc7eFuLc3+wtXM69Pjc52KHvx3gyhfYWvOexADXq7ku809WhoGei8Is4Dr
n0y+zCo+AwKyke9Ku9WdSE3FRSklbAhkfMpbUKMD5Jo69YnAyhGIf5ZoXCywY2rP
ZBfvvSNoi5E0/ZufwQDGm6weGcF38/ozkweKlcnrc7dsQMmVYKyAFikgJRPOvaRv
P01uHowr12qcQtM/D7Xf9GYeGj5jYiasBreW/cufdW8LGlXXr+6MswaXyGu7x6bW
5Ud7Jdb8Byn5UGiCvry9QaZ5WAMFONTuDixF9IGO0bnEfuh+Q3cTXIMQ75ATUQBk
XROOHa/4rQzsotR/cE/6sYjLB4L+33w7W9XZfUr66Sxdi63z4+6lHxXdOzCg4oBA
2GQBpekE5HVzkGuW
=B2x+
-----END PGP SIGNATURE-----

--=_MailMate_B32868AA-F20E-4EBD-B003-00A8CA3679EF_=--


From nobody Mon Jan 20 13:25:34 2020
Return-Path: <henrik@levkowetz.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 2F145120232 for <xml2rfc@ietfa.amsl.com>; Mon, 20 Jan 2020 13:25:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 nUV3qo684Km2 for <xml2rfc@ietfa.amsl.com>; Mon, 20 Jan 2020 13:25:26 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 904CD12011D for <xml2rfc@ietf.org>; Mon, 20 Jan 2020 13:25:26 -0800 (PST)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:59795 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1iteY0-00012b-TM; Mon, 20 Jan 2020 13:25:26 -0800
To: "David R. Oran" <daveoran@orandom.net>
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net> <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com> <DA4F22F5-5A43-4671-B69B-EDF61F976623@orandom.net>
Cc: xml2rfc@ietf.org
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <61971d80-1c1e-bdf7-a986-0cfe9de157e6@levkowetz.com>
Date: Mon, 20 Jan 2020 22:25:17 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <DA4F22F5-5A43-4671-B69B-EDF61F976623@orandom.net>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Fi4T6Cd3IOOLdrkHvG6EeVTod1qPgkPsI"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: xml2rfc@ietf.org, daveoran@orandom.net
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/jtgP7AQJNLecMLQdmBVAbv6qWiU>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
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: Mon, 20 Jan 2020 21:25:32 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--Fi4T6Cd3IOOLdrkHvG6EeVTod1qPgkPsI
Content-Type: multipart/mixed; boundary="OCvIRT8FBwNavo7mfxpESI07gtGF8KhEu";
 protected-headers="v1"
From: Henrik Levkowetz <henrik@levkowetz.com>
To: "David R. Oran" <daveoran@orandom.net>
Cc: xml2rfc@ietf.org
Message-ID: <61971d80-1c1e-bdf7-a986-0cfe9de157e6@levkowetz.com>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net>
 <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com>
 <DA4F22F5-5A43-4671-B69B-EDF61F976623@orandom.net>
In-Reply-To: <DA4F22F5-5A43-4671-B69B-EDF61F976623@orandom.net>

--OCvIRT8FBwNavo7mfxpESI07gtGF8KhEu
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi David,

On 2020-01-20 22:03, David R. Oran wrote:
> On 20 Jan 2020, at 15:10, Henrik Levkowetz wrote:
>=20
>> Hi David,
>>
>> You should simply remove "<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>" if your=

>> <rfc/> element contains the "version=3D'3'" attribute.
>>
> If I do that xml2rfc crashes (both the one on my machine and the web to=
ol:

Oh, wow.  Ok, I'll fix that in the next release.  Could you send the full=

xml file, please?  It's not obvious from your snippet where the superfluo=
us
other definition of xmlns:xi is.

Now, you say that instead of trying the converter, you stared out right
away with v3 syntax, but neither the DOCTYPE above, nor the <?rfc ... ?>
PIs visible in your snippet are appropriate for a v3 document.  Did you
grab a v2 template to start with?  I think really going to lead you into
a number of problems if you start with a v2 template and declare it to be=

v3.

Using the v2v3 converter on a v2 document, even on a v2 template, on the
other hand, should give you a proper v3 starting point, without the issue=
s
you've run into so far.


Regards,

	Henrik

>=20
> xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
> Traceback (most recent call last):
>   File "/usr/local/bin/xml2rfc", line 8, in <module>
>     sys.exit(main())
>   File "/usr/local/lib/python2.7/site-packages/xml2rfc/run.py", line 61=
2, in main
>     xmlrfc =3D parser.parse(remove_comments=3DFalse, quiet=3DTrue, add_=
xmlns=3DTrue)
>   File "/usr/local/lib/python2.7/site-packages/xml2rfc/parser.py", line=
 548, in parse
>     for action, element in context:
>   File "src/lxml/iterparse.pxi", line 208, in lxml.etree.iterparse.__ne=
xt__ (src/lxml/lxml.etree.c:148588)
>   File "<string>", line 22
> lxml.etree.XMLSyntaxError: Attribute xmlns:xi redefined, line 22, colum=
n 59
>=20
>> Regards,
>>
>> 	Henrik
>>
>> On 2020-01-20 21:00, David R. Oran wrote:
>>> I have a new Internet Draft to write, so I decided to bite the bullet=

>>> and do it in V3. Rather than write in V2 and try the converter, I
>>> started out right away with V3 syntax. I didn=E2=80=99t get very far.=
 I tried
>>> both the most recent xml2rfc by installing it on my machine, and the =
web
>>> tool and got identical errors.
>>>
>>> If I follow the described syntax in RFC7991, the RFC Editor FAQ in
>>> https://ftp.ripe.net/rfc/v3test/FAQ-2019-02.html and the example in
>>> draft-hoffman-rfcexamples-latest as below:
>>>
>>> 	<?xml version=3D"1.0" encoding=3D"US-ASCII"?>
>>> 	<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>
>>>
>>> 	<?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?>
>>> 	<?rfc strict=3D"yes" ?>
>>> 	<?rfc toc=3D"yes"?>
>>> 	<?rfc tocdepth=3D"4"?>
>>> 	<?rfc symrefs=3D"yes" ?>
>>> 	<?rfc sortrefs=3D"yes" ?>
>>> 	<?rfc compact=3D"yes" ?>
>>> 	<?rfc subcompact=3D"no" ?>
>>> 	<rfc
>>> 		version=3D=E2=80=983=E2=80=99
>>> 		ipr=3D'trust200902'
>>> 		category=3D'exp'
>>> 		submissionType=3D'IRTF'
>>> 		docName=3D'draft-oran-icnrg-reflexive-forwarding-00'
>>> 		xml:lang=3D'en' xmlns:xi=3D"https://www.w3.org/2001/XInclude">
>>>
>>> 	<front>
>>> 		<seriesInfo name=3D'Internet-Draft'
>>> value=3D'draft-oran-icnrg-reflexive-forwarding-00'/>
>>> 	    <title abbrev=3D'ICN Reflexive Forwarding'>Reflexive Forwarding =
for
>>> CCNx and NDN Protocols
>>> 	    </title>
>>>
>>>
>>>
>>> I get
>>>
>>> 	% xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
>>> 	Incompatible schema information: found "rfc2629.dtd" in <DOCTYPE> of=
 a
>>> version 3 file.
>>>
>>> If I leave off the =E2=80=9Cversion=3D=E2=80=983=E2=80=99, as below
>>>
>>> 	<?xml version=3D"1.0" encoding=3D"US-ASCII"?>
>>> 	<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>
>>> 	<?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?>
>>> 	<?rfc strict=3D"yes" ?>
>>> 	<?rfc toc=3D"yes"?>
>>> 	<?rfc tocdepth=3D"4"?>
>>> 	<?rfc symrefs=3D"yes" ?>
>>> 	<?rfc sortrefs=3D"yes" ?>
>>> 	<?rfc compact=3D"yes" ?>
>>> 	<?rfc subcompact=3D"no" ?>
>>>
>>> 	<rfc
>>> 		ipr=3D'trust200902'
>>> 		category=3D'exp'
>>> 		submissionType=3D'IRTF'
>>> 		docName=3D'draft-oran-icnrg-reflexive-forwarding-00'
>>> 		xml:lang=3D'en' xmlns:xi=3D"https://www.w3.org/2001/XInclude">
>>>
>>> 	<front>
>>> 		<seriesInfo name=3D'Internet-Draft'
>>> value=3D'draft-oran-icnrg-reflexive-forwarding-00'/>
>>> 	    <title abbrev=3D'ICN Reflexive Forwarding'>Reflexive Forwarding =
for
>>> CCNx and NDN Protocols
>>> 	    </title>
>>>
>>> I get:
>>>
>>> 		xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
>>> 		Error: Unable to validate the XML document:
>>> draft-oran-icnrg-reflexive-forwarding.xml
>>> 		 <string>: Line 23: No declaration for attribute xmlns:xi of elemen=
t
>>> rfc
>>> 		 <string>: Line 25: Element front content does not follow the DTD,
>>> expecting (title , author+ , date , area* , workgroup* , keyword* ,
>>> abstract? , note*), got (seriesInfo title author author date area
>>> workgroup keyword keyword abstract )
>>> 		 <string>: Line 81: Element section content does not follow the DTD=
,
>>> expecting ((t | figure | texttable | iref)* , section*), got (name t =
)
>>> 		 <string>: Line 81: Element section does not carry attribute title
>>> 		 <string>: Line 81: No declaration for element name
>>> 		 <string>: Line 85: Element section content does not follow the DTD=
,
>>> expecting ((t | figure | texttable | iref)* , section*), got (name t =
)
>>> 		 <string>: Line 85: Element section does not carry attribute title
>>> 		 <string>: Line 85: No declaration for element name
>>> 		 <string>: Line 94: Element section content does not follow the DTD=
,
>>> expecting ((t | figure | texttable | iref)* , section*), got (name t
>>> section section )
>>> 		 <string>: Line 94: Element section does not carry attribute title
>>> 		 <string>: Line 94: No declaration for element name
>>> 		 <string>: Line 97: Element section content does not follow the DTD=
,
>>> expecting ((t | figure | texttable | iref)* , section*), got (name t
>>> table )
>>> 		 <string>: Line 97: Element section does not carry attribute title
>>> 		 <string>: Line 97: No declaration for element name
>>> 		 <string>: Line 98: No declaration for attribute keepWithNext of
>>> element t
>>> 		 <string>: Line 99: No declaration for element table
>>> 		 <string>: Line 99: No declaration for attribute title of element
>>> table
>>>
>>> Clue bat please?
>>>
>>> DaveO
>>>
>>>
>>>
>>> _______________________________________________
>>> xml2rfc mailing list
>>> xml2rfc@ietf.org
>>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>>
>=20
> DaveO
>=20


--OCvIRT8FBwNavo7mfxpESI07gtGF8KhEu--

--Fi4T6Cd3IOOLdrkHvG6EeVTod1qPgkPsI
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl4mGr4ACgkQTptXS4+7
FxpCBw//ZyQbfY22BvA440Szogouu2KKAqAISO+/oyfjAARNwwSrla9GJqk5UpjD
RY7BTgBLsW+BLoJ3w4n0gp1uAaWj24mhRErug9l1VyDbjzCI6P4TqyF/Cl+H5sgC
dCRu7i4tTas5K7zg0d5SCq+droLnOXD8vLP4BF7RlJvs3gsZh1HsEDkvUnTj4B7L
Vi7QpvgW4YSuKML1u4MyhUQFy+rdWO0u54Uk74+eXO1s5IcK/W14GUpmqoGc69E1
6GJbbR7Y7wY7idc8/PP4Tl2tGc1GJB0PjK1EP1lCT1/8NL/5YlKi60hMWsjtFP9B
sEDMg9mmKifKe7LnvCsMORwrLpAs3GOlG+If9THWd+K9WzXAmntqHbT7jwlOcvJi
h8CWtrcZz8u2zg23K4FioBbuWYsZMmtSwbh1YoKkJE6FSWvZmqJhbjqCF+z8E7FB
Bs4Olibm9gNYsCxJ7z1avJol++7srAXU8mHXuJIUxGcHkMNuusK/qrdTLidOKfiV
l2HrhCVkWZyeYZ/kyb0p9bcd1cvMI3MHhZuOZjgYBLGJx3sPN5Luij4mujf4KaYr
qDfyxAlF8CDo0gJtdf2rO0S83hmfB1hxQdgtL5n1uQ9U/zf36ERcOWQO4yg0/gZC
2xK19gbgwOejqKivxBLw3B8aLyqT9OIMN7xRHGheMeBjumaI534=
=KROR
-----END PGP SIGNATURE-----

--Fi4T6Cd3IOOLdrkHvG6EeVTod1qPgkPsI--


From nobody Mon Jan 20 21:51:18 2020
Return-Path: <daveoran@orandom.net>
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 A044012006E for <xml2rfc@ietfa.amsl.com>; Mon, 20 Jan 2020 21:51:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 LwzspfyzadeM for <xml2rfc@ietfa.amsl.com>; Mon, 20 Jan 2020 21:51:13 -0800 (PST)
Received: from spark.crystalorb.net (spark.crystalorb.net [IPv6:2607:fca8:1530::c]) (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 61DBA120052 for <xml2rfc@ietf.org>; Mon, 20 Jan 2020 21:51:13 -0800 (PST)
Received: from [192.168.15.102] ([IPv6:2601:184:407f:80ce:349f:2df:2bdc:d2ac]) (authenticated bits=0) by spark.crystalorb.net (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id 00L5p7lO025032 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Mon, 20 Jan 2020 21:51:09 -0800
From: "David R. Oran" <daveoran@orandom.net>
To: "Henrik Levkowetz" <henrik@levkowetz.com>
Cc: xml2rfc@ietf.org
Date: Tue, 21 Jan 2020 00:51:01 -0500
X-Mailer: MailMate (1.13.1r5676)
Message-ID: <A6C1B0DF-EAE0-46DC-9539-F56A3192E336@orandom.net>
In-Reply-To: <647a593e-8104-0a59-bd0b-fb377f49201e@levkowetz.com>
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net> <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com> <DA4F22F5-5A43-4671-B69B-EDF61F976623@orandom.net> <61971d80-1c1e-bdf7-a986-0cfe9de157e6@levkowetz.com> <6C8FDE4E-88F8-4862-A9CC-3D1E9B0DCD4C@orandom.net> <fe468ed5-3d9b-88b2-8403-f8482bb1f55b@levkowetz.com> <647a593e-8104-0a59-bd0b-fb377f49201e@levkowetz.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_1887897D-3C6E-44B0-B22F-C9BE523CB48B_="; micalg=pgp-sha1; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/3O0WP5AwDzUJCOaCEitiH7kBEPo>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
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: Tue, 21 Jan 2020 05:51:17 -0000

This is an OpenPGP/MIME signed message (RFC 3156 and 4880).

--=_MailMate_1887897D-3C6E-44B0-B22F-C9BE523CB48B_=
Content-Type: multipart/alternative;
 boundary="=_MailMate_91C00C75-57F8-4598-A695-EF6345034D44_="


--=_MailMate_91C00C75-57F8-4598-A695-EF6345034D44_=
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks a ton for the help. I puzzled around some more in the FAQ and RFC7=
991, getting rid of suspicious V2-ish stuff that used to be adorning all =
my draft source files and replacing the essentials with the right V3 cons=
tructs. However, among those was not the xmlns:ni, which I had copied fro=
m one of the examples in draft-hoffman-rfcexamples. Once that was gone th=
e crash disappeared.

One unsolicited piece of advice is that in addition to the FAQ and RFC799=
1 itself, some templates in native V3 for people to start from would have=
 saved me the pain you see in this thread. The example in Paul Hoffman=E2=
=80=99s draft (which I found googling =E2=80=9Cxml2rfc v3 examples=E2=80=9D=
 of course) was generated using the converter and wound up being extremel=
y misleading for a =E2=80=9Cnative=E2=80=9D V3 source file.

Best, DaveO.

P.S. I did get another crash when I put my own <date> element in the <fro=
nt> element as per =E2=80=9C<date month=3D'January' year=3D'2020' /> When=
 I let the converter insert the date in the output itself, no problem.


	xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
	draft-oran-icnrg-reflexive-forwarding.xml(63): Warning: The document dat=
e (2020-01-01) is more than 3 days away from today's date
	Traceback (most recent call last):
	  File "/usr/local/bin/xml2rfc", line 8, in <module>
	    sys.exit(main())
	  File "/usr/local/lib/python2.7/site-packages/xml2rfc/run.py", line 620=
, in main
	    xmlrfc.tree =3D prep.prep()
	  File "/usr/local/lib/python2.7/site-packages/xml2rfc/writers/preptool.=
py", line 342, in prep
	    func(e, e.getparent())
	  File "/usr/local/lib/python2.7/site-packages/xml2rfc/writers/preptool.=
py", line 1123, in boilerplate_insert_status_of_memo
	    exp =3D datetime.date(year=3Dyear, month=3Dmonth, day=3Dday) + datet=
ime.timedelta(days=3D185)
	TypeError: an integer is required


On 20 Jan 2020, at 18:20, Henrik Levkowetz wrote:

> Hi again David,
>
> The issue is triggered by the code trying to insert the XInclude namesp=
ace
> if it isn't defined, but your file defines the 'xi' namespace prefix no=
t
> as the XInclude namespace (http://www.w3.org/2001/XInclude), but as som=
ething
> that's very close to it:  (https://www.w3.org/2001/XInclude).  The code=

> then tries to insert xmlns:xi=3D"http://www.w3.org/2001/XInclude" which=
 fails.
>
> The code should handle this better.  It's clearly a bug.  Menawhile, if=
 you
> change the https:// to http:// in the xmlns:xi attribute value, you sho=
uld
> be able to get further.
>
> Once you've fixed that, you'll find that using XInclude doesn't permit
> any inaccuracies in the specification of the href, so you'll have to ad=
d
> https:// to the <xi:include/> entries around line 140.  The v2 processo=
r
> is much more forgiving about this, but the XInclude specification doesn=
't
> permit a processor to be lenient in the manner xml2rfc is for v2 input.=

>
> Then you'll find that <tbody> isn't optional in v3 the way it is in htm=
l,
> and other issues that should be easier to sort out.
>
>
> Best,
>
> 	Henrik
>
> On 2020-01-20 23:59, Henrik Levkowetz wrote:
>> Hi David,
>>
>> On 2020-01-20 23:25, David R. Oran wrote:
>>> Thanks much. See below.
>>
>> Ack.  Will reply further once I've looked at the xml.  One point inlin=
e
>> now:
>>
>>> On 20 Jan 2020, at 16:25, Henrik Levkowetz wrote:
>>>
>>>> Hi David,
>>>>
>>>> On 2020-01-20 22:03, David R. Oran wrote:
>>>>> On 20 Jan 2020, at 15:10, Henrik Levkowetz wrote:
>>>>>
>>>>>> Hi David,
>>>>>>
>>>>>> You should simply remove "<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>" if =
your
>>>>>> <rfc/> element contains the "version=3D'3'" attribute.
>>>>>>
>>>>> If I do that xml2rfc crashes (both the one on my machine and the we=
b tool:
>>>>
>>>> Oh, wow.  Ok, I'll fix that in the next release.  Could you send the=
 full
>>>> xml file, please?  It's not obvious from your snippet where the supe=
rfluous
>>>> other definition of xmlns:xi is.
>>>>
>>> attached.
>>>
>>>> Now, you say that instead of trying the converter, you stared out ri=
ght
>>>> away with v3 syntax, but neither the DOCTYPE above, nor the <?rfc ..=
=2E ?>
>>>> PIs visible in your snippet are appropriate for a v3 document.  Did =
you
>>>> grab a v2 template to start with?  I think really going to lead you =
into
>>>> a number of problems if you start with a v2 template and declare it =
to be
>>>> v3.
>>>>
>>> No, I started from scratch=E2=80=A6but cut a pasted a few things from=
 an
>>> earlier draft after checking (I thought correctly) that I was
>>> following the strict V3 definitions. Possibly not=E2=80=A6
>>>
>>> For yucks, I got rid of all that and started right off with the <rfc>=

>>> element and xml2rfc still crashes.
>>>
>>>> Using the v2v3 converter on a v2 document, even on a v2 template, on=
 the
>>>> other hand, should give you a proper v3 starting point, without the =
issues
>>>> you've run into so far.
>>
>>> I believe that. But the output of the converter on
>>> draft-hoffman-rfcexamples-latest left the DOCTYPE declaration in
>>> there=E2=80=A6
>>
>> I think you'll find that the DOCTYPE doesn't mention a dtd in that cas=
e,
>> just a file which (if available) provides entity definitions.
>>
>> More in a moment.
>>
>>
>> Best regards,
>>
>> 	Henrik
>>
>>>
>>>>
>>>>
>>>> Regards,
>>>>
>>>> 	Henrik
>>>>
>>>>>
>>>>> xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
>>>>> Traceback (most recent call last):
>>>>>   File "/usr/local/bin/xml2rfc", line 8, in <module>
>>>>>     sys.exit(main())
>>>>>   File "/usr/local/lib/python2.7/site-packages/xml2rfc/run.py", lin=
e 612, in main
>>>>>     xmlrfc =3D parser.parse(remove_comments=3DFalse, quiet=3DTrue, =
add_xmlns=3DTrue)
>>>>>   File "/usr/local/lib/python2.7/site-packages/xml2rfc/parser.py", =
line 548, in parse
>>>>>     for action, element in context:
>>>>>   File "src/lxml/iterparse.pxi", line 208, in lxml.etree.iterparse.=
__next__ (src/lxml/lxml.etree.c:148588)
>>>>>   File "<string>", line 22
>>>>> lxml.etree.XMLSyntaxError: Attribute xmlns:xi redefined, line 22, c=
olumn 59
>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> 	Henrik
>>>>>>
>>>>>> On 2020-01-20 21:00, David R. Oran wrote:
>>>>>>> I have a new Internet Draft to write, so I decided to bite the bu=
llet
>>>>>>> and do it in V3. Rather than write in V2 and try the converter, I=

>>>>>>> started out right away with V3 syntax. I didn=E2=80=99t get very =
far. I tried
>>>>>>> both the most recent xml2rfc by installing it on my machine, and =
the web
>>>>>>> tool and got identical errors.
>>>>>>>
>>>>>>> If I follow the described syntax in RFC7991, the RFC Editor FAQ i=
n
>>>>>>> https://ftp.ripe.net/rfc/v3test/FAQ-2019-02.html and the example =
in
>>>>>>> draft-hoffman-rfcexamples-latest as below:
>>>>>>>
>>>>>>> 	<?xml version=3D"1.0" encoding=3D"US-ASCII"?>
>>>>>>> 	<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>
>>>>>>>
>>>>>>> 	<?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?>
>>>>>>> 	<?rfc strict=3D"yes" ?>
>>>>>>> 	<?rfc toc=3D"yes"?>
>>>>>>> 	<?rfc tocdepth=3D"4"?>
>>>>>>> 	<?rfc symrefs=3D"yes" ?>
>>>>>>> 	<?rfc sortrefs=3D"yes" ?>
>>>>>>> 	<?rfc compact=3D"yes" ?>
>>>>>>> 	<?rfc subcompact=3D"no" ?>
>>>>>>> 	<rfc
>>>>>>> 		version=3D=E2=80=983=E2=80=99
>>>>>>> 		ipr=3D'trust200902'
>>>>>>> 		category=3D'exp'
>>>>>>> 		submissionType=3D'IRTF'
>>>>>>> 		docName=3D'draft-oran-icnrg-reflexive-forwarding-00'
>>>>>>> 		xml:lang=3D'en' xmlns:xi=3D"https://www.w3.org/2001/XInclude">
>>>>>>>
>>>>>>> 	<front>
>>>>>>> 		<seriesInfo name=3D'Internet-Draft'
>>>>>>> value=3D'draft-oran-icnrg-reflexive-forwarding-00'/>
>>>>>>> 	    <title abbrev=3D'ICN Reflexive Forwarding'>Reflexive Forward=
ing for
>>>>>>> CCNx and NDN Protocols
>>>>>>> 	    </title>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I get
>>>>>>>
>>>>>>> 	% xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
>>>>>>> 	Incompatible schema information: found "rfc2629.dtd" in <DOCTYPE=
> of a
>>>>>>> version 3 file.
>>>>>>>
>>>>>>> If I leave off the =E2=80=9Cversion=3D=E2=80=983=E2=80=99, as bel=
ow
>>>>>>>
>>>>>>> 	<?xml version=3D"1.0" encoding=3D"US-ASCII"?>
>>>>>>> 	<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>
>>>>>>> 	<?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?>
>>>>>>> 	<?rfc strict=3D"yes" ?>
>>>>>>> 	<?rfc toc=3D"yes"?>
>>>>>>> 	<?rfc tocdepth=3D"4"?>
>>>>>>> 	<?rfc symrefs=3D"yes" ?>
>>>>>>> 	<?rfc sortrefs=3D"yes" ?>
>>>>>>> 	<?rfc compact=3D"yes" ?>
>>>>>>> 	<?rfc subcompact=3D"no" ?>
>>>>>>>
>>>>>>> 	<rfc
>>>>>>> 		ipr=3D'trust200902'
>>>>>>> 		category=3D'exp'
>>>>>>> 		submissionType=3D'IRTF'
>>>>>>> 		docName=3D'draft-oran-icnrg-reflexive-forwarding-00'
>>>>>>> 		xml:lang=3D'en' xmlns:xi=3D"https://www.w3.org/2001/XInclude">
>>>>>>>
>>>>>>> 	<front>
>>>>>>> 		<seriesInfo name=3D'Internet-Draft'
>>>>>>> value=3D'draft-oran-icnrg-reflexive-forwarding-00'/>
>>>>>>> 	    <title abbrev=3D'ICN Reflexive Forwarding'>Reflexive Forward=
ing for
>>>>>>> CCNx and NDN Protocols
>>>>>>> 	    </title>
>>>>>>>
>>>>>>> I get:
>>>>>>>
>>>>>>> 		xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
>>>>>>> 		Error: Unable to validate the XML document:
>>>>>>> draft-oran-icnrg-reflexive-forwarding.xml
>>>>>>> 		 <string>: Line 23: No declaration for attribute xmlns:xi of el=
ement
>>>>>>> rfc
>>>>>>> 		 <string>: Line 25: Element front content does not follow the D=
TD,
>>>>>>> expecting (title , author+ , date , area* , workgroup* , keyword*=
 ,
>>>>>>> abstract? , note*), got (seriesInfo title author author date area=

>>>>>>> workgroup keyword keyword abstract )
>>>>>>> 		 <string>: Line 81: Element section content does not follow the=
 DTD,
>>>>>>> expecting ((t | figure | texttable | iref)* , section*), got (nam=
e t )
>>>>>>> 		 <string>: Line 81: Element section does not carry attribute ti=
tle
>>>>>>> 		 <string>: Line 81: No declaration for element name
>>>>>>> 		 <string>: Line 85: Element section content does not follow the=
 DTD,
>>>>>>> expecting ((t | figure | texttable | iref)* , section*), got (nam=
e t )
>>>>>>> 		 <string>: Line 85: Element section does not carry attribute ti=
tle
>>>>>>> 		 <string>: Line 85: No declaration for element name
>>>>>>> 		 <string>: Line 94: Element section content does not follow the=
 DTD,
>>>>>>> expecting ((t | figure | texttable | iref)* , section*), got (nam=
e t
>>>>>>> section section )
>>>>>>> 		 <string>: Line 94: Element section does not carry attribute ti=
tle
>>>>>>> 		 <string>: Line 94: No declaration for element name
>>>>>>> 		 <string>: Line 97: Element section content does not follow the=
 DTD,
>>>>>>> expecting ((t | figure | texttable | iref)* , section*), got (nam=
e t
>>>>>>> table )
>>>>>>> 		 <string>: Line 97: Element section does not carry attribute ti=
tle
>>>>>>> 		 <string>: Line 97: No declaration for element name
>>>>>>> 		 <string>: Line 98: No declaration for attribute keepWithNext o=
f
>>>>>>> element t
>>>>>>> 		 <string>: Line 99: No declaration for element table
>>>>>>> 		 <string>: Line 99: No declaration for attribute title of eleme=
nt
>>>>>>> table
>>>>>>>
>>>>>>> Clue bat please?
>>>>>>>
>>>>>>> DaveO
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> xml2rfc mailing list
>>>>>>> xml2rfc@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>>>>>>
>>>>>
>>>>> DaveO
>>>>>
>>>
>>> DaveO
>>>
>>

DaveO

--=_MailMate_91C00C75-57F8-4598-A695-EF6345034D44_=
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">Thanks a ton for the help. I puzzled around some more in =
the FAQ and RFC7991, getting rid of suspicious V2-ish stuff that used to =
be adorning all my draft source files and replacing the essentials with t=
he right V3 constructs. However, among those was not the xmlns:ni, which =
I had copied from one of the examples in draft-hoffman-rfcexamples. Once =
that was gone the crash disappeared.</p>

<p dir=3D"auto">One unsolicited piece of advice is that in addition to th=
e FAQ and RFC7991 itself, some templates in native V3 for people to start=
 from would have saved me the pain you see in this thread. The example in=
 Paul Hoffman=E2=80=99s draft (which I found googling =E2=80=9Cxml2rfc v3=
 examples=E2=80=9D of course) was generated using the converter and wound=
 up being extremely misleading for a =E2=80=9Cnative=E2=80=9D V3 source f=
ile.</p>

<p dir=3D"auto">Best, DaveO.</p>

<p dir=3D"auto">P.S. I did get another crash when I put my own &lt;date&g=
t; element in the &lt;front&gt; element as per =E2=80=9C&lt;date month=3D=
'January' year=3D'2020' /&gt; When I let the converter insert the date in=
 the output itself, no problem.</p>

<pre style=3D"background-color:#F7F7F7; border-radius:5px 5px 5px 5px; ma=
rgin-left:15px; margin-right:15px; max-width:90vw; overflow-x:auto; paddi=
ng:5px" bgcolor=3D"#F7F7F7"><code style=3D"background-color:#F7F7F7; bord=
er-radius:3px; margin:0; padding:0" bgcolor=3D"#F7F7F7">xml2rfc draft-ora=
n-icnrg-reflexive-forwarding.xml
draft-oran-icnrg-reflexive-forwarding.xml(63): Warning: The document date=
 (2020-01-01) is more than 3 days away from today's date
Traceback (most recent call last):
  File "/usr/local/bin/xml2rfc", line 8, in &lt;module&gt;
    sys.exit(main())
  File "/usr/local/lib/python2.7/site-packages/xml2rfc/run.py", line 620,=
 in main
    xmlrfc.tree =3D prep.prep()
  File "/usr/local/lib/python2.7/site-packages/xml2rfc/writers/preptool.p=
y", line 342, in prep
    func(e, e.getparent())
  File "/usr/local/lib/python2.7/site-packages/xml2rfc/writers/preptool.p=
y", line 1123, in boilerplate_insert_status_of_memo
    exp =3D datetime.date(year=3Dyear, month=3Dmonth, day=3Dday) + dateti=
me.timedelta(days=3D185)
TypeError: an integer is required
</code></pre>

<p dir=3D"auto">On 20 Jan 2020, at 18:20, Henrik Levkowetz wrote:</p>

</div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir=3D"auto">H=
i again David,<br>
<br>
The issue is triggered by the code trying to insert the XInclude namespac=
e<br>
if it isn't defined, but your file defines the 'xi' namespace prefix not<=
br>
as the XInclude namespace (<a href=3D"http://www.w3.org/2001/XInclude" st=
yle=3D"color:#777">http://www.w3.org/2001/XInclude</a>), but as something=
<br>
that's very close to it:  (<a href=3D"https://www.w3.org/2001/XInclude" s=
tyle=3D"color:#777">https://www.w3.org/2001/XInclude</a>).  The code<br>
then tries to insert xmlns:xi=3D"<a href=3D"http://www.w3.org/2001/XInclu=
de" style=3D"color:#777">http://www.w3.org/2001/XInclude</a>" which fails=
=2E<br>
<br>
The code should handle this better.  It's clearly a bug.  Menawhile, if y=
ou<br>
change the https:// to http:// in the xmlns:xi attribute value, you shoul=
d<br>
be able to get further.<br>
<br>
Once you've fixed that, you'll find that using XInclude doesn't permit<br=
>
any inaccuracies in the specification of the href, so you'll have to add<=
br>
https:// to the &lt;xi:include/&gt; entries around line 140.  The v2 proc=
essor<br>
is much more forgiving about this, but the XInclude specification doesn't=
<br>
permit a processor to be lenient in the manner xml2rfc is for v2 input.<b=
r>
<br>
Then you'll find that &lt;tbody&gt; isn't optional in v3 the way it is in=
 html,<br>
and other issues that should be easier to sort out.<br>
<br>
<br>
Best,<br>
<br>
	Henrik<br>
<br>
On 2020-01-20 23:59, Henrik Levkowetz wrote:</p>
<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 5=
px; padding-left:5px; border-left-color:#999"><p dir=3D"auto">Hi David,<b=
r>
<br>
On 2020-01-20 23:25, David R. Oran wrote:</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">Thanks much=
=2E See below.</p>
</blockquote><p dir=3D"auto">Ack.  Will reply further once I've looked at=
 the xml.  One point inline<br>
now:<br>
</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">On 20 Jan 2=
020, at 16:25, Henrik Levkowetz wrote:<br>
</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">Hi David,<b=
r>
<br>
On 2020-01-20 22:03, David R. Oran wrote:</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">On 20 Jan 2=
020, at 15:10, Henrik Levkowetz wrote:<br>
</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">Hi David,<b=
r>
<br>
You should simply remove "&lt;!DOCTYPE rfc SYSTEM 'rfc2629.dtd'&gt;" if y=
our<br>
&lt;rfc/&gt; element contains the "version=3D'3'" attribute.<br>
</p>
</blockquote><p dir=3D"auto">If I do that xml2rfc crashes (both the one o=
n my machine and the web tool:</p>
</blockquote><p dir=3D"auto">Oh, wow.  Ok, I'll fix that in the next rele=
ase.  Could you send the full<br>
xml file, please?  It's not obvious from your snippet where the superfluo=
us<br>
other definition of xmlns:xi is.<br>
</p>
</blockquote><p dir=3D"auto">attached.<br>
</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">Now, you sa=
y that instead of trying the converter, you stared out right<br>
away with v3 syntax, but neither the DOCTYPE above, nor the &lt;?rfc ... =
?&gt;<br>
PIs visible in your snippet are appropriate for a v3 document.  Did you<b=
r>
grab a v2 template to start with?  I think really going to lead you into<=
br>
a number of problems if you start with a v2 template and declare it to be=
<br>
v3.<br>
</p>
</blockquote><p dir=3D"auto">No, I started from scratch=E2=80=A6but cut a=
 pasted a few things from an<br>
earlier draft after checking (I thought correctly) that I was<br>
following the strict V3 definitions. Possibly not=E2=80=A6<br>
<br>
For yucks, I got rid of all that and started right off with the &lt;rfc&g=
t;<br>
element and xml2rfc still crashes.<br>
</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">Using the v=
2v3 converter on a v2 document, even on a v2 template, on the<br>
other hand, should give you a proper v3 starting point, without the issue=
s<br>
you've run into so far.</p>
</blockquote></blockquote><blockquote style=3D"border-left:2px solid #777=
; color:#BBB; margin:0 0 5px; padding-left:5px; border-left-color:#BBB"><=
p dir=3D"auto">I believe that. But the output of the converter on<br>
draft-hoffman-rfcexamples-latest left the DOCTYPE declaration in<br>
there=E2=80=A6</p>
</blockquote><p dir=3D"auto">I think you'll find that the DOCTYPE doesn't=
 mention a dtd in that case,<br>
just a file which (if available) provides entity definitions.<br>
<br>
More in a moment.<br>
<br>
<br>
Best regards,<br>
<br>
	Henrik<br>
</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><blockquote style=3D"border=
-left:2px solid #777; color:#BBB; margin:0 0 5px; padding-left:5px; borde=
r-left-color:#BBB"><p dir=3D"auto">Regards,<br>
<br>
	Henrik<br>
</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">xml2rfc dra=
ft-oran-icnrg-reflexive-forwarding.xml<br>
Traceback (most recent call last):<br>
  File "/usr/local/bin/xml2rfc", line 8, in &lt;module&gt;<br>
    sys.exit(main())<br>
  File "/usr/local/lib/python2.7/site-packages/xml2rfc/run.py", line 612,=
 in main<br>
    xmlrfc =3D parser.parse(remove_comments=3DFalse, quiet=3DTrue, add_xm=
lns=3DTrue)<br>
  File "/usr/local/lib/python2.7/site-packages/xml2rfc/parser.py", line 5=
48, in parse<br>
    for action, element in context:<br>
  File "src/lxml/iterparse.pxi", line 208, in lxml.etree.iterparse.__next=
__ (src/lxml/lxml.etree.c:148588)<br>
  File "&lt;string&gt;", line 22<br>
lxml.etree.XMLSyntaxError: Attribute xmlns:xi redefined, line 22, column =
59<br>
</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">Regards,<br=
>
<br>
	Henrik<br>
<br>
On 2020-01-20 21:00, David R. Oran wrote:</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">I have a ne=
w Internet Draft to write, so I decided to bite the bullet<br>
and do it in V3. Rather than write in V2 and try the converter, I<br>
started out right away with V3 syntax. I didn=E2=80=99t get very far. I t=
ried<br>
both the most recent xml2rfc by installing it on my machine, and the web<=
br>
tool and got identical errors.<br>
<br>
If I follow the described syntax in RFC7991, the RFC Editor FAQ in<br>
<a href=3D"https://ftp.ripe.net/rfc/v3test/FAQ-2019-02.html" style=3D"col=
or:#BBB">https://ftp.ripe.net/rfc/v3test/FAQ-2019-02.html</a> and the exa=
mple in<br>
draft-hoffman-rfcexamples-latest as below:<br>
<br>
	&lt;?xml version=3D"1.0" encoding=3D"US-ASCII"?&gt;<br>
	&lt;!DOCTYPE rfc SYSTEM 'rfc2629.dtd'&gt;<br>
<br>
	&lt;?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?&gt;<br>
	&lt;?rfc strict=3D"yes" ?&gt;<br>
	&lt;?rfc toc=3D"yes"?&gt;<br>
	&lt;?rfc tocdepth=3D"4"?&gt;<br>
	&lt;?rfc symrefs=3D"yes" ?&gt;<br>
	&lt;?rfc sortrefs=3D"yes" ?&gt;<br>
	&lt;?rfc compact=3D"yes" ?&gt;<br>
	&lt;?rfc subcompact=3D"no" ?&gt;<br>
	&lt;rfc<br>
		version=3D=E2=80=983=E2=80=99<br>
		ipr=3D'trust200902'<br>
		category=3D'exp'<br>
		submissionType=3D'IRTF'<br>
		docName=3D'draft-oran-icnrg-reflexive-forwarding-00'<br>
		xml:lang=3D'en' xmlns:xi=3D"<a href=3D"https://www.w3.org/2001/XInclude=
" style=3D"color:#BBB">https://www.w3.org/2001/XInclude</a>"&gt;<br>
<br>
	&lt;front&gt;<br>
		&lt;seriesInfo name=3D'Internet-Draft'<br>
value=3D'draft-oran-icnrg-reflexive-forwarding-00'/&gt;<br>
	    &lt;title abbrev=3D'ICN Reflexive Forwarding'&gt;Reflexive Forwardin=
g for<br>
CCNx and NDN Protocols<br>
	    &lt;/title&gt;<br>
<br>
<br>
<br>
I get<br>
<br>
	% xml2rfc draft-oran-icnrg-reflexive-forwarding.xml<br>
	Incompatible schema information: found "rfc2629.dtd" in &lt;DOCTYPE&gt; =
of a<br>
version 3 file.<br>
<br>
If I leave off the =E2=80=9Cversion=3D=E2=80=983=E2=80=99, as below<br>
<br>
	&lt;?xml version=3D"1.0" encoding=3D"US-ASCII"?&gt;<br>
	&lt;!DOCTYPE rfc SYSTEM 'rfc2629.dtd'&gt;<br>
	&lt;?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?&gt;<br>
	&lt;?rfc strict=3D"yes" ?&gt;<br>
	&lt;?rfc toc=3D"yes"?&gt;<br>
	&lt;?rfc tocdepth=3D"4"?&gt;<br>
	&lt;?rfc symrefs=3D"yes" ?&gt;<br>
	&lt;?rfc sortrefs=3D"yes" ?&gt;<br>
	&lt;?rfc compact=3D"yes" ?&gt;<br>
	&lt;?rfc subcompact=3D"no" ?&gt;<br>
<br>
	&lt;rfc<br>
		ipr=3D'trust200902'<br>
		category=3D'exp'<br>
		submissionType=3D'IRTF'<br>
		docName=3D'draft-oran-icnrg-reflexive-forwarding-00'<br>
		xml:lang=3D'en' xmlns:xi=3D"<a href=3D"https://www.w3.org/2001/XInclude=
" style=3D"color:#BBB">https://www.w3.org/2001/XInclude</a>"&gt;<br>
<br>
	&lt;front&gt;<br>
		&lt;seriesInfo name=3D'Internet-Draft'<br>
value=3D'draft-oran-icnrg-reflexive-forwarding-00'/&gt;<br>
	    &lt;title abbrev=3D'ICN Reflexive Forwarding'&gt;Reflexive Forwardin=
g for<br>
CCNx and NDN Protocols<br>
	    &lt;/title&gt;<br>
<br>
I get:<br>
<br>
		xml2rfc draft-oran-icnrg-reflexive-forwarding.xml<br>
		Error: Unable to validate the XML document:<br>
draft-oran-icnrg-reflexive-forwarding.xml<br>
		 &lt;string&gt;: Line 23: No declaration for attribute xmlns:xi of elem=
ent<br>
rfc<br>
		 &lt;string&gt;: Line 25: Element front content does not follow the DTD=
,<br>
expecting (title , author+ , date , area* , workgroup* , keyword* ,<br>
abstract? , note*), got (seriesInfo title author author date area<br>
workgroup keyword keyword abstract )<br>
		 &lt;string&gt;: Line 81: Element section content does not follow the D=
TD,<br>
expecting ((t | figure | texttable | iref)* , section*), got (name t )<br=
>
		 &lt;string&gt;: Line 81: Element section does not carry attribute titl=
e<br>
		 &lt;string&gt;: Line 81: No declaration for element name<br>
		 &lt;string&gt;: Line 85: Element section content does not follow the D=
TD,<br>
expecting ((t | figure | texttable | iref)* , section*), got (name t )<br=
>
		 &lt;string&gt;: Line 85: Element section does not carry attribute titl=
e<br>
		 &lt;string&gt;: Line 85: No declaration for element name<br>
		 &lt;string&gt;: Line 94: Element section content does not follow the D=
TD,<br>
expecting ((t | figure | texttable | iref)* , section*), got (name t<br>
section section )<br>
		 &lt;string&gt;: Line 94: Element section does not carry attribute titl=
e<br>
		 &lt;string&gt;: Line 94: No declaration for element name<br>
		 &lt;string&gt;: Line 97: Element section content does not follow the D=
TD,<br>
expecting ((t | figure | texttable | iref)* , section*), got (name t<br>
table )<br>
		 &lt;string&gt;: Line 97: Element section does not carry attribute titl=
e<br>
		 &lt;string&gt;: Line 97: No declaration for element name<br>
		 &lt;string&gt;: Line 98: No declaration for attribute keepWithNext of<=
br>
element t<br>
		 &lt;string&gt;: Line 99: No declaration for element table<br>
		 &lt;string&gt;: Line 99: No declaration for attribute title of element=
<br>
table<br>
<br>
Clue bat please?<br>
<br>
DaveO<br>
<br>
<br>
<br>
_______________________________________________<br>
xml2rfc mailing list<br>
xml2rfc@ietf.org<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/xml2rfc" style=3D"color:=
#BBB">https://www.ietf.org/mailman/listinfo/xml2rfc</a><br>
</p>
</blockquote></blockquote><p dir=3D"auto">DaveO<br>
</p>
</blockquote></blockquote><p dir=3D"auto">DaveO<br>
</p>
</blockquote></blockquote></blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">DaveO</p>
</div>
</div>
</body>
</html>

--=_MailMate_91C00C75-57F8-4598-A695-EF6345034D44_=--

--=_MailMate_1887897D-3C6E-44B0-B22F-C9BE523CB48B_=
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename=signature.asc
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iQJJBAEBAgAzFiEEroJBCc9z/EJK1xs/eu0uvThCv/AFAl4mkUUVHGRhdmVvcmFu
QG9yYW5kb20ubmV0AAoJEHrtLr04Qr/wNrgP/2YDGpRHv6RHg5ajD3bnmD5k1Qt1
MFvvzx3Fh2hihmbvCO+mFM6HmT3MOGXGNP/isfd9Ktigv2kPnQON5H7l5vqi+HHK
PdprUW/55O6Hoq8ThtSHwH0EZdo16L8xxQGod/poTMWJcF4bbl1iCWfE4cVvniLQ
bNpirc0wsLmCoUudQFr+jCc1FyBiffO8nKqmEcCrh1fyWjGO0kR53y+IPVqLAQT+
/F+VC9rtogH0OkDA0Nv3ceEUHcyY5UynCGNgLnUWjBk1rQLvq/u5zyvLVx6TTDKc
jWvOPoEtYd4XV3tibQ42oio5aj/RyYrMA3xkcGJTPtWURgAISx5zPhNSFF874dhg
kxx4Y3qNNUjeR0K9DBwlnCUxuYUjTjKlA8g2y0C+WFSQhtwM04yje6x/EwoDD+m2
tq2/W9m3KXwYFkF/GskZ8X+FGNYaw6kwUV5rfocsavueFi2Rqg6tX8Qn4FIv/0Tg
dc3S5G1MIIg+SJg86CBaMg29rDPlV7ZFXbkPp4dvS2yyizthy0FYNBPPhrecVcvW
ZQg7CNdE20pdvcls5CJVOhMN37QzTnfJP8RrIf15M4i/2PnS2ThzVkFfAopG/RUt
faYMppt04sac6pcSH7A7+7ahuXrn/aFAda2mpJGbo3qMgP8QQYl9/O2Bk6nkpR0x
jUlyCnGYjUu+df5p
=xmu7
-----END PGP SIGNATURE-----

--=_MailMate_1887897D-3C6E-44B0-B22F-C9BE523CB48B_=--


From nobody Mon Jan 20 22:00:00 2020
Return-Path: <daveoran@orandom.net>
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 B1552120071 for <xml2rfc@ietfa.amsl.com>; Mon, 20 Jan 2020 21:59:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 25U1mR7lq6nG for <xml2rfc@ietfa.amsl.com>; Mon, 20 Jan 2020 21:59:55 -0800 (PST)
Received: from spark.crystalorb.net (spark.crystalorb.net [IPv6:2607:fca8:1530::c]) (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 63EFF120052 for <xml2rfc@ietf.org>; Mon, 20 Jan 2020 21:59:55 -0800 (PST)
Received: from [192.168.15.102] ([IPv6:2601:184:407f:80ce:349f:2df:2bdc:d2ac]) (authenticated bits=0) by spark.crystalorb.net (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id 00L5xqm6025242 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Mon, 20 Jan 2020 21:59:54 -0800
From: "David R. Oran" <daveoran@orandom.net>
To: "Henrik Levkowetz" <henrik@levkowetz.com>
Cc: xml2rfc@ietf.org
Date: Tue, 21 Jan 2020 00:59:46 -0500
X-Mailer: MailMate (1.13.1r5676)
Message-ID: <C49A9B95-1196-4439-8021-31ECDC676813@orandom.net>
In-Reply-To: <A6C1B0DF-EAE0-46DC-9539-F56A3192E336@orandom.net>
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net> <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com> <DA4F22F5-5A43-4671-B69B-EDF61F976623@orandom.net> <61971d80-1c1e-bdf7-a986-0cfe9de157e6@levkowetz.com> <6C8FDE4E-88F8-4862-A9CC-3D1E9B0DCD4C@orandom.net> <fe468ed5-3d9b-88b2-8403-f8482bb1f55b@levkowetz.com> <647a593e-8104-0a59-bd0b-fb377f49201e@levkowetz.com> <A6C1B0DF-EAE0-46DC-9539-F56A3192E336@orandom.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_E479A2A2-0EE9-48DC-8C2E-D36E5D3ADC9B_="; micalg=pgp-sha1; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/3tDKclsn-SLNowrMpYKWUI6tQB0>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
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: Tue, 21 Jan 2020 05:59:59 -0000

This is an OpenPGP/MIME signed message (RFC 3156 and 4880).

--=_MailMate_E479A2A2-0EE9-48DC-8C2E-D36E5D3ADC9B_=
Content-Type: multipart/alternative;
 boundary="=_MailMate_F8600329-138A-4ACF-A128-F4AAB0A6996C_="
Embedded-HTML: [{"HTML":[996,14140],"plain":[313,11223],"uuid":"D63EF277-B83F-4107-90B2-C3BAEFBA4FC2"}]


--=_MailMate_F8600329-138A-4ACF-A128-F4AAB0A6996C_=
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Oh, one more thing I noticed that puzzled me briefly=E2=80=A6

RFC7991 says:

	2.45.3.  "docName" Attribute

	   Deprecated; instead, use the "value" attribute in <seriesInfo>.

but your draft won=E2=80=99t compile unless you include it as an attribut=
e of the <rfc> element.

On 21 Jan 2020, at 0:51, David R. Oran wrote:

> Thanks a ton for the help. I puzzled around some more in the FAQ and RF=
C7991, getting rid of suspicious V2-ish stuff that used to be adorning al=
l my draft source files and replacing the essentials with the right V3 co=
nstructs. However, among those was not the xmlns:ni, which I had copied f=
rom one of the examples in draft-hoffman-rfcexamples. Once that was gone =
the crash disappeared.
>
> One unsolicited piece of advice is that in addition to the FAQ and RFC7=
991 itself, some templates in native V3 for people to start from would ha=
ve saved me the pain you see in this thread. The example in Paul Hoffman=E2=
=80=99s draft (which I found googling =E2=80=9Cxml2rfc v3 examples=E2=80=9D=
 of course) was generated using the converter and wound up being extremel=
y misleading for a =E2=80=9Cnative=E2=80=9D V3 source file.
>
> Best, DaveO.
>
> P.S. I did get another crash when I put my own <date> element in the <f=
ront> element as per =E2=80=9C<date month=3D'January' year=3D'2020' /> Wh=
en I let the converter insert the date in the output itself, no problem.
>
>
> 	xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
> 	draft-oran-icnrg-reflexive-forwarding.xml(63): Warning: The document d=
ate (2020-01-01) is more than 3 days away from today's date
> 	Traceback (most recent call last):
> 	  File "/usr/local/bin/xml2rfc", line 8, in <module>
> 	    sys.exit(main())
> 	  File "/usr/local/lib/python2.7/site-packages/xml2rfc/run.py", line 6=
20, in main
> 	    xmlrfc.tree =3D prep.prep()
> 	  File "/usr/local/lib/python2.7/site-packages/xml2rfc/writers/preptoo=
l.py", line 342, in prep
> 	    func(e, e.getparent())
> 	  File "/usr/local/lib/python2.7/site-packages/xml2rfc/writers/preptoo=
l.py", line 1123, in boilerplate_insert_status_of_memo
> 	    exp =3D datetime.date(year=3Dyear, month=3Dmonth, day=3Dday) + dat=
etime.timedelta(days=3D185)
> 	TypeError: an integer is required
>
>
> On 20 Jan 2020, at 18:20, Henrik Levkowetz wrote:
>
>> Hi again David,
>>
>> The issue is triggered by the code trying to insert the XInclude names=
pace
>> if it isn't defined, but your file defines the 'xi' namespace prefix n=
ot
>> as the XInclude namespace (http://www.w3.org/2001/XInclude), but as so=
mething
>> that's very close to it:  (https://www.w3.org/2001/XInclude).  The cod=
e
>> then tries to insert xmlns:xi=3D"http://www.w3.org/2001/XInclude" whic=
h fails.
>>
>> The code should handle this better.  It's clearly a bug.  Menawhile, i=
f you
>> change the https:// to http:// in the xmlns:xi attribute value, you sh=
ould
>> be able to get further.
>>
>> Once you've fixed that, you'll find that using XInclude doesn't permit=

>> any inaccuracies in the specification of the href, so you'll have to a=
dd
>> https:// to the <xi:include/> entries around line 140.  The v2 process=
or
>> is much more forgiving about this, but the XInclude specification does=
n't
>> permit a processor to be lenient in the manner xml2rfc is for v2 input=
=2E
>>
>> Then you'll find that <tbody> isn't optional in v3 the way it is in ht=
ml,
>> and other issues that should be easier to sort out.
>>
>>
>> Best,
>>
>> 	Henrik
>>
>> On 2020-01-20 23:59, Henrik Levkowetz wrote:
>>> Hi David,
>>>
>>> On 2020-01-20 23:25, David R. Oran wrote:
>>>> Thanks much. See below.
>>>
>>> Ack.  Will reply further once I've looked at the xml.  One point inli=
ne
>>> now:
>>>
>>>> On 20 Jan 2020, at 16:25, Henrik Levkowetz wrote:
>>>>
>>>>> Hi David,
>>>>>
>>>>> On 2020-01-20 22:03, David R. Oran wrote:
>>>>>> On 20 Jan 2020, at 15:10, Henrik Levkowetz wrote:
>>>>>>
>>>>>>> Hi David,
>>>>>>>
>>>>>>> You should simply remove "<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>" if=
 your
>>>>>>> <rfc/> element contains the "version=3D'3'" attribute.
>>>>>>>
>>>>>> If I do that xml2rfc crashes (both the one on my machine and the w=
eb tool:
>>>>>
>>>>> Oh, wow.  Ok, I'll fix that in the next release.  Could you send th=
e full
>>>>> xml file, please?  It's not obvious from your snippet where the sup=
erfluous
>>>>> other definition of xmlns:xi is.
>>>>>
>>>> attached.
>>>>
>>>>> Now, you say that instead of trying the converter, you stared out r=
ight
>>>>> away with v3 syntax, but neither the DOCTYPE above, nor the <?rfc .=
=2E. ?>
>>>>> PIs visible in your snippet are appropriate for a v3 document.  Did=
 you
>>>>> grab a v2 template to start with?  I think really going to lead you=
 into
>>>>> a number of problems if you start with a v2 template and declare it=
 to be
>>>>> v3.
>>>>>
>>>> No, I started from scratch=E2=80=A6but cut a pasted a few things fro=
m an
>>>> earlier draft after checking (I thought correctly) that I was
>>>> following the strict V3 definitions. Possibly not=E2=80=A6
>>>>
>>>> For yucks, I got rid of all that and started right off with the <rfc=
>
>>>> element and xml2rfc still crashes.
>>>>
>>>>> Using the v2v3 converter on a v2 document, even on a v2 template, o=
n the
>>>>> other hand, should give you a proper v3 starting point, without the=
 issues
>>>>> you've run into so far.
>>>
>>>> I believe that. But the output of the converter on
>>>> draft-hoffman-rfcexamples-latest left the DOCTYPE declaration in
>>>> there=E2=80=A6
>>>
>>> I think you'll find that the DOCTYPE doesn't mention a dtd in that ca=
se,
>>> just a file which (if available) provides entity definitions.
>>>
>>> More in a moment.
>>>
>>>
>>> Best regards,
>>>
>>> 	Henrik
>>>
>>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>> 	Henrik
>>>>>
>>>>>>
>>>>>> xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
>>>>>> Traceback (most recent call last):
>>>>>>   File "/usr/local/bin/xml2rfc", line 8, in <module>
>>>>>>     sys.exit(main())
>>>>>>   File "/usr/local/lib/python2.7/site-packages/xml2rfc/run.py", li=
ne 612, in main
>>>>>>     xmlrfc =3D parser.parse(remove_comments=3DFalse, quiet=3DTrue,=
 add_xmlns=3DTrue)
>>>>>>   File "/usr/local/lib/python2.7/site-packages/xml2rfc/parser.py",=
 line 548, in parse
>>>>>>     for action, element in context:
>>>>>>   File "src/lxml/iterparse.pxi", line 208, in lxml.etree.iterparse=
=2E__next__ (src/lxml/lxml.etree.c:148588)
>>>>>>   File "<string>", line 22
>>>>>> lxml.etree.XMLSyntaxError: Attribute xmlns:xi redefined, line 22, =
column 59
>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> 	Henrik
>>>>>>>
>>>>>>> On 2020-01-20 21:00, David R. Oran wrote:
>>>>>>>> I have a new Internet Draft to write, so I decided to bite the b=
ullet
>>>>>>>> and do it in V3. Rather than write in V2 and try the converter, =
I
>>>>>>>> started out right away with V3 syntax. I didn=E2=80=99t get very=
 far. I tried
>>>>>>>> both the most recent xml2rfc by installing it on my machine, and=
 the web
>>>>>>>> tool and got identical errors.
>>>>>>>>
>>>>>>>> If I follow the described syntax in RFC7991, the RFC Editor FAQ =
in
>>>>>>>> https://ftp.ripe.net/rfc/v3test/FAQ-2019-02.html and the example=
 in
>>>>>>>> draft-hoffman-rfcexamples-latest as below:
>>>>>>>>
>>>>>>>> 	<?xml version=3D"1.0" encoding=3D"US-ASCII"?>
>>>>>>>> 	<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>
>>>>>>>>
>>>>>>>> 	<?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?>
>>>>>>>> 	<?rfc strict=3D"yes" ?>
>>>>>>>> 	<?rfc toc=3D"yes"?>
>>>>>>>> 	<?rfc tocdepth=3D"4"?>
>>>>>>>> 	<?rfc symrefs=3D"yes" ?>
>>>>>>>> 	<?rfc sortrefs=3D"yes" ?>
>>>>>>>> 	<?rfc compact=3D"yes" ?>
>>>>>>>> 	<?rfc subcompact=3D"no" ?>
>>>>>>>> 	<rfc
>>>>>>>> 		version=3D=E2=80=983=E2=80=99
>>>>>>>> 		ipr=3D'trust200902'
>>>>>>>> 		category=3D'exp'
>>>>>>>> 		submissionType=3D'IRTF'
>>>>>>>> 		docName=3D'draft-oran-icnrg-reflexive-forwarding-00'
>>>>>>>> 		xml:lang=3D'en' xmlns:xi=3D"https://www.w3.org/2001/XInclude">=

>>>>>>>>
>>>>>>>> 	<front>
>>>>>>>> 		<seriesInfo name=3D'Internet-Draft'
>>>>>>>> value=3D'draft-oran-icnrg-reflexive-forwarding-00'/>
>>>>>>>> 	    <title abbrev=3D'ICN Reflexive Forwarding'>Reflexive Forwar=
ding for
>>>>>>>> CCNx and NDN Protocols
>>>>>>>> 	    </title>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> I get
>>>>>>>>
>>>>>>>> 	% xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
>>>>>>>> 	Incompatible schema information: found "rfc2629.dtd" in <DOCTYP=
E> of a
>>>>>>>> version 3 file.
>>>>>>>>
>>>>>>>> If I leave off the =E2=80=9Cversion=3D=E2=80=983=E2=80=99, as be=
low
>>>>>>>>
>>>>>>>> 	<?xml version=3D"1.0" encoding=3D"US-ASCII"?>
>>>>>>>> 	<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>
>>>>>>>> 	<?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?>
>>>>>>>> 	<?rfc strict=3D"yes" ?>
>>>>>>>> 	<?rfc toc=3D"yes"?>
>>>>>>>> 	<?rfc tocdepth=3D"4"?>
>>>>>>>> 	<?rfc symrefs=3D"yes" ?>
>>>>>>>> 	<?rfc sortrefs=3D"yes" ?>
>>>>>>>> 	<?rfc compact=3D"yes" ?>
>>>>>>>> 	<?rfc subcompact=3D"no" ?>
>>>>>>>>
>>>>>>>> 	<rfc
>>>>>>>> 		ipr=3D'trust200902'
>>>>>>>> 		category=3D'exp'
>>>>>>>> 		submissionType=3D'IRTF'
>>>>>>>> 		docName=3D'draft-oran-icnrg-reflexive-forwarding-00'
>>>>>>>> 		xml:lang=3D'en' xmlns:xi=3D"https://www.w3.org/2001/XInclude">=

>>>>>>>>
>>>>>>>> 	<front>
>>>>>>>> 		<seriesInfo name=3D'Internet-Draft'
>>>>>>>> value=3D'draft-oran-icnrg-reflexive-forwarding-00'/>
>>>>>>>> 	    <title abbrev=3D'ICN Reflexive Forwarding'>Reflexive Forwar=
ding for
>>>>>>>> CCNx and NDN Protocols
>>>>>>>> 	    </title>
>>>>>>>>
>>>>>>>> I get:
>>>>>>>>
>>>>>>>> 		xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
>>>>>>>> 		Error: Unable to validate the XML document:
>>>>>>>> draft-oran-icnrg-reflexive-forwarding.xml
>>>>>>>> 		 <string>: Line 23: No declaration for attribute xmlns:xi of e=
lement
>>>>>>>> rfc
>>>>>>>> 		 <string>: Line 25: Element front content does not follow the =
DTD,
>>>>>>>> expecting (title , author+ , date , area* , workgroup* , keyword=
* ,
>>>>>>>> abstract? , note*), got (seriesInfo title author author date are=
a
>>>>>>>> workgroup keyword keyword abstract )
>>>>>>>> 		 <string>: Line 81: Element section content does not follow th=
e DTD,
>>>>>>>> expecting ((t | figure | texttable | iref)* , section*), got (na=
me t )
>>>>>>>> 		 <string>: Line 81: Element section does not carry attribute t=
itle
>>>>>>>> 		 <string>: Line 81: No declaration for element name
>>>>>>>> 		 <string>: Line 85: Element section content does not follow th=
e DTD,
>>>>>>>> expecting ((t | figure | texttable | iref)* , section*), got (na=
me t )
>>>>>>>> 		 <string>: Line 85: Element section does not carry attribute t=
itle
>>>>>>>> 		 <string>: Line 85: No declaration for element name
>>>>>>>> 		 <string>: Line 94: Element section content does not follow th=
e DTD,
>>>>>>>> expecting ((t | figure | texttable | iref)* , section*), got (na=
me t
>>>>>>>> section section )
>>>>>>>> 		 <string>: Line 94: Element section does not carry attribute t=
itle
>>>>>>>> 		 <string>: Line 94: No declaration for element name
>>>>>>>> 		 <string>: Line 97: Element section content does not follow th=
e DTD,
>>>>>>>> expecting ((t | figure | texttable | iref)* , section*), got (na=
me t
>>>>>>>> table )
>>>>>>>> 		 <string>: Line 97: Element section does not carry attribute t=
itle
>>>>>>>> 		 <string>: Line 97: No declaration for element name
>>>>>>>> 		 <string>: Line 98: No declaration for attribute keepWithNext =
of
>>>>>>>> element t
>>>>>>>> 		 <string>: Line 99: No declaration for element table
>>>>>>>> 		 <string>: Line 99: No declaration for attribute title of elem=
ent
>>>>>>>> table
>>>>>>>>
>>>>>>>> Clue bat please?
>>>>>>>>
>>>>>>>> DaveO
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> xml2rfc mailing list
>>>>>>>> xml2rfc@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>>>>>>>
>>>>>>
>>>>>> DaveO
>>>>>>
>>>>
>>>> DaveO
>>>>
>>>
>
> DaveO


> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc

DaveO

--=_MailMate_F8600329-138A-4ACF-A128-F4AAB0A6996C_=
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">Oh, one more thing I noticed that puzzled me briefly=E2=80=
=A6</p>

<p dir=3D"auto">RFC7991 says:</p>

<pre style=3D"background-color:#F7F7F7; border-radius:5px 5px 5px 5px; ma=
rgin-left:15px; margin-right:15px; max-width:90vw; overflow-x:auto; paddi=
ng:5px" bgcolor=3D"#F7F7F7"><code style=3D"background-color:#F7F7F7; bord=
er-radius:3px; margin:0; padding:0" bgcolor=3D"#F7F7F7">2.45.3.  "docName=
" Attribute

   Deprecated; instead, use the "value" attribute in &lt;seriesInfo&gt;.
</code></pre>

<p dir=3D"auto">but your draft won=E2=80=99t compile unless you include i=
t as an attribute of the &lt;rfc&gt; element.</p>

<p dir=3D"auto">On 21 Jan 2020, at 0:51, David R. Oran wrote:</p>

</div>
<div style=3D"white-space:normal"></div>
<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px"><div id=3D"D63EF277-B83F-4107-90B2-C3BAEFBA4FC2">

<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">Thanks a ton for the help. I puzzled around some more in =
the FAQ and RFC7991, getting rid of suspicious V2-ish stuff that used to =
be adorning all my draft source files and replacing the essentials with t=
he right V3 constructs. However, among those was not the xmlns:ni, which =
I had copied from one of the examples in draft-hoffman-rfcexamples. Once =
that was gone the crash disappeared.</p>

<p dir=3D"auto">One unsolicited piece of advice is that in addition to th=
e FAQ and RFC7991 itself, some templates in native V3 for people to start=
 from would have saved me the pain you see in this thread. The example in=
 Paul Hoffman=E2=80=99s draft (which I found googling =E2=80=9Cxml2rfc v3=
 examples=E2=80=9D of course) was generated using the converter and wound=
 up being extremely misleading for a =E2=80=9Cnative=E2=80=9D V3 source f=
ile.</p>

<p dir=3D"auto">Best, DaveO.</p>

<p dir=3D"auto">P.S. I did get another crash when I put my own &lt;date&g=
t; element in the &lt;front&gt; element as per =E2=80=9C&lt;date month=3D=
'January' year=3D'2020' /&gt; When I let the converter insert the date in=
 the output itself, no problem.</p>

<pre style=3D"background-color:#F7F7F7; border-radius:5px 5px 5px 5px; ma=
rgin-left:15px; margin-right:15px; max-width:90vw; overflow-x:auto; paddi=
ng:5px" bgcolor=3D"#F7F7F7"><code style=3D"background-color:#F7F7F7; bord=
er-radius:3px; margin:0; padding:0" bgcolor=3D"#F7F7F7">xml2rfc draft-ora=
n-icnrg-reflexive-forwarding.xml
draft-oran-icnrg-reflexive-forwarding.xml(63): Warning: The document date=
 (2020-01-01) is more than 3 days away from today's date
Traceback (most recent call last):
  File "/usr/local/bin/xml2rfc", line 8, in &lt;module&gt;
    sys.exit(main())
  File "/usr/local/lib/python2.7/site-packages/xml2rfc/run.py", line 620,=
 in main
    xmlrfc.tree =3D prep.prep()
  File "/usr/local/lib/python2.7/site-packages/xml2rfc/writers/preptool.p=
y", line 342, in prep
    func(e, e.getparent())
  File "/usr/local/lib/python2.7/site-packages/xml2rfc/writers/preptool.p=
y", line 1123, in boilerplate_insert_status_of_memo
    exp =3D datetime.date(year=3Dyear, month=3Dmonth, day=3Dday) + dateti=
me.timedelta(days=3D185)
TypeError: an integer is required
</code></pre>

<p dir=3D"auto">On 20 Jan 2020, at 18:20, Henrik Levkowetz wrote:</p>

</div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir=3D"auto">H=
i again David,<br>
<br>
The issue is triggered by the code trying to insert the XInclude namespac=
e<br>
if it isn't defined, but your file defines the 'xi' namespace prefix not<=
br>
as the XInclude namespace (<a href=3D"http://www.w3.org/2001/XInclude" st=
yle=3D"color:#777">http://www.w3.org/2001/XInclude</a>), but as something=
<br>
that's very close to it:  (<a href=3D"https://www.w3.org/2001/XInclude" s=
tyle=3D"color:#777">https://www.w3.org/2001/XInclude</a>).  The code<br>
then tries to insert xmlns:xi=3D"<a href=3D"http://www.w3.org/2001/XInclu=
de" style=3D"color:#777">http://www.w3.org/2001/XInclude</a>" which fails=
=2E<br>
<br>
The code should handle this better.  It's clearly a bug.  Menawhile, if y=
ou<br>
change the https:// to http:// in the xmlns:xi attribute value, you shoul=
d<br>
be able to get further.<br>
<br>
Once you've fixed that, you'll find that using XInclude doesn't permit<br=
>
any inaccuracies in the specification of the href, so you'll have to add<=
br>
https:// to the &lt;xi:include/&gt; entries around line 140.  The v2 proc=
essor<br>
is much more forgiving about this, but the XInclude specification doesn't=
<br>
permit a processor to be lenient in the manner xml2rfc is for v2 input.<b=
r>
<br>
Then you'll find that &lt;tbody&gt; isn't optional in v3 the way it is in=
 html,<br>
and other issues that should be easier to sort out.<br>
<br>
<br>
Best,<br>
<br>
	Henrik<br>
<br>
On 2020-01-20 23:59, Henrik Levkowetz wrote:</p>
<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 5=
px; padding-left:5px; border-left-color:#999"><p dir=3D"auto">Hi David,<b=
r>
<br>
On 2020-01-20 23:25, David R. Oran wrote:</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">Thanks much=
=2E See below.</p>
</blockquote><p dir=3D"auto">Ack.  Will reply further once I've looked at=
 the xml.  One point inline<br>
now:<br>
</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">On 20 Jan 2=
020, at 16:25, Henrik Levkowetz wrote:<br>
</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">Hi David,<b=
r>
<br>
On 2020-01-20 22:03, David R. Oran wrote:</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">On 20 Jan 2=
020, at 15:10, Henrik Levkowetz wrote:<br>
</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">Hi David,<b=
r>
<br>
You should simply remove "&lt;!DOCTYPE rfc SYSTEM 'rfc2629.dtd'&gt;" if y=
our<br>
&lt;rfc/&gt; element contains the "version=3D'3'" attribute.<br>
</p>
</blockquote><p dir=3D"auto">If I do that xml2rfc crashes (both the one o=
n my machine and the web tool:</p>
</blockquote><p dir=3D"auto">Oh, wow.  Ok, I'll fix that in the next rele=
ase.  Could you send the full<br>
xml file, please?  It's not obvious from your snippet where the superfluo=
us<br>
other definition of xmlns:xi is.<br>
</p>
</blockquote><p dir=3D"auto">attached.<br>
</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">Now, you sa=
y that instead of trying the converter, you stared out right<br>
away with v3 syntax, but neither the DOCTYPE above, nor the &lt;?rfc ... =
?&gt;<br>
PIs visible in your snippet are appropriate for a v3 document.  Did you<b=
r>
grab a v2 template to start with?  I think really going to lead you into<=
br>
a number of problems if you start with a v2 template and declare it to be=
<br>
v3.<br>
</p>
</blockquote><p dir=3D"auto">No, I started from scratch=E2=80=A6but cut a=
 pasted a few things from an<br>
earlier draft after checking (I thought correctly) that I was<br>
following the strict V3 definitions. Possibly not=E2=80=A6<br>
<br>
For yucks, I got rid of all that and started right off with the &lt;rfc&g=
t;<br>
element and xml2rfc still crashes.<br>
</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">Using the v=
2v3 converter on a v2 document, even on a v2 template, on the<br>
other hand, should give you a proper v3 starting point, without the issue=
s<br>
you've run into so far.</p>
</blockquote></blockquote><blockquote style=3D"border-left:2px solid #777=
; color:#BBB; margin:0 0 5px; padding-left:5px; border-left-color:#BBB"><=
p dir=3D"auto">I believe that. But the output of the converter on<br>
draft-hoffman-rfcexamples-latest left the DOCTYPE declaration in<br>
there=E2=80=A6</p>
</blockquote><p dir=3D"auto">I think you'll find that the DOCTYPE doesn't=
 mention a dtd in that case,<br>
just a file which (if available) provides entity definitions.<br>
<br>
More in a moment.<br>
<br>
<br>
Best regards,<br>
<br>
	Henrik<br>
</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><blockquote style=3D"border=
-left:2px solid #777; color:#BBB; margin:0 0 5px; padding-left:5px; borde=
r-left-color:#BBB"><p dir=3D"auto">Regards,<br>
<br>
	Henrik<br>
</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">xml2rfc dra=
ft-oran-icnrg-reflexive-forwarding.xml<br>
Traceback (most recent call last):<br>
  File "/usr/local/bin/xml2rfc", line 8, in &lt;module&gt;<br>
    sys.exit(main())<br>
  File "/usr/local/lib/python2.7/site-packages/xml2rfc/run.py", line 612,=
 in main<br>
    xmlrfc =3D parser.parse(remove_comments=3DFalse, quiet=3DTrue, add_xm=
lns=3DTrue)<br>
  File "/usr/local/lib/python2.7/site-packages/xml2rfc/parser.py", line 5=
48, in parse<br>
    for action, element in context:<br>
  File "src/lxml/iterparse.pxi", line 208, in lxml.etree.iterparse.__next=
__ (src/lxml/lxml.etree.c:148588)<br>
  File "&lt;string&gt;", line 22<br>
lxml.etree.XMLSyntaxError: Attribute xmlns:xi redefined, line 22, column =
59<br>
</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">Regards,<br=
>
<br>
	Henrik<br>
<br>
On 2020-01-20 21:00, David R. Oran wrote:</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">I have a ne=
w Internet Draft to write, so I decided to bite the bullet<br>
and do it in V3. Rather than write in V2 and try the converter, I<br>
started out right away with V3 syntax. I didn=E2=80=99t get very far. I t=
ried<br>
both the most recent xml2rfc by installing it on my machine, and the web<=
br>
tool and got identical errors.<br>
<br>
If I follow the described syntax in RFC7991, the RFC Editor FAQ in<br>
<a href=3D"https://ftp.ripe.net/rfc/v3test/FAQ-2019-02.html" style=3D"col=
or:#BBB">https://ftp.ripe.net/rfc/v3test/FAQ-2019-02.html</a> and the exa=
mple in<br>
draft-hoffman-rfcexamples-latest as below:<br>
<br>
	&lt;?xml version=3D"1.0" encoding=3D"US-ASCII"?&gt;<br>
	&lt;!DOCTYPE rfc SYSTEM 'rfc2629.dtd'&gt;<br>
<br>
	&lt;?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?&gt;<br>
	&lt;?rfc strict=3D"yes" ?&gt;<br>
	&lt;?rfc toc=3D"yes"?&gt;<br>
	&lt;?rfc tocdepth=3D"4"?&gt;<br>
	&lt;?rfc symrefs=3D"yes" ?&gt;<br>
	&lt;?rfc sortrefs=3D"yes" ?&gt;<br>
	&lt;?rfc compact=3D"yes" ?&gt;<br>
	&lt;?rfc subcompact=3D"no" ?&gt;<br>
	&lt;rfc<br>
		version=3D=E2=80=983=E2=80=99<br>
		ipr=3D'trust200902'<br>
		category=3D'exp'<br>
		submissionType=3D'IRTF'<br>
		docName=3D'draft-oran-icnrg-reflexive-forwarding-00'<br>
		xml:lang=3D'en' xmlns:xi=3D"<a href=3D"https://www.w3.org/2001/XInclude=
" style=3D"color:#BBB">https://www.w3.org/2001/XInclude</a>"&gt;<br>
<br>
	&lt;front&gt;<br>
		&lt;seriesInfo name=3D'Internet-Draft'<br>
value=3D'draft-oran-icnrg-reflexive-forwarding-00'/&gt;<br>
	    &lt;title abbrev=3D'ICN Reflexive Forwarding'&gt;Reflexive Forwardin=
g for<br>
CCNx and NDN Protocols<br>
	    &lt;/title&gt;<br>
<br>
<br>
<br>
I get<br>
<br>
	% xml2rfc draft-oran-icnrg-reflexive-forwarding.xml<br>
	Incompatible schema information: found "rfc2629.dtd" in &lt;DOCTYPE&gt; =
of a<br>
version 3 file.<br>
<br>
If I leave off the =E2=80=9Cversion=3D=E2=80=983=E2=80=99, as below<br>
<br>
	&lt;?xml version=3D"1.0" encoding=3D"US-ASCII"?&gt;<br>
	&lt;!DOCTYPE rfc SYSTEM 'rfc2629.dtd'&gt;<br>
	&lt;?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?&gt;<br>
	&lt;?rfc strict=3D"yes" ?&gt;<br>
	&lt;?rfc toc=3D"yes"?&gt;<br>
	&lt;?rfc tocdepth=3D"4"?&gt;<br>
	&lt;?rfc symrefs=3D"yes" ?&gt;<br>
	&lt;?rfc sortrefs=3D"yes" ?&gt;<br>
	&lt;?rfc compact=3D"yes" ?&gt;<br>
	&lt;?rfc subcompact=3D"no" ?&gt;<br>
<br>
	&lt;rfc<br>
		ipr=3D'trust200902'<br>
		category=3D'exp'<br>
		submissionType=3D'IRTF'<br>
		docName=3D'draft-oran-icnrg-reflexive-forwarding-00'<br>
		xml:lang=3D'en' xmlns:xi=3D"<a href=3D"https://www.w3.org/2001/XInclude=
" style=3D"color:#BBB">https://www.w3.org/2001/XInclude</a>"&gt;<br>
<br>
	&lt;front&gt;<br>
		&lt;seriesInfo name=3D'Internet-Draft'<br>
value=3D'draft-oran-icnrg-reflexive-forwarding-00'/&gt;<br>
	    &lt;title abbrev=3D'ICN Reflexive Forwarding'&gt;Reflexive Forwardin=
g for<br>
CCNx and NDN Protocols<br>
	    &lt;/title&gt;<br>
<br>
I get:<br>
<br>
		xml2rfc draft-oran-icnrg-reflexive-forwarding.xml<br>
		Error: Unable to validate the XML document:<br>
draft-oran-icnrg-reflexive-forwarding.xml<br>
		 &lt;string&gt;: Line 23: No declaration for attribute xmlns:xi of elem=
ent<br>
rfc<br>
		 &lt;string&gt;: Line 25: Element front content does not follow the DTD=
,<br>
expecting (title , author+ , date , area* , workgroup* , keyword* ,<br>
abstract? , note*), got (seriesInfo title author author date area<br>
workgroup keyword keyword abstract )<br>
		 &lt;string&gt;: Line 81: Element section content does not follow the D=
TD,<br>
expecting ((t | figure | texttable | iref)* , section*), got (name t )<br=
>
		 &lt;string&gt;: Line 81: Element section does not carry attribute titl=
e<br>
		 &lt;string&gt;: Line 81: No declaration for element name<br>
		 &lt;string&gt;: Line 85: Element section content does not follow the D=
TD,<br>
expecting ((t | figure | texttable | iref)* , section*), got (name t )<br=
>
		 &lt;string&gt;: Line 85: Element section does not carry attribute titl=
e<br>
		 &lt;string&gt;: Line 85: No declaration for element name<br>
		 &lt;string&gt;: Line 94: Element section content does not follow the D=
TD,<br>
expecting ((t | figure | texttable | iref)* , section*), got (name t<br>
section section )<br>
		 &lt;string&gt;: Line 94: Element section does not carry attribute titl=
e<br>
		 &lt;string&gt;: Line 94: No declaration for element name<br>
		 &lt;string&gt;: Line 97: Element section content does not follow the D=
TD,<br>
expecting ((t | figure | texttable | iref)* , section*), got (name t<br>
table )<br>
		 &lt;string&gt;: Line 97: Element section does not carry attribute titl=
e<br>
		 &lt;string&gt;: Line 97: No declaration for element name<br>
		 &lt;string&gt;: Line 98: No declaration for attribute keepWithNext of<=
br>
element t<br>
		 &lt;string&gt;: Line 99: No declaration for element table<br>
		 &lt;string&gt;: Line 99: No declaration for attribute title of element=
<br>
table<br>
<br>
Clue bat please?<br>
<br>
DaveO<br>
<br>
<br>
<br>
_______________________________________________<br>
xml2rfc mailing list<br>
xml2rfc@ietf.org<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/xml2rfc" style=3D"color:=
#BBB">https://www.ietf.org/mailman/listinfo/xml2rfc</a><br>
</p>
</blockquote></blockquote><p dir=3D"auto">DaveO<br>
</p>
</blockquote></blockquote><p dir=3D"auto">DaveO<br>
</p>
</blockquote></blockquote></blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">DaveO</p>
</div>
</div></div></blockquote>
<div style=3D"white-space:normal">
<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
</blockquote><blockquote style=3D"border-left:2px solid #777; color:#777;=
 margin:0 0 5px; padding-left:5px"><p dir=3D"auto">______________________=
_________________________<br>
xml2rfc mailing list<br>
xml2rfc@ietf.org<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/xml2rfc" style=3D"color:=
#777">https://www.ietf.org/mailman/listinfo/xml2rfc</a></p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">DaveO</p>
</div>
</div>
</body>
</html>

--=_MailMate_F8600329-138A-4ACF-A128-F4AAB0A6996C_=--

--=_MailMate_E479A2A2-0EE9-48DC-8C2E-D36E5D3ADC9B_=
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename=signature.asc
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iQJJBAEBAgAzFiEEroJBCc9z/EJK1xs/eu0uvThCv/AFAl4mk1IVHGRhdmVvcmFu
QG9yYW5kb20ubmV0AAoJEHrtLr04Qr/wSOsP/0x+Rx0i8AWUYELJdSoGXDN6LGfH
+OfIEKlfs1vEnYyPjv00VK+9RcxZm6UbP0UJZEl3ia9S4TBXn7FwVvTe+TbMtjW4
wZ69EkmxWD8RsohzaV19/WHNM7vbcUmhBEyV3jfRQzY8Iug/JUs1dDN7GEQEz/bd
OLVrjmb0LCdJtJHISNt8gllCNBaHal3ik5PChXfwajlDLRpEz0Wsj6TErDhZM7/U
Hfm+DpNA3GKTpJhJP3PRtsa9wZKrzyIGknskU7Yo5a265tZoOhEq1bXKLcoG9t9K
IjRXC8JHFeLU6/oiFf/xbMNuv1SE38VEsesOovi+o5zYq5i88z6U5+Y9W0pDq6oD
l2k0tfgHUfM5pePSG12L2gW/awyoQMcbRIACdC6MCtYNkXUoe09AQ8dXCe93Uz0k
jNWSR33i2IW/JX3YuFr1pjnfHbOaJ8+INnvjGetVfcrRA1QEOWeNMpZ1Gi2zXjDs
MsVJsxuxzu8rXGrq9Gegy+zyzS140Jjf0aIlahpFBlqOOnFchQH3/Sj1o9OMqFPl
IT0Z0ZlMWzOTczjCJK7VvLzmBKr/RBSkjlhmUAqe4ok0DnOlQJj4EpL758eZ50BY
/GSM1tZCAcuY1aGOO55Mk3/z2chs+LDGnE3ljfpszzkT6iRFirEYNV7b3yR2XiKc
k4745PGdYVYr5LkE
=5W/g
-----END PGP SIGNATURE-----

--=_MailMate_E479A2A2-0EE9-48DC-8C2E-D36E5D3ADC9B_=--


From nobody Mon Jan 20 22:13:46 2020
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 25AC112008B for <xml2rfc@ietfa.amsl.com>; Mon, 20 Jan 2020 22:13:45 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 1J9iBr6Mn1ME for <xml2rfc@ietfa.amsl.com>; Mon, 20 Jan 2020 22:13:43 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 327A4120071 for <xml2rfc@ietf.org>; Mon, 20 Jan 2020 22:13:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1579587195; bh=Zbs+v79e9b3uMd/LP1TyPnVuPRFoiFoacOrc45iRdaA=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=CREQvfLiRoNkyMZDvO/iIc2hUD3Udt4zPNG2VTNN+wT86Fm6/5B6399u0rqK3yWCq FgyhoLvsAezV/tC0qRoMaZVloflFq9fQw8MPUMDq9CT+XEY7A/VlOd+v5VJ/xHYBAf ui2okSBhY0AG5pR972v2ISOeOCHFH303Z1jg82Lw=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([217.251.133.39]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MvK0R-1jkn2w1O5p-00rJqy; Tue, 21 Jan 2020 07:13:15 +0100
To: "David R. Oran" <daveoran@orandom.net>, Henrik Levkowetz <henrik@levkowetz.com>
Cc: xml2rfc@ietf.org
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net> <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com> <DA4F22F5-5A43-4671-B69B-EDF61F976623@orandom.net> <61971d80-1c1e-bdf7-a986-0cfe9de157e6@levkowetz.com> <6C8FDE4E-88F8-4862-A9CC-3D1E9B0DCD4C@orandom.net> <fe468ed5-3d9b-88b2-8403-f8482bb1f55b@levkowetz.com> <647a593e-8104-0a59-bd0b-fb377f49201e@levkowetz.com> <A6C1B0DF-EAE0-46DC-9539-F56A3192E336@orandom.net>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <2d9a0eb4-b565-42a7-6f69-9a80bd7a6ea1@gmx.de>
Date: Tue, 21 Jan 2020 07:13:13 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <A6C1B0DF-EAE0-46DC-9539-F56A3192E336@orandom.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:nZ44cqBc/lwprWJ91G6O3ZdB8LP8gDrxYyjAtlKrW6cM7TRj5eG u69Gkufgin99VmAjr2mLPrZoWOKaPAMDFCNjbCMQpiI8KKEOQ0IALkq8nIGeUrmyvEKH2YG dms3mYh0PlD8swJzUdcX9cuDcl7KhxgYHtSbga7LH22AKcoVqBoxnt+xS8PUEzRoGP4CYDO gpEQRZmkg9p/UT4zbY1hg==
X-UI-Out-Filterresults: notjunk:1;V03:K0:kT4Y3+NtMA0=:FhSPEVDbtqHkMxfap7fZuy NwcjteAaS1R/3efnSENAhIFXKkqNelbIbX4yIERfdgShw3M8pa9F7XrJ7gMlhMzbQ4YuhIPsc 9s9r+dd0PgOjwKtWlJpDwUM8NSfFaqdJIhdFq5TpuEVeu64eakaoXl0VGM6cQjPqRFvAcv3Pz KfiRWcK+dQOcOZel4Img16EDLTYH9WlIz771rD6VlDcluy+Y8/4RSDGPM71YQGJ/MW46FnzcL 2xE3dk8QXlVsQesFi541hmXnAWNh5Do4zLO0ZKHZ/dQdCpHzyYM7vWpcpMcdZjBdQ5m0SNJP5 akKJiSWBYMHzYSgKBxYl5wK7kyxDIFMlYU/YbD6z7LuXPIYkvKaKvFNe4CobbwlBFXh809PKb shfmvfEgwuiJrW/lSNpLTjFDZ4MADEsybbtflYIilD77aEEe2r5rrhglFdU9W3yalIz9T3Ibc aKqSh6f2oEywPblW/7rl4xdhBhnjMgOF5GcoEWrtMvS1v/tups5vD1cAmHRiTAqtRIzu12Sxw KXAuj2feEL0JTnRARJyXRtIuLreozuDaUkleM5e7CBMl/C6DzOx+9llRiTejwYQ2SavK2FKZO xoBJ7y056y1i2s7i12mgCkn7SCDe+WPiIi9+DbPdSUMN2kvhYzMHr+N/JRGrqR1fTaB/TUf/4 AlUSNW4lMTeu3EZNVEaYE3cKhfEGC66VY6F9zr6r9keRa4jQjypmmCpGQooF9ucNdXRIig9We 67T0jYk7Dmt9JICmQPOdXUts60QjrpoyhBh0/4l0z3pjccgVtoEwRAk3IeDNoIKwv1Tn+lN0W aKqo9Mht2fWoEQX50dZBxC5DGOuncr5SAYT9q2BwxRYSqwuFhXDbhydVGFKHCsYtg59IVF9dL Zl37MvdfETXUeBulZz4sZGq0QA7xvQBLPZoIXM9qnGFJgzA0x1dt19v5UIrDIJFhR43lCJD8+ Llc/nWlVoM7nIQFXzYcqUMfN/4I3owj5pcyPrw8m3kPue004Q7Gdq9qkabYRU4w/6oF/SHyAA m4ueYu4h4EnLIodj1j2y/RyzmioDu1/tYPrtvHRRqdzRG7czUqM5lijhD0srQkoaaXJDacO38 wY/i2Fwfv9fcJi2+AalPpCnhclWY0kpSGp8OBZCI9dtNyW30tsi6zX0BDF6zJLf/fw+hi+BW/ TVlKogy3CsACrkVg0eMVmjt1jV5jrfbc6umSqO60ebfH2aVyofH605hyRK9XwAWCvQF4hopHj JrEm5SS0fC5Pw3rFuANMthZFra6LJXWUQU6hhWXugN/6AhoN50+BXEsyPnxI=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/H3vhLvxQCaDT46BEToAUt4jcxTg>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
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: Tue, 21 Jan 2020 06:13:45 -0000

On 21.01.2020 06:51, David R. Oran wrote:
 > ...
> Thanks a ton for the help. I puzzled around some more in the FAQ and
> RFC7991, getting rid of suspicious V2-ish stuff that used to be adorning
> all my draft source files and replacing the essentials with the right V3
> constructs. However, among those was not the xmlns:ni, which I had
> copied from one of the examples in draft-hoffman-rfcexamples. Once that
> was gone the crash disappeared.
 > ...

Extra namespace declarations should not cause any problems. They are
allowed in XML.

Best regards, Julian


From nobody Mon Jan 20 22:15:22 2020
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 106FB120052 for <xml2rfc@ietfa.amsl.com>; Mon, 20 Jan 2020 22:15:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 (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 Mt-XOpfgzU10 for <xml2rfc@ietfa.amsl.com>; Mon, 20 Jan 2020 22:15:18 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 77B01120045 for <xml2rfc@ietf.org>; Mon, 20 Jan 2020 22:15:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1579587286; bh=1NzH5EbpHrod6av5M8zqZkDt/ADY3qvkn0B6fe7OPBk=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=OYpMJPpheqbpIbmETv0Blrn8UUO9xnpg7IoegCh7U0g1dULEI+9zduBvaRMp+B3oJ /9Z8s9ravfKdykZUbd6GedKrXu5o2q/AEsKeq/ndpdgjqOqtagvECpnK/PWsVbQ5Ue 4nQgcFH82S4d1FTqmRIBpPD0KULttvIaCUFJ7dSM=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([217.251.133.39]) by mail.gmx.com (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1N79uI-1jhEde3Juu-017YRm; Tue, 21 Jan 2020 07:14:46 +0100
To: "David R. Oran" <daveoran@orandom.net>, Henrik Levkowetz <henrik@levkowetz.com>
Cc: xml2rfc@ietf.org
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net> <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com> <DA4F22F5-5A43-4671-B69B-EDF61F976623@orandom.net> <61971d80-1c1e-bdf7-a986-0cfe9de157e6@levkowetz.com> <6C8FDE4E-88F8-4862-A9CC-3D1E9B0DCD4C@orandom.net> <fe468ed5-3d9b-88b2-8403-f8482bb1f55b@levkowetz.com> <647a593e-8104-0a59-bd0b-fb377f49201e@levkowetz.com> <A6C1B0DF-EAE0-46DC-9539-F56A3192E336@orandom.net> <C49A9B95-1196-4439-8021-31ECDC676813@orandom.net>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <e8173c00-2bed-0561-e3b2-4b6f06bc08f9@gmx.de>
Date: Tue, 21 Jan 2020 07:14:45 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <C49A9B95-1196-4439-8021-31ECDC676813@orandom.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:87CmTfv2ZNyedrZSPq1sGJcN2DglOSnksoEGVrrHuEWkSpHbePa 80c4T/J4FO0WliVO5F5hQS9YHvuY++2kG6T0zqj5EcBLzESXT5g/PKhpB3h21Mjf8FLo0Rq VGRmZNjekQMkHzcnjpDCN0HSlNybcRNbYL4XqJuZCu6QX9YyZirqJYX61S3HBUEpnaw8gUJ q1iDC1CLEzRjLcVXM4/Og==
X-UI-Out-Filterresults: notjunk:1;V03:K0:10DVt5A+NxU=:C1KYCx43dh+KRmu4eIAcFd g3kqn+fCHrIKzaCIumoHSpyFutULpPP1Nguaa+LGC0RrwXv5eGJm4HiaJ9RoX3zwOo3TIOUDi hIU1dJ/m744FNoWddiKa/fiTiwmIf47WtLLt80Yz7C1HEvleewWQD8JklkmWr7i4ApPQMWG6n eR361oxpuRNlpIAnLgcXZ90uS74BONGeEaJ46rLGZgpSju/4isA50nX+vOjUpN+SvTTtTmM+4 tn7o8BOsJNdOvPa8r+cIWtnZs6rvkT/DYw+mFIRN9K6fjllsFFfPS5E34XZYcF+KMvkhVpE0A GsN0QewPmjJtoPN/HpXNGljvBGkMC6SVE22g4V9BJTEN/m4W0Zj4o5dr4W0h0j129Xhy5jXaK kVEEsbjtQySJLMaIm7gLqxa6ExPuX6Hshp0ntYwCGntXbeRYDzVb37iZ4xSNFHyPrb7CO2q38 GWeyWbTBSql7Tn+g98XjdrbC385uaO3iOgIbWskoFElImmAYC7jLX3LlFPH9TfUp0Ls96HT+A abvlCg+bC0wtnt+hLBX+yZrpJCBJjwKMspmWk1rallBHgFs3dXDkp3duf61tzZLmFGqfsZkac YBpuF+XnzFy0kf8MiYXHGQb8033rXpbu3IFgx6VbRvKWc2T+k8BRRp4zvqohynyEXkP1LHasd QXp9ePuxtE3GTZQ9hG+7QALYfbzaVNtGCDo/+jJnRe1ytxZk+dJUkHeqPuKEdzE/tSDmao96e YxDhOS1v8IugzsDnPReCHLkQum+s4dOnkomzmqZY+AMBjnjWrUFm4M1t85zX7x2UeLPeaT8ze 4c2GjzEHnpw3xPKQGxWxodCvcwZmLRP1JrFYxM+pzEevNV1+O+uyNnXHv6bIdT+3pvWH464dc omR4cC5qlV/TT9V0RkrecgsyK/0imVHMyB+Kk5lemjz9w7K2ZDRy42kXKpoPifgH09jk6Ipeh ZV9GG7F1qYVCtA6bZqxnqQxdUTpgkXb+0obAXs9uYXkYIaowdcbw51XSAaZiIb5+8XWao9KWM yuvb1g8STrtv5QPYs3yJJNp/OFKGsoiQ5yyP5aGeAeypQu4be3O1oBeKSOrx+HDyi0lgJylM2 Pp69qvfKWcRtOiohNiN1J0g/Uv0GsVvsVsIE0Y9bkvor48Y5HM2PFTHM8ZWUh0Q55khFUtbSm N2BTr5ve8zofFMS+2hxtf6FRYk6gH1taA1AJrrfaZPprVsm/ehg+OhrgWUcHRillnPCtu79bm 29tntw2gh+vX0vCAaEpdJhN/3gkDGK0a/i/zXyERCQBUMr87erjG3nO6cevg=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/tYCkIO24nXfKtbs37MpTDU_3puE>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
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: Tue, 21 Jan 2020 06:15:21 -0000

On 21.01.2020 06:59, David R. Oran wrote:
> Oh, one more thing I noticed that puzzled me briefly=E2=80=A6
>
> RFC7991 says:
>
> |2.45.3. "docName" Attribute Deprecated; instead, use the "value"
> attribute in <seriesInfo>. |
>
> but your draft won=E2=80=99t compile unless you include it as an attribu=
te of
> the <rfc> element.
> ...

We currently do not have a spec that describes v3-as-implemented.

You will *also* have to look at
<https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-not=
es-10>,
and even that will not give you the full picture.

Best regards, Julian


From nobody Tue Jan 21 00:26:42 2020
Return-Path: <henrik@levkowetz.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 7D5C7120071 for <xml2rfc@ietfa.amsl.com>; Tue, 21 Jan 2020 00:26:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 yFi0RmRspBrZ for <xml2rfc@ietfa.amsl.com>; Tue, 21 Jan 2020 00:26:35 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 391B9120043 for <xml2rfc@ietf.org>; Tue, 21 Jan 2020 00:26:35 -0800 (PST)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:60991 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1itorm-0006Uz-1t; Tue, 21 Jan 2020 00:26:34 -0800
To: "David R. Oran" <daveoran@orandom.net>
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net> <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com> <DA4F22F5-5A43-4671-B69B-EDF61F976623@orandom.net> <61971d80-1c1e-bdf7-a986-0cfe9de157e6@levkowetz.com> <6C8FDE4E-88F8-4862-A9CC-3D1E9B0DCD4C@orandom.net> <fe468ed5-3d9b-88b2-8403-f8482bb1f55b@levkowetz.com> <647a593e-8104-0a59-bd0b-fb377f49201e@levkowetz.com> <A6C1B0DF-EAE0-46DC-9539-F56A3192E336@orandom.net>
Cc: xml2rfc@ietf.org
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <43f689a4-7bc5-5e8c-0ca6-0ca785a77c8e@levkowetz.com>
Date: Tue, 21 Jan 2020 09:26:22 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <A6C1B0DF-EAE0-46DC-9539-F56A3192E336@orandom.net>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="mwuEH3AIg7RGBhXfqOxGCJU6pf4u2cO1r"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: xml2rfc@ietf.org, daveoran@orandom.net
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/vXmNxD-AikyIDDuPtvh34sBM0ak>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
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: Tue, 21 Jan 2020 08:26:40 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--mwuEH3AIg7RGBhXfqOxGCJU6pf4u2cO1r
Content-Type: multipart/mixed; boundary="OiJ8DJJ1Lkaa3fWsQ0qaBSaI9jQOPrCeF";
 protected-headers="v1"
From: Henrik Levkowetz <henrik@levkowetz.com>
To: "David R. Oran" <daveoran@orandom.net>
Cc: xml2rfc@ietf.org
Message-ID: <43f689a4-7bc5-5e8c-0ca6-0ca785a77c8e@levkowetz.com>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net>
 <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com>
 <DA4F22F5-5A43-4671-B69B-EDF61F976623@orandom.net>
 <61971d80-1c1e-bdf7-a986-0cfe9de157e6@levkowetz.com>
 <6C8FDE4E-88F8-4862-A9CC-3D1E9B0DCD4C@orandom.net>
 <fe468ed5-3d9b-88b2-8403-f8482bb1f55b@levkowetz.com>
 <647a593e-8104-0a59-bd0b-fb377f49201e@levkowetz.com>
 <A6C1B0DF-EAE0-46DC-9539-F56A3192E336@orandom.net>
In-Reply-To: <A6C1B0DF-EAE0-46DC-9539-F56A3192E336@orandom.net>

--OiJ8DJJ1Lkaa3fWsQ0qaBSaI9jQOPrCeF
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Dave,

On 2020-01-21 06:51, David R. Oran wrote:
> Thanks a ton for the help. I puzzled around some more in the FAQ and
> RFC7991, getting rid of suspicious V2-ish stuff that used to be
> adorning all my draft source files and replacing the essentials with
> the right V3 constructs. However, among those was not the xmlns:ni,
> which I had copied from one of the examples in
> draft-hoffman-rfcexamples. Once that was gone the crash disappeared.
>=20
> One unsolicited piece of advice is that in addition to the FAQ and
> RFC7991 itself, some templates in native V3 for people to start from
> would have saved me the pain you see in this thread. The example in
> Paul Hoffman=E2=80=99s draft (which I found googling =E2=80=9Cxml2rfc v=
3 examples=E2=80=9D of
> course) was generated using the converter and wound up being
> extremely misleading for a =E2=80=9Cnative=E2=80=9D V3 source file.
>=20
> Best, DaveO.
>=20
> P.S. I did get another crash when I put my own <date> element in the
> <front> element as per =E2=80=9C<date month=3D'January' year=3D'2020' /=
> When I
> let the converter insert the date in the output itself, no problem.

Thanks for the data and traceback; will fix the issue in the next release=
 :-)

And yes, having v3 templates would be helpful.  I'll see if I can fix tha=
t
too.  Where would you normally grab a template?

	Henrik

>=20
> 	xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
> 	draft-oran-icnrg-reflexive-forwarding.xml(63): Warning: The document d=
ate (2020-01-01) is more than 3 days away from today's date
> 	Traceback (most recent call last):
> 	  File "/usr/local/bin/xml2rfc", line 8, in <module>
> 	    sys.exit(main())
> 	  File "/usr/local/lib/python2.7/site-packages/xml2rfc/run.py", line 6=
20, in main
> 	    xmlrfc.tree =3D prep.prep()
> 	  File "/usr/local/lib/python2.7/site-packages/xml2rfc/writers/preptoo=
l.py", line 342, in prep
> 	    func(e, e.getparent())
> 	  File "/usr/local/lib/python2.7/site-packages/xml2rfc/writers/preptoo=
l.py", line 1123, in boilerplate_insert_status_of_memo
> 	    exp =3D datetime.date(year=3Dyear, month=3Dmonth, day=3Dday) + dat=
etime.timedelta(days=3D185)
> 	TypeError: an integer is required
>=20
>=20
> On 20 Jan 2020, at 18:20, Henrik Levkowetz wrote:
>=20
>> Hi again David,
>>
>> The issue is triggered by the code trying to insert the XInclude names=
pace
>> if it isn't defined, but your file defines the 'xi' namespace prefix n=
ot
>> as the XInclude namespace (http://www.w3.org/2001/XInclude), but as so=
mething
>> that's very close to it:  (https://www.w3.org/2001/XInclude).  The cod=
e
>> then tries to insert xmlns:xi=3D"http://www.w3.org/2001/XInclude" whic=
h fails.
>>
>> The code should handle this better.  It's clearly a bug.  Menawhile, i=
f you
>> change the https:// to http:// in the xmlns:xi attribute value, you sh=
ould
>> be able to get further.
>>
>> Once you've fixed that, you'll find that using XInclude doesn't permit=

>> any inaccuracies in the specification of the href, so you'll have to a=
dd
>> https:// to the <xi:include/> entries around line 140.  The v2 process=
or
>> is much more forgiving about this, but the XInclude specification does=
n't
>> permit a processor to be lenient in the manner xml2rfc is for v2 input=
=2E
>>
>> Then you'll find that <tbody> isn't optional in v3 the way it is in ht=
ml,
>> and other issues that should be easier to sort out.
>>
>>
>> Best,
>>
>> 	Henrik
>>
>> On 2020-01-20 23:59, Henrik Levkowetz wrote:
>>> Hi David,
>>>
>>> On 2020-01-20 23:25, David R. Oran wrote:
>>>> Thanks much. See below.
>>>
>>> Ack.  Will reply further once I've looked at the xml.  One point inli=
ne
>>> now:
>>>
>>>> On 20 Jan 2020, at 16:25, Henrik Levkowetz wrote:
>>>>
>>>>> Hi David,
>>>>>
>>>>> On 2020-01-20 22:03, David R. Oran wrote:
>>>>>> On 20 Jan 2020, at 15:10, Henrik Levkowetz wrote:
>>>>>>
>>>>>>> Hi David,
>>>>>>>
>>>>>>> You should simply remove "<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>" if=
 your
>>>>>>> <rfc/> element contains the "version=3D'3'" attribute.
>>>>>>>
>>>>>> If I do that xml2rfc crashes (both the one on my machine and the w=
eb tool:
>>>>>
>>>>> Oh, wow.  Ok, I'll fix that in the next release.  Could you send th=
e full
>>>>> xml file, please?  It's not obvious from your snippet where the sup=
erfluous
>>>>> other definition of xmlns:xi is.
>>>>>
>>>> attached.
>>>>
>>>>> Now, you say that instead of trying the converter, you stared out r=
ight
>>>>> away with v3 syntax, but neither the DOCTYPE above, nor the <?rfc .=
=2E. ?>
>>>>> PIs visible in your snippet are appropriate for a v3 document.  Did=
 you
>>>>> grab a v2 template to start with?  I think really going to lead you=
 into
>>>>> a number of problems if you start with a v2 template and declare it=
 to be
>>>>> v3.
>>>>>
>>>> No, I started from scratch=E2=80=A6but cut a pasted a few things fro=
m an
>>>> earlier draft after checking (I thought correctly) that I was
>>>> following the strict V3 definitions. Possibly not=E2=80=A6
>>>>
>>>> For yucks, I got rid of all that and started right off with the <rfc=
>
>>>> element and xml2rfc still crashes.
>>>>
>>>>> Using the v2v3 converter on a v2 document, even on a v2 template, o=
n the
>>>>> other hand, should give you a proper v3 starting point, without the=
 issues
>>>>> you've run into so far.
>>>
>>>> I believe that. But the output of the converter on
>>>> draft-hoffman-rfcexamples-latest left the DOCTYPE declaration in
>>>> there=E2=80=A6
>>>
>>> I think you'll find that the DOCTYPE doesn't mention a dtd in that ca=
se,
>>> just a file which (if available) provides entity definitions.
>>>
>>> More in a moment.
>>>
>>>
>>> Best regards,
>>>
>>> 	Henrik
>>>
>>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>> 	Henrik
>>>>>
>>>>>>
>>>>>> xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
>>>>>> Traceback (most recent call last):
>>>>>>   File "/usr/local/bin/xml2rfc", line 8, in <module>
>>>>>>     sys.exit(main())
>>>>>>   File "/usr/local/lib/python2.7/site-packages/xml2rfc/run.py", li=
ne 612, in main
>>>>>>     xmlrfc =3D parser.parse(remove_comments=3DFalse, quiet=3DTrue,=
 add_xmlns=3DTrue)
>>>>>>   File "/usr/local/lib/python2.7/site-packages/xml2rfc/parser.py",=
 line 548, in parse
>>>>>>     for action, element in context:
>>>>>>   File "src/lxml/iterparse.pxi", line 208, in lxml.etree.iterparse=
=2E__next__ (src/lxml/lxml.etree.c:148588)
>>>>>>   File "<string>", line 22
>>>>>> lxml.etree.XMLSyntaxError: Attribute xmlns:xi redefined, line 22, =
column 59
>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> 	Henrik
>>>>>>>
>>>>>>> On 2020-01-20 21:00, David R. Oran wrote:
>>>>>>>> I have a new Internet Draft to write, so I decided to bite the b=
ullet
>>>>>>>> and do it in V3. Rather than write in V2 and try the converter, =
I
>>>>>>>> started out right away with V3 syntax. I didn=E2=80=99t get very=
 far. I tried
>>>>>>>> both the most recent xml2rfc by installing it on my machine, and=
 the web
>>>>>>>> tool and got identical errors.
>>>>>>>>
>>>>>>>> If I follow the described syntax in RFC7991, the RFC Editor FAQ =
in
>>>>>>>> https://ftp.ripe.net/rfc/v3test/FAQ-2019-02.html and the example=
 in
>>>>>>>> draft-hoffman-rfcexamples-latest as below:
>>>>>>>>
>>>>>>>> 	<?xml version=3D"1.0" encoding=3D"US-ASCII"?>
>>>>>>>> 	<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>
>>>>>>>>
>>>>>>>> 	<?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?>
>>>>>>>> 	<?rfc strict=3D"yes" ?>
>>>>>>>> 	<?rfc toc=3D"yes"?>
>>>>>>>> 	<?rfc tocdepth=3D"4"?>
>>>>>>>> 	<?rfc symrefs=3D"yes" ?>
>>>>>>>> 	<?rfc sortrefs=3D"yes" ?>
>>>>>>>> 	<?rfc compact=3D"yes" ?>
>>>>>>>> 	<?rfc subcompact=3D"no" ?>
>>>>>>>> 	<rfc
>>>>>>>> 		version=3D=E2=80=983=E2=80=99
>>>>>>>> 		ipr=3D'trust200902'
>>>>>>>> 		category=3D'exp'
>>>>>>>> 		submissionType=3D'IRTF'
>>>>>>>> 		docName=3D'draft-oran-icnrg-reflexive-forwarding-00'
>>>>>>>> 		xml:lang=3D'en' xmlns:xi=3D"https://www.w3.org/2001/XInclude">=

>>>>>>>>
>>>>>>>> 	<front>
>>>>>>>> 		<seriesInfo name=3D'Internet-Draft'
>>>>>>>> value=3D'draft-oran-icnrg-reflexive-forwarding-00'/>
>>>>>>>> 	    <title abbrev=3D'ICN Reflexive Forwarding'>Reflexive Forwar=
ding for
>>>>>>>> CCNx and NDN Protocols
>>>>>>>> 	    </title>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> I get
>>>>>>>>
>>>>>>>> 	% xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
>>>>>>>> 	Incompatible schema information: found "rfc2629.dtd" in <DOCTYP=
E> of a
>>>>>>>> version 3 file.
>>>>>>>>
>>>>>>>> If I leave off the =E2=80=9Cversion=3D=E2=80=983=E2=80=99, as be=
low
>>>>>>>>
>>>>>>>> 	<?xml version=3D"1.0" encoding=3D"US-ASCII"?>
>>>>>>>> 	<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>
>>>>>>>> 	<?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?>
>>>>>>>> 	<?rfc strict=3D"yes" ?>
>>>>>>>> 	<?rfc toc=3D"yes"?>
>>>>>>>> 	<?rfc tocdepth=3D"4"?>
>>>>>>>> 	<?rfc symrefs=3D"yes" ?>
>>>>>>>> 	<?rfc sortrefs=3D"yes" ?>
>>>>>>>> 	<?rfc compact=3D"yes" ?>
>>>>>>>> 	<?rfc subcompact=3D"no" ?>
>>>>>>>>
>>>>>>>> 	<rfc
>>>>>>>> 		ipr=3D'trust200902'
>>>>>>>> 		category=3D'exp'
>>>>>>>> 		submissionType=3D'IRTF'
>>>>>>>> 		docName=3D'draft-oran-icnrg-reflexive-forwarding-00'
>>>>>>>> 		xml:lang=3D'en' xmlns:xi=3D"https://www.w3.org/2001/XInclude">=

>>>>>>>>
>>>>>>>> 	<front>
>>>>>>>> 		<seriesInfo name=3D'Internet-Draft'
>>>>>>>> value=3D'draft-oran-icnrg-reflexive-forwarding-00'/>
>>>>>>>> 	    <title abbrev=3D'ICN Reflexive Forwarding'>Reflexive Forwar=
ding for
>>>>>>>> CCNx and NDN Protocols
>>>>>>>> 	    </title>
>>>>>>>>
>>>>>>>> I get:
>>>>>>>>
>>>>>>>> 		xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
>>>>>>>> 		Error: Unable to validate the XML document:
>>>>>>>> draft-oran-icnrg-reflexive-forwarding.xml
>>>>>>>> 		 <string>: Line 23: No declaration for attribute xmlns:xi of e=
lement
>>>>>>>> rfc
>>>>>>>> 		 <string>: Line 25: Element front content does not follow the =
DTD,
>>>>>>>> expecting (title , author+ , date , area* , workgroup* , keyword=
* ,
>>>>>>>> abstract? , note*), got (seriesInfo title author author date are=
a
>>>>>>>> workgroup keyword keyword abstract )
>>>>>>>> 		 <string>: Line 81: Element section content does not follow th=
e DTD,
>>>>>>>> expecting ((t | figure | texttable | iref)* , section*), got (na=
me t )
>>>>>>>> 		 <string>: Line 81: Element section does not carry attribute t=
itle
>>>>>>>> 		 <string>: Line 81: No declaration for element name
>>>>>>>> 		 <string>: Line 85: Element section content does not follow th=
e DTD,
>>>>>>>> expecting ((t | figure | texttable | iref)* , section*), got (na=
me t )
>>>>>>>> 		 <string>: Line 85: Element section does not carry attribute t=
itle
>>>>>>>> 		 <string>: Line 85: No declaration for element name
>>>>>>>> 		 <string>: Line 94: Element section content does not follow th=
e DTD,
>>>>>>>> expecting ((t | figure | texttable | iref)* , section*), got (na=
me t
>>>>>>>> section section )
>>>>>>>> 		 <string>: Line 94: Element section does not carry attribute t=
itle
>>>>>>>> 		 <string>: Line 94: No declaration for element name
>>>>>>>> 		 <string>: Line 97: Element section content does not follow th=
e DTD,
>>>>>>>> expecting ((t | figure | texttable | iref)* , section*), got (na=
me t
>>>>>>>> table )
>>>>>>>> 		 <string>: Line 97: Element section does not carry attribute t=
itle
>>>>>>>> 		 <string>: Line 97: No declaration for element name
>>>>>>>> 		 <string>: Line 98: No declaration for attribute keepWithNext =
of
>>>>>>>> element t
>>>>>>>> 		 <string>: Line 99: No declaration for element table
>>>>>>>> 		 <string>: Line 99: No declaration for attribute title of elem=
ent
>>>>>>>> table
>>>>>>>>
>>>>>>>> Clue bat please?
>>>>>>>>
>>>>>>>> DaveO
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> xml2rfc mailing list
>>>>>>>> xml2rfc@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>>>>>>>
>>>>>>
>>>>>> DaveO
>>>>>>
>>>>
>>>> DaveO
>>>>
>>>
>=20
> DaveO
>=20


--OiJ8DJJ1Lkaa3fWsQ0qaBSaI9jQOPrCeF--

--mwuEH3AIg7RGBhXfqOxGCJU6pf4u2cO1r
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl4mta8ACgkQTptXS4+7
Fxr+gBAAuwx/SQjXBTawbGUKdE1SoVP8Aheq/pRALo10laLFlsx+GJHIaYpYYi9z
NCMpMsAONp8f7XUE6+dL3wMCb/yOaNB6R0sLnNAVkLARV7GmP1bO+kJV+rdWoGyR
EfV69SaQ4GWvy8Db5wdjAC09WC40909EMII7DUhJQzjyXB0dPjEay2Aj1GIk32e3
DULA8acVwTtYZzvjHBgafzCRiN83TnbOCSExH4HWP4cKRfGwunDPBuKWtXy/qF3N
LWM6NwVWmu3kpk5XJFrcnPBMijNK6IwcY/XtXygpxoUY5J61ZmVD8zYY0xbIINR9
GNERIGmd7ZQ1ukiip18lvPuR4hbQSffFCc2xaX+VcDR31XNRop1GbZy2NaeGchGN
k6Rst/6fKRaaD0a3aLEtC6MU91ZAthqP2ULk3lgN3ABnmQAckR6T0wKeZw+LH2aG
jDzEeqJPyNxARwWTObVET412GH5RRSsJ4rt2rJ+CiuFlUarNFXxmgdns5aAeSgGj
f8lx6XnsSnqNZ7SxEeZvUHOgzttNF35tPumhXNxI3C3iL9WPWqujase4xkWVQ66S
pU9thje/QznbWtRI04TZkj37l/Jv1uHEI6siXh5TH2V43o8E3As5sbYlWgJfPgVt
MPJ3pLZ1bA4n0n4C4Kv0Q8aKhQyTt2q0KQvilwDiAHzNlqJE3ZU=
=9BvS
-----END PGP SIGNATURE-----

--mwuEH3AIg7RGBhXfqOxGCJU6pf4u2cO1r--


From nobody Tue Jan 21 00:28:12 2020
Return-Path: <henrik@levkowetz.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 7F624120043 for <xml2rfc@ietfa.amsl.com>; Tue, 21 Jan 2020 00:28:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 7HpvL4_70FSk for <xml2rfc@ietfa.amsl.com>; Tue, 21 Jan 2020 00:28:08 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B059120071 for <xml2rfc@ietf.org>; Tue, 21 Jan 2020 00:28:08 -0800 (PST)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:61006 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1itotH-0008JZ-U3; Tue, 21 Jan 2020 00:28:08 -0800
To: "David R. Oran" <daveoran@orandom.net>
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net> <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com> <DA4F22F5-5A43-4671-B69B-EDF61F976623@orandom.net> <61971d80-1c1e-bdf7-a986-0cfe9de157e6@levkowetz.com> <6C8FDE4E-88F8-4862-A9CC-3D1E9B0DCD4C@orandom.net> <fe468ed5-3d9b-88b2-8403-f8482bb1f55b@levkowetz.com> <647a593e-8104-0a59-bd0b-fb377f49201e@levkowetz.com> <A6C1B0DF-EAE0-46DC-9539-F56A3192E336@orandom.net> <C49A9B95-1196-4439-8021-31ECDC676813@orandom.net>
Cc: xml2rfc@ietf.org
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <ef268839-ad99-3246-7c98-65d07bbe1d4e@levkowetz.com>
Date: Tue, 21 Jan 2020 09:27:56 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <C49A9B95-1196-4439-8021-31ECDC676813@orandom.net>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="sdP96lXu0P8ErDx3fMFiScxJIKQC6qppm"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: xml2rfc@ietf.org, daveoran@orandom.net
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/5EtzOwBKY5BxawhAm-lSxi3gkZc>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
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: Tue, 21 Jan 2020 08:28:11 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--sdP96lXu0P8ErDx3fMFiScxJIKQC6qppm
Content-Type: multipart/mixed; boundary="sKVk4ABoGhFoMsuInVbHjn0gLjmuhWEIi";
 protected-headers="v1"
From: Henrik Levkowetz <henrik@levkowetz.com>
To: "David R. Oran" <daveoran@orandom.net>
Cc: xml2rfc@ietf.org
Message-ID: <ef268839-ad99-3246-7c98-65d07bbe1d4e@levkowetz.com>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net>
 <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com>
 <DA4F22F5-5A43-4671-B69B-EDF61F976623@orandom.net>
 <61971d80-1c1e-bdf7-a986-0cfe9de157e6@levkowetz.com>
 <6C8FDE4E-88F8-4862-A9CC-3D1E9B0DCD4C@orandom.net>
 <fe468ed5-3d9b-88b2-8403-f8482bb1f55b@levkowetz.com>
 <647a593e-8104-0a59-bd0b-fb377f49201e@levkowetz.com>
 <A6C1B0DF-EAE0-46DC-9539-F56A3192E336@orandom.net>
 <C49A9B95-1196-4439-8021-31ECDC676813@orandom.net>
In-Reply-To: <C49A9B95-1196-4439-8021-31ECDC676813@orandom.net>

--sKVk4ABoGhFoMsuInVbHjn0gLjmuhWEIi
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


On 2020-01-21 06:59, David R. Oran wrote:
> Oh, one more thing I noticed that puzzled me briefly=E2=80=A6
>=20
> RFC7991 says:
>=20
> 	2.45.3.  "docName" Attribute
>=20
> 	   Deprecated; instead, use the "value" attribute in <seriesInfo>.
>=20

> but your draft won=E2=80=99t compile unless you include it as an attrib=
ute of
> the <rfc> element.

Yes.  There are a number of changes after RFC7991; a -bis is definitely
needed.


Best regards,

	Henrik

> On 21 Jan 2020, at 0:51, David R. Oran wrote:
>=20
>> Thanks a ton for the help. I puzzled around some more in the FAQ and R=
FC7991, getting rid of suspicious V2-ish stuff that used to be adorning a=
ll my draft source files and replacing the essentials with the right V3 c=
onstructs. However, among those was not the xmlns:ni, which I had copied =
from one of the examples in draft-hoffman-rfcexamples. Once that was gone=
 the crash disappeared.
>>
>> One unsolicited piece of advice is that in addition to the FAQ and RFC=
7991 itself, some templates in native V3 for people to start from would h=
ave saved me the pain you see in this thread. The example in Paul Hoffman=
=E2=80=99s draft (which I found googling =E2=80=9Cxml2rfc v3 examples=E2=80=
=9D of course) was generated using the converter and wound up being extre=
mely misleading for a =E2=80=9Cnative=E2=80=9D V3 source file.
>>
>> Best, DaveO.
>>
>> P.S. I did get another crash when I put my own <date> element in the <=
front> element as per =E2=80=9C<date month=3D'January' year=3D'2020' /> W=
hen I let the converter insert the date in the output itself, no problem.=

>>
>>
>> 	xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
>> 	draft-oran-icnrg-reflexive-forwarding.xml(63): Warning: The document =
date (2020-01-01) is more than 3 days away from today's date
>> 	Traceback (most recent call last):
>> 	  File "/usr/local/bin/xml2rfc", line 8, in <module>
>> 	    sys.exit(main())
>> 	  File "/usr/local/lib/python2.7/site-packages/xml2rfc/run.py", line =
620, in main
>> 	    xmlrfc.tree =3D prep.prep()
>> 	  File "/usr/local/lib/python2.7/site-packages/xml2rfc/writers/prepto=
ol.py", line 342, in prep
>> 	    func(e, e.getparent())
>> 	  File "/usr/local/lib/python2.7/site-packages/xml2rfc/writers/prepto=
ol.py", line 1123, in boilerplate_insert_status_of_memo
>> 	    exp =3D datetime.date(year=3Dyear, month=3Dmonth, day=3Dday) + da=
tetime.timedelta(days=3D185)
>> 	TypeError: an integer is required
>>
>>
>> On 20 Jan 2020, at 18:20, Henrik Levkowetz wrote:
>>
>>> Hi again David,
>>>
>>> The issue is triggered by the code trying to insert the XInclude name=
space
>>> if it isn't defined, but your file defines the 'xi' namespace prefix =
not
>>> as the XInclude namespace (http://www.w3.org/2001/XInclude), but as s=
omething
>>> that's very close to it:  (https://www.w3.org/2001/XInclude).  The co=
de
>>> then tries to insert xmlns:xi=3D"http://www.w3.org/2001/XInclude" whi=
ch fails.
>>>
>>> The code should handle this better.  It's clearly a bug.  Menawhile, =
if you
>>> change the https:// to http:// in the xmlns:xi attribute value, you s=
hould
>>> be able to get further.
>>>
>>> Once you've fixed that, you'll find that using XInclude doesn't permi=
t
>>> any inaccuracies in the specification of the href, so you'll have to =
add
>>> https:// to the <xi:include/> entries around line 140.  The v2 proces=
sor
>>> is much more forgiving about this, but the XInclude specification doe=
sn't
>>> permit a processor to be lenient in the manner xml2rfc is for v2 inpu=
t.
>>>
>>> Then you'll find that <tbody> isn't optional in v3 the way it is in h=
tml,
>>> and other issues that should be easier to sort out.
>>>
>>>
>>> Best,
>>>
>>> 	Henrik
>>>
>>> On 2020-01-20 23:59, Henrik Levkowetz wrote:
>>>> Hi David,
>>>>
>>>> On 2020-01-20 23:25, David R. Oran wrote:
>>>>> Thanks much. See below.
>>>>
>>>> Ack.  Will reply further once I've looked at the xml.  One point inl=
ine
>>>> now:
>>>>
>>>>> On 20 Jan 2020, at 16:25, Henrik Levkowetz wrote:
>>>>>
>>>>>> Hi David,
>>>>>>
>>>>>> On 2020-01-20 22:03, David R. Oran wrote:
>>>>>>> On 20 Jan 2020, at 15:10, Henrik Levkowetz wrote:
>>>>>>>
>>>>>>>> Hi David,
>>>>>>>>
>>>>>>>> You should simply remove "<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>" i=
f your
>>>>>>>> <rfc/> element contains the "version=3D'3'" attribute.
>>>>>>>>
>>>>>>> If I do that xml2rfc crashes (both the one on my machine and the =
web tool:
>>>>>>
>>>>>> Oh, wow.  Ok, I'll fix that in the next release.  Could you send t=
he full
>>>>>> xml file, please?  It's not obvious from your snippet where the su=
perfluous
>>>>>> other definition of xmlns:xi is.
>>>>>>
>>>>> attached.
>>>>>
>>>>>> Now, you say that instead of trying the converter, you stared out =
right
>>>>>> away with v3 syntax, but neither the DOCTYPE above, nor the <?rfc =
=2E.. ?>
>>>>>> PIs visible in your snippet are appropriate for a v3 document.  Di=
d you
>>>>>> grab a v2 template to start with?  I think really going to lead yo=
u into
>>>>>> a number of problems if you start with a v2 template and declare i=
t to be
>>>>>> v3.
>>>>>>
>>>>> No, I started from scratch=E2=80=A6but cut a pasted a few things fr=
om an
>>>>> earlier draft after checking (I thought correctly) that I was
>>>>> following the strict V3 definitions. Possibly not=E2=80=A6
>>>>>
>>>>> For yucks, I got rid of all that and started right off with the <rf=
c>
>>>>> element and xml2rfc still crashes.
>>>>>
>>>>>> Using the v2v3 converter on a v2 document, even on a v2 template, =
on the
>>>>>> other hand, should give you a proper v3 starting point, without th=
e issues
>>>>>> you've run into so far.
>>>>
>>>>> I believe that. But the output of the converter on
>>>>> draft-hoffman-rfcexamples-latest left the DOCTYPE declaration in
>>>>> there=E2=80=A6
>>>>
>>>> I think you'll find that the DOCTYPE doesn't mention a dtd in that c=
ase,
>>>> just a file which (if available) provides entity definitions.
>>>>
>>>> More in a moment.
>>>>
>>>>
>>>> Best regards,
>>>>
>>>> 	Henrik
>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> 	Henrik
>>>>>>
>>>>>>>
>>>>>>> xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
>>>>>>> Traceback (most recent call last):
>>>>>>>   File "/usr/local/bin/xml2rfc", line 8, in <module>
>>>>>>>     sys.exit(main())
>>>>>>>   File "/usr/local/lib/python2.7/site-packages/xml2rfc/run.py", l=
ine 612, in main
>>>>>>>     xmlrfc =3D parser.parse(remove_comments=3DFalse, quiet=3DTrue=
, add_xmlns=3DTrue)
>>>>>>>   File "/usr/local/lib/python2.7/site-packages/xml2rfc/parser.py"=
, line 548, in parse
>>>>>>>     for action, element in context:
>>>>>>>   File "src/lxml/iterparse.pxi", line 208, in lxml.etree.iterpars=
e.__next__ (src/lxml/lxml.etree.c:148588)
>>>>>>>   File "<string>", line 22
>>>>>>> lxml.etree.XMLSyntaxError: Attribute xmlns:xi redefined, line 22,=
 column 59
>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> 	Henrik
>>>>>>>>
>>>>>>>> On 2020-01-20 21:00, David R. Oran wrote:
>>>>>>>>> I have a new Internet Draft to write, so I decided to bite the =
bullet
>>>>>>>>> and do it in V3. Rather than write in V2 and try the converter,=
 I
>>>>>>>>> started out right away with V3 syntax. I didn=E2=80=99t get ver=
y far. I tried
>>>>>>>>> both the most recent xml2rfc by installing it on my machine, an=
d the web
>>>>>>>>> tool and got identical errors.
>>>>>>>>>
>>>>>>>>> If I follow the described syntax in RFC7991, the RFC Editor FAQ=
 in
>>>>>>>>> https://ftp.ripe.net/rfc/v3test/FAQ-2019-02.html and the exampl=
e in
>>>>>>>>> draft-hoffman-rfcexamples-latest as below:
>>>>>>>>>
>>>>>>>>> 	<?xml version=3D"1.0" encoding=3D"US-ASCII"?>
>>>>>>>>> 	<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>
>>>>>>>>>
>>>>>>>>> 	<?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?>
>>>>>>>>> 	<?rfc strict=3D"yes" ?>
>>>>>>>>> 	<?rfc toc=3D"yes"?>
>>>>>>>>> 	<?rfc tocdepth=3D"4"?>
>>>>>>>>> 	<?rfc symrefs=3D"yes" ?>
>>>>>>>>> 	<?rfc sortrefs=3D"yes" ?>
>>>>>>>>> 	<?rfc compact=3D"yes" ?>
>>>>>>>>> 	<?rfc subcompact=3D"no" ?>
>>>>>>>>> 	<rfc
>>>>>>>>> 		version=3D=E2=80=983=E2=80=99
>>>>>>>>> 		ipr=3D'trust200902'
>>>>>>>>> 		category=3D'exp'
>>>>>>>>> 		submissionType=3D'IRTF'
>>>>>>>>> 		docName=3D'draft-oran-icnrg-reflexive-forwarding-00'
>>>>>>>>> 		xml:lang=3D'en' xmlns:xi=3D"https://www.w3.org/2001/XInclude"=
>
>>>>>>>>>
>>>>>>>>> 	<front>
>>>>>>>>> 		<seriesInfo name=3D'Internet-Draft'
>>>>>>>>> value=3D'draft-oran-icnrg-reflexive-forwarding-00'/>
>>>>>>>>> 	    <title abbrev=3D'ICN Reflexive Forwarding'>Reflexive Forwa=
rding for
>>>>>>>>> CCNx and NDN Protocols
>>>>>>>>> 	    </title>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I get
>>>>>>>>>
>>>>>>>>> 	% xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
>>>>>>>>> 	Incompatible schema information: found "rfc2629.dtd" in <DOCTY=
PE> of a
>>>>>>>>> version 3 file.
>>>>>>>>>
>>>>>>>>> If I leave off the =E2=80=9Cversion=3D=E2=80=983=E2=80=99, as b=
elow
>>>>>>>>>
>>>>>>>>> 	<?xml version=3D"1.0" encoding=3D"US-ASCII"?>
>>>>>>>>> 	<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>
>>>>>>>>> 	<?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?>
>>>>>>>>> 	<?rfc strict=3D"yes" ?>
>>>>>>>>> 	<?rfc toc=3D"yes"?>
>>>>>>>>> 	<?rfc tocdepth=3D"4"?>
>>>>>>>>> 	<?rfc symrefs=3D"yes" ?>
>>>>>>>>> 	<?rfc sortrefs=3D"yes" ?>
>>>>>>>>> 	<?rfc compact=3D"yes" ?>
>>>>>>>>> 	<?rfc subcompact=3D"no" ?>
>>>>>>>>>
>>>>>>>>> 	<rfc
>>>>>>>>> 		ipr=3D'trust200902'
>>>>>>>>> 		category=3D'exp'
>>>>>>>>> 		submissionType=3D'IRTF'
>>>>>>>>> 		docName=3D'draft-oran-icnrg-reflexive-forwarding-00'
>>>>>>>>> 		xml:lang=3D'en' xmlns:xi=3D"https://www.w3.org/2001/XInclude"=
>
>>>>>>>>>
>>>>>>>>> 	<front>
>>>>>>>>> 		<seriesInfo name=3D'Internet-Draft'
>>>>>>>>> value=3D'draft-oran-icnrg-reflexive-forwarding-00'/>
>>>>>>>>> 	    <title abbrev=3D'ICN Reflexive Forwarding'>Reflexive Forwa=
rding for
>>>>>>>>> CCNx and NDN Protocols
>>>>>>>>> 	    </title>
>>>>>>>>>
>>>>>>>>> I get:
>>>>>>>>>
>>>>>>>>> 		xml2rfc draft-oran-icnrg-reflexive-forwarding.xml
>>>>>>>>> 		Error: Unable to validate the XML document:
>>>>>>>>> draft-oran-icnrg-reflexive-forwarding.xml
>>>>>>>>> 		 <string>: Line 23: No declaration for attribute xmlns:xi of =
element
>>>>>>>>> rfc
>>>>>>>>> 		 <string>: Line 25: Element front content does not follow the=
 DTD,
>>>>>>>>> expecting (title , author+ , date , area* , workgroup* , keywor=
d* ,
>>>>>>>>> abstract? , note*), got (seriesInfo title author author date ar=
ea
>>>>>>>>> workgroup keyword keyword abstract )
>>>>>>>>> 		 <string>: Line 81: Element section content does not follow t=
he DTD,
>>>>>>>>> expecting ((t | figure | texttable | iref)* , section*), got (n=
ame t )
>>>>>>>>> 		 <string>: Line 81: Element section does not carry attribute =
title
>>>>>>>>> 		 <string>: Line 81: No declaration for element name
>>>>>>>>> 		 <string>: Line 85: Element section content does not follow t=
he DTD,
>>>>>>>>> expecting ((t | figure | texttable | iref)* , section*), got (n=
ame t )
>>>>>>>>> 		 <string>: Line 85: Element section does not carry attribute =
title
>>>>>>>>> 		 <string>: Line 85: No declaration for element name
>>>>>>>>> 		 <string>: Line 94: Element section content does not follow t=
he DTD,
>>>>>>>>> expecting ((t | figure | texttable | iref)* , section*), got (n=
ame t
>>>>>>>>> section section )
>>>>>>>>> 		 <string>: Line 94: Element section does not carry attribute =
title
>>>>>>>>> 		 <string>: Line 94: No declaration for element name
>>>>>>>>> 		 <string>: Line 97: Element section content does not follow t=
he DTD,
>>>>>>>>> expecting ((t | figure | texttable | iref)* , section*), got (n=
ame t
>>>>>>>>> table )
>>>>>>>>> 		 <string>: Line 97: Element section does not carry attribute =
title
>>>>>>>>> 		 <string>: Line 97: No declaration for element name
>>>>>>>>> 		 <string>: Line 98: No declaration for attribute keepWithNext=
 of
>>>>>>>>> element t
>>>>>>>>> 		 <string>: Line 99: No declaration for element table
>>>>>>>>> 		 <string>: Line 99: No declaration for attribute title of ele=
ment
>>>>>>>>> table
>>>>>>>>>
>>>>>>>>> Clue bat please?
>>>>>>>>>
>>>>>>>>> DaveO
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> xml2rfc mailing list
>>>>>>>>> xml2rfc@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>>>>>>>>
>>>>>>>
>>>>>>> DaveO
>>>>>>>
>>>>>
>>>>> DaveO
>>>>>
>>>>
>>
>> DaveO
>=20
>=20
>> _______________________________________________
>> xml2rfc mailing list
>> xml2rfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/xml2rfc
>=20
> DaveO
>=20


--sKVk4ABoGhFoMsuInVbHjn0gLjmuhWEIi--

--sdP96lXu0P8ErDx3fMFiScxJIKQC6qppm
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl4mtg0ACgkQTptXS4+7
FxrAGBAApEnwj55WFa7Be3CqHluqYI3zw8ZrisxTF2J/DPAv9FB0H93Jkr4TXeCT
w7Ah25u6H74UsEOMngaT1i7YJXixzfWEnfVDdftTimHBeQ45L54VoOfUxIF27LoZ
IeUHYrZmtE+smaIHxoa5W0EXSG13P5R4Nax7Mmbi4vYzk/cKG7TDwlt7B1FDP5rG
rMdGdzqWVefSSnLOguOkN0VpNFZafWmlOX/yFl5Qk6Gzb30O2Nh73VleDmDvDc28
FQuFRq1tTn8doCQagsZ7CHYtI+thd8iDu0tiKoZKcLk4LDgzBcHopoBSArTl5HIo
AWAj5xVnkVuvs7byWB0dOQfSb1eF6O5bYgeH19gy+Fs23ftfDVvnP0+N9mt74Hag
gnehT6OXxdyc1YxneA+4wQbluvmYRLZYNX8LhiHTAEOa9Z9jqRSoN1ATkEcI7IlK
+CS9f+lP4dJ5xxV1mUDWlTX4LdS4vLn3oFV8wS3MOIBBsOP+S9fU0vGnAGZv/qnU
CQivxpzFSITs7R4zif28nBMgnVetSG1b7Dv3S7Rw3xW9mosFYXVtcAX056WDm/4X
6Ub+C2ueI9CjVznInZoUWK9uBeYy2PzjIZEho3MslUoKWYAwWhQ1gLtlSYpn/DYs
vvEVJXjcY1UM/VxOdQI22w7gByZoQ64iQ8F4E2odQzTtMy0hiZ8=
=7YFP
-----END PGP SIGNATURE-----

--sdP96lXu0P8ErDx3fMFiScxJIKQC6qppm--


From nobody Tue Jan 21 05:30:40 2020
Return-Path: <daveoran@orandom.net>
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 D85591200CD for <xml2rfc@ietfa.amsl.com>; Tue, 21 Jan 2020 05:30:38 -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 EnC-exKUbTkT for <xml2rfc@ietfa.amsl.com>; Tue, 21 Jan 2020 05:30:33 -0800 (PST)
Received: from spark.crystalorb.net (spark.crystalorb.net [IPv6:2607:fca8:1530::c]) (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 D0306120059 for <xml2rfc@ietf.org>; Tue, 21 Jan 2020 05:30:33 -0800 (PST)
Received: from [192.168.2.1] ([IPv6:2601:184:407f:80ce:349f:2df:2bdc:d2ac]) (authenticated bits=0) by spark.crystalorb.net (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id 00LDUQ64004234 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Tue, 21 Jan 2020 05:30:28 -0800
From: "David R. Oran" <daveoran@orandom.net>
To: "Julian Reschke" <julian.reschke@gmx.de>
Cc: "Henrik Levkowetz" <henrik@levkowetz.com>, xml2rfc@ietf.org
Date: Tue, 21 Jan 2020 08:30:20 -0500
X-Mailer: MailMate (1.13.1r5676)
Message-ID: <EE70DAA2-A374-4D6C-A3BA-A6C2CD3D865B@orandom.net>
In-Reply-To: <e8173c00-2bed-0561-e3b2-4b6f06bc08f9@gmx.de>
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net> <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com> <DA4F22F5-5A43-4671-B69B-EDF61F976623@orandom.net> <61971d80-1c1e-bdf7-a986-0cfe9de157e6@levkowetz.com> <6C8FDE4E-88F8-4862-A9CC-3D1E9B0DCD4C@orandom.net> <fe468ed5-3d9b-88b2-8403-f8482bb1f55b@levkowetz.com> <647a593e-8104-0a59-bd0b-fb377f49201e@levkowetz.com> <A6C1B0DF-EAE0-46DC-9539-F56A3192E336@orandom.net> <C49A9B95-1196-4439-8021-31ECDC676813@orandom.net> <e8173c00-2bed-0561-e3b2-4b6f06bc08f9@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/UYxp6RlKtqG8BlZ41dgdyvv78z0>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
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: Tue, 21 Jan 2020 13:30:39 -0000

On 21 Jan 2020, at 1:14, Julian Reschke wrote:

> On 21.01.2020 06:59, David R. Oran wrote:
>> Oh, one more thing I noticed that puzzled me briefly=E2=80=A6
>>
>> RFC7991 says:
>>
>> |2.45.3. "docName" Attribute Deprecated; instead, use the "value"
>> attribute in <seriesInfo>. |
>>
>> but your draft won=E2=80=99t compile unless you include it as an attri=
bute =

>> of
>> the <rfc> element.
>> ...
>
> We currently do not have a spec that describes v3-as-implemented.
>
> You will *also* have to look at
> <https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-=
notes-10>,
> and even that will not give you the full picture.
>
Thanks, I had looked a that a while back when I was just perusing =

RFC-editor related drafts, but had forgotten it. Will keep it handy =

going forward.

> Best regards, Julian

DaveO


From nobody Tue Jan 21 05:37:33 2020
Return-Path: <daveoran@orandom.net>
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 9C5161200F7 for <xml2rfc@ietfa.amsl.com>; Tue, 21 Jan 2020 05:37:31 -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 zeL0X-N2VdYd for <xml2rfc@ietfa.amsl.com>; Tue, 21 Jan 2020 05:37:26 -0800 (PST)
Received: from spark.crystalorb.net (spark.crystalorb.net [IPv6:2607:fca8:1530::c]) (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 949D11200E5 for <xml2rfc@ietf.org>; Tue, 21 Jan 2020 05:37:26 -0800 (PST)
Received: from [192.168.2.1] ([IPv6:2601:184:407f:80ce:349f:2df:2bdc:d2ac]) (authenticated bits=0) by spark.crystalorb.net (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id 00LDbNNH004413 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Tue, 21 Jan 2020 05:37:25 -0800
From: "David R. Oran" <daveoran@orandom.net>
To: "Henrik Levkowetz" <henrik@levkowetz.com>
Cc: xml2rfc@ietf.org
Date: Tue, 21 Jan 2020 08:37:17 -0500
X-Mailer: MailMate (1.13.1r5676)
Message-ID: <7FAEB626-F120-4A03-91D8-F3FE6FE26001@orandom.net>
In-Reply-To: <43f689a4-7bc5-5e8c-0ca6-0ca785a77c8e@levkowetz.com>
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net> <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com> <DA4F22F5-5A43-4671-B69B-EDF61F976623@orandom.net> <61971d80-1c1e-bdf7-a986-0cfe9de157e6@levkowetz.com> <6C8FDE4E-88F8-4862-A9CC-3D1E9B0DCD4C@orandom.net> <fe468ed5-3d9b-88b2-8403-f8482bb1f55b@levkowetz.com> <647a593e-8104-0a59-bd0b-fb377f49201e@levkowetz.com> <A6C1B0DF-EAE0-46DC-9539-F56A3192E336@orandom.net> <43f689a4-7bc5-5e8c-0ca6-0ca785a77c8e@levkowetz.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_DC9FD84C-C0A2-46EB-9A65-27448EBE8F0D_="; micalg=pgp-sha1; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/v9uu-vc1wrs3Lns98AabwL-X2uY>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
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: Tue, 21 Jan 2020 13:37:32 -0000

This is an OpenPGP/MIME signed message (RFC 3156 and 4880).

--=_MailMate_DC9FD84C-C0A2-46EB-9A65-27448EBE8F0D_=
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On 21 Jan 2020, at 3:26, Henrik Levkowetz wrote:

> Hi Dave,
>
[snipping out to get to your question]

> On 2020-01-21 06:51, David R. Oran wrote:
>
> And yes, having v3 templates would be helpful.  I'll see if I can fix t=
hat
> too.  Where would you normally grab a template?
>
well, by googling :-)
Probably the home ought to be off the tools home page at tools.ietf.org. =
There=E2=80=99s already a =E2=80=9Ctemplates=E2=80=9D link on that page -=
 it=E2=80=99s to Elwyn Davies examples, and ought to have a V3 template.

A pointer in the RFC Editor xml2rfc FAQ would also be useful.

DaveO.

> 	Henrik
>

--=_MailMate_DC9FD84C-C0A2-46EB-9A65-27448EBE8F0D_=
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename=signature.asc
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iQJJBAEBAgAzFiEEroJBCc9z/EJK1xs/eu0uvThCv/AFAl4m/o0VHGRhdmVvcmFu
QG9yYW5kb20ubmV0AAoJEHrtLr04Qr/weesP/3kjdQp1RYdYGqLmUQZUKFVLsZxn
RTu2u9KQbLHrIGiz2pn0Mh675AWpxKzsu8onPkhwGOXfWJuU7bMt22nQdvrq44Yo
3WNM9uNMRuK59U0aJHgGD8+iNLs5rvi8D7NJKprRC0/3CNNliWRwQLuJE0yuwewA
9KkjDugduZ2Jk6Ro8YsKoCPgWMZaHzUlCWVRp4STESvspuhFD9cV5zRZgu3L7Ij7
Cd2CHo9n0qeYl1BNnXz1NcYTaXA3IznOy1Lr4uBAEdlPh/O3EXRSniu7uUrozA4G
PBsSz6QFG6FowdYIOrSCVsm1fkwFifof0joqjlfVitNW+5bpE0MiwU9QhwlWmqif
dxapJ1BAFA4FkHp4u/32yZMe0i9Yngorl3NeQJShlcxJaJzuOkUfPGXBVUSHUDRm
wjt7X6ok1BrCRYb7keLvCE8CAocnN8eEwkh3yquHAPoOv65t8gdsOOdjkjBdtbCS
h+Pgcwsf57CnKpAHSiQRsogQykKbLOQFKArsivpT5NFpiO0Yh7iaZXY20ZvRVn74
xsagOrANJt81gu3t6R1Mzr+T+3nTQgoSBg0LXO8mq23oZO5/1FcyH0YZoiZwXktT
+Uh/6T9nGQEwIPonR7lHkgp2qKMLkf8mY3PnvfY5aoTiJYzO9vXfbe9L6lc5VpS9
IikrvCPRmqe9C5uT
=u0rv
-----END PGP SIGNATURE-----

--=_MailMate_DC9FD84C-C0A2-46EB-9A65-27448EBE8F0D_=--


From nobody Tue Jan 21 08:35:07 2020
Return-Path: <pkyzivat@alum.mit.edu>
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 C1C61120108 for <xml2rfc@ietfa.amsl.com>; Tue, 21 Jan 2020 08:35:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alum.mit.edu
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 z20j6-9mi_jz for <xml2rfc@ietfa.amsl.com>; Tue, 21 Jan 2020 08:35:00 -0800 (PST)
Received: from NAM12-MW2-obe.outbound.protection.outlook.com (mail-mw2nam12on2089.outbound.protection.outlook.com [40.107.244.89]) (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 C8B43120044 for <xml2rfc@ietf.org>; Tue, 21 Jan 2020 08:34:56 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=gpun5dSzv41g3fnrDSPEiI5TUE4Ckol5G135+RfYokgZsu8spjuYh0LtZvJnpQvdKiXNoUdGuI9uEXlVHIHR+CRzdrMX5VFLosrk3aBfADOf5ECptvgHL2jHaxoJZl716aD69dyrEQuERJ9pB2KoXdU2gpMgW2xuUxG0p6S0bBPgsKjDqnJTJFeZ9mqV+5s/BehEJYf8AJMWLcslpQc2xVPOR5/zT1p+2DJbkKLC/s5zSjNMaAk6+/wnHbhkY7HBXg55YIXa2csAdP5IJ0cOdoe0g+BiCPff/KmLEUzj4UfEYuRDrwN/n/zkGOU/pV9TKMG+npDoShxI+kLo8eVarA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=IcfSyWj1dzvvFeGAICW0hFpxXCpK/KvAIvO1Ojz/Nsk=; b=lxlFSj/oos7MvLGqOzmG1HzoKPY/5e0wUCeKWF2xWWU2QnpANGfO2tTCotijlagOG84PjXsCbCpcFyxPp7UdVhU1hC7AzC2qqDOtS+NGcRMTL0QrYMWu7WkcjI/JOeervbrkbZgguOjSsAoXVyfKlDuWaIxd0DKfw3u3su2+r9eJVY13mPCq31k7uYmFuI7LmHuVTegrff9Cw66cVDTbIldHgd1U6zlIZt0Dx/mUTV3CrWu1WW7fA4Q97rR7l45qiWvQy1C/tQUDC8rr9JYY0q4byqW66wyQ6Dz8bNbRUdlGNac2ZL3Syfmn9I/qvY88QW080BkIxs895BOVcRCf2Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 18.7.68.33) smtp.rcpttodomain=ietf.org smtp.mailfrom=alum.mit.edu; dmarc=bestguesspass action=none header.from=alum.mit.edu; dkim=none (message not signed); arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alum.mit.edu; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=IcfSyWj1dzvvFeGAICW0hFpxXCpK/KvAIvO1Ojz/Nsk=; b=dct35sO9xnN0ojoGXGcfK+ojST0Pv5KDEa+HQSAgpPLlSygx+5gI11aNgKa46RilSvKHjJUCylpNeMc7wqjyQS7yGDuAG5L3rbvB2sW3tLvoEw4QNvejdSUBGuLfp3lavEYYZAUTCuOzlmL60gIC1ptHhguxOvAHgQF0vtJdaXk=
Received: from SN1PR12CA0054.namprd12.prod.outlook.com (2603:10b6:802:20::25) by BN6PR12MB1155.namprd12.prod.outlook.com (2603:10b6:404:1b::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2644.25; Tue, 21 Jan 2020 16:34:54 +0000
Received: from SN1NAM02FT062.eop-nam02.prod.protection.outlook.com (2a01:111:f400:7e44::207) by SN1PR12CA0054.outlook.office365.com (2603:10b6:802:20::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2644.18 via Frontend Transport; Tue, 21 Jan 2020 16:34:54 +0000
Authentication-Results: spf=pass (sender IP is 18.7.68.33) smtp.mailfrom=alum.mit.edu; ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=bestguesspass action=none header.from=alum.mit.edu;
Received-SPF: Pass (protection.outlook.com: domain of alum.mit.edu designates 18.7.68.33 as permitted sender) receiver=protection.outlook.com;  client-ip=18.7.68.33; helo=outgoing-alum.mit.edu;
Received: from outgoing-alum.mit.edu (18.7.68.33) by SN1NAM02FT062.mail.protection.outlook.com (10.152.72.208) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2644.19 via Frontend Transport; Tue, 21 Jan 2020 16:34:54 +0000
Received: from Kokiri.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id 00LGYq1A021484 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <xml2rfc@ietf.org>; Tue, 21 Jan 2020 11:34:53 -0500
To: xml2rfc@ietf.org
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net> <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com> <DA4F22F5-5A43-4671-B69B-EDF61F976623@orandom.net> <61971d80-1c1e-bdf7-a986-0cfe9de157e6@levkowetz.com> <6C8FDE4E-88F8-4862-A9CC-3D1E9B0DCD4C@orandom.net> <fe468ed5-3d9b-88b2-8403-f8482bb1f55b@levkowetz.com> <647a593e-8104-0a59-bd0b-fb377f49201e@levkowetz.com> <A6C1B0DF-EAE0-46DC-9539-F56A3192E336@orandom.net> <43f689a4-7bc5-5e8c-0ca6-0ca785a77c8e@levkowetz.com> <7FAEB626-F120-4A03-91D8-F3FE6FE26001@orandom.net>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <ffabdb16-89af-2f62-8d2e-db080a73d7ec@alum.mit.edu>
Date: Tue, 21 Jan 2020 11:34:52 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <7FAEB626-F120-4A03-91D8-F3FE6FE26001@orandom.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:18.7.68.33; IPV:CAL; SCL:-1; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10009020)(199004)(189003)(356004)(498600001)(246002)(336012)(26826003)(2616005)(8676002)(186003)(53546011)(956004)(8936002)(36906005)(26005)(7596002)(86362001)(31696002)(6916009)(70206006)(2906002)(70586007)(31686004)(5660300002)(75432002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR12MB1155; H:outgoing-alum.mit.edu; FPR:; SPF:Pass; LANG:en; PTR:outgoing-alum.mit.edu; A:1; MX:1; 
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 88a5eb4f-5842-4950-6c50-08d79e8fd85f
X-MS-TrafficTypeDiagnostic: BN6PR12MB1155:
X-Microsoft-Antispam-PRVS: <BN6PR12MB115596770FA6F26C6E40248FF90D0@BN6PR12MB1155.namprd12.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:8273;
X-Forefront-PRVS: 0289B6431E
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: CoQQL7x+1HIUrC/mtEOigER+tOCjT2F4fH2lMe3CeLO5odURHDJXDk+pHY+VIlKltUK5SHIdBK3j5L2QU1e1elh8XSorSqoKG8q6yuHz+GAwR2or/FcGdKlKQ2mrJnIiOEC9hPBNkgm3QC7zLXuY4MZ21elojXG2NIPXHSAKBLrl/pRstCdxOYWmVHPqjulTel9OG3rPextOQAoExa2gwy7PkhvttD3mrCWO2qkHlv3xWixUd7zwFGmMBQ6mVS5TjMRFZPjMpXYwBa61cYZ8v9jMe8JSKbX137gvI7+gQ5vMzRchvSbYz7xXNEsPOEn4uqZr5ceyqlCcKLZlRA866JV3WEuZvZ4+JCZyKKu3wRSOIaYZ8Ki65WjuWaAr+UB0n4fbeEMj+wTz+VnROw9wFCKOdbWca0wy9XAXEd+f+mRWe/rsH9tjf4/W3xtXT969
X-OriginatorOrg: alum.mit.edu
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Jan 2020 16:34:54.1787 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 88a5eb4f-5842-4950-6c50-08d79e8fd85f
X-MS-Exchange-CrossTenant-Id: 3326b102-c043-408b-a990-b89e477d582f
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=3326b102-c043-408b-a990-b89e477d582f; Ip=[18.7.68.33];  Helo=[outgoing-alum.mit.edu]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR12MB1155
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/Qg6_w0QkfALiiVDwIEWUQfIpXjI>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
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: Tue, 21 Jan 2020 16:35:06 -0000

On 1/21/20 8:37 AM, David R. Oran wrote:
> On 21 Jan 2020, at 3:26, Henrik Levkowetz wrote:
> 
>> Hi Dave,
>>
> [snipping out to get to your question]
> 
>> On 2020-01-21 06:51, David R. Oran wrote:
>>
>> And yes, having v3 templates would be helpful.  I'll see if I can fix that
>> too.  Where would you normally grab a template?
>>
> well, by googling :-)
> Probably the home ought to be off the tools home page at tools.ietf.org. There’s already a “templates” link on that page - it’s to Elwyn Davies examples, and ought to have a V3 template.

I've just been lurking, but seems like a good time to comment...

I normally get my "template" by starting with some similar document, 
either one of my own if I have a suitable one, or from some document I 
am generally aware of.

But that doesn't work well now when there aren't many v3 documents to 
crib from.

I guess I would be inclined to grab the v2 for some similar document and 
convert it. But I guess maybe that won't give optimal style for the new 
document. So maybe having a recommended source of pure templates and 
also some "real" documents that are judged to be "good" examples would 
be helpful.

	Thanks,
	Paul


From nobody Tue Jan 21 09:03:05 2020
Return-Path: <sginoza@amsl.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 7831E120804 for <xml2rfc@ietfa.amsl.com>; Tue, 21 Jan 2020 09:03:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 ntnD9zHV0svz for <xml2rfc@ietfa.amsl.com>; Tue, 21 Jan 2020 09:02:58 -0800 (PST)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CD5512024E for <xml2rfc@ietf.org>; Tue, 21 Jan 2020 09:02:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id E28E22032BC; Tue, 21 Jan 2020 09:01:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I60X4_IFDaHj; Tue, 21 Jan 2020 09:01:05 -0800 (PST)
Received: from [IPv6:2605:e000:1524:de:4431:ee23:764e:1ac0] (unknown [IPv6:2605:e000:1524:de:4431:ee23:764e:1ac0]) by c8a.amsl.com (Postfix) with ESMTPSA id A0020202EF6; Tue, 21 Jan 2020 09:01:05 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Sandy Ginoza <sginoza@amsl.com>
In-Reply-To: <ffabdb16-89af-2f62-8d2e-db080a73d7ec@alum.mit.edu>
Date: Tue, 21 Jan 2020 09:02:52 -0800
Cc: xml2rfc@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <21C39653-A1B9-4225-9406-681218978FDA@amsl.com>
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net> <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com> <DA4F22F5-5A43-4671-B69B-EDF61F976623@orandom.net> <61971d80-1c1e-bdf7-a986-0cfe9de157e6@levkowetz.com> <6C8FDE4E-88F8-4862-A9CC-3D1E9B0DCD4C@orandom.net> <fe468ed5-3d9b-88b2-8403-f8482bb1f55b@levkowetz.com> <647a593e-8104-0a59-bd0b-fb377f49201e@levkowetz.com> <A6C1B0DF-EAE0-46DC-9539-F56A3192E336@orandom.net> <43f689a4-7bc5-5e8c-0ca6-0ca785a77c8e@levkowetz.com> <7FAEB626-F120-4A03-91D8-F3FE6FE26001@orandom.net> <ffabdb16-89af-2f62-8d2e-db080a73d7ec@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/jmt_HVklqyqc14g1qv36zJHkZog>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
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: Tue, 21 Jan 2020 17:03:04 -0000

Hi all,

You may find some of the XML files in =
<https://www.rfc-editor.org/rfc/prerelease/> helpful.  These are the v3 =
XML files for the RFCs before they are run through the final =E2=80=9Cprep=
=E2=80=9D tool (see https://tools.ietf.org/html/rfc7998).=20

I suggest reviewing some of the more recently published RFCs for better =
examples. =20

Thanks,
Sandy=20



> On Jan 21, 2020, at 8:34 AM, Paul Kyzivat <pkyzivat@alum.mit.edu> =
wrote:
>=20
> On 1/21/20 8:37 AM, David R. Oran wrote:
>> On 21 Jan 2020, at 3:26, Henrik Levkowetz wrote:
>>> Hi Dave,
>>>=20
>> [snipping out to get to your question]
>>> On 2020-01-21 06:51, David R. Oran wrote:
>>>=20
>>> And yes, having v3 templates would be helpful.  I'll see if I can =
fix that
>>> too.  Where would you normally grab a template?
>>>=20
>> well, by googling :-)
>> Probably the home ought to be off the tools home page at =
tools.ietf.org. There=E2=80=99s already a =E2=80=9Ctemplates=E2=80=9D =
link on that page - it=E2=80=99s to Elwyn Davies examples, and ought to =
have a V3 template.
>=20
> I've just been lurking, but seems like a good time to comment...
>=20
> I normally get my "template" by starting with some similar document, =
either one of my own if I have a suitable one, or from some document I =
am generally aware of.
>=20
> But that doesn't work well now when there aren't many v3 documents to =
crib from.
>=20
> I guess I would be inclined to grab the v2 for some similar document =
and convert it. But I guess maybe that won't give optimal style for the =
new document. So maybe having a recommended source of pure templates and =
also some "real" documents that are judged to be "good" examples would =
be helpful.
>=20
> 	Thanks,
> 	Paul
>=20
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc


From nobody Tue Jan 21 09:03:22 2020
Return-Path: <henrik@levkowetz.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 3F8D8120820 for <xml2rfc@ietfa.amsl.com>; Tue, 21 Jan 2020 09:03:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 OhxG-E5MUixR for <xml2rfc@ietfa.amsl.com>; Tue, 21 Jan 2020 09:03:11 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 065C1120804 for <xml2rfc@ietf.org>; Tue, 21 Jan 2020 09:03:11 -0800 (PST)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:62356 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1itwvk-0003t4-JW; Tue, 21 Jan 2020 09:03:09 -0800
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, xml2rfc@ietf.org
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net> <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com> <DA4F22F5-5A43-4671-B69B-EDF61F976623@orandom.net> <61971d80-1c1e-bdf7-a986-0cfe9de157e6@levkowetz.com> <6C8FDE4E-88F8-4862-A9CC-3D1E9B0DCD4C@orandom.net> <fe468ed5-3d9b-88b2-8403-f8482bb1f55b@levkowetz.com> <647a593e-8104-0a59-bd0b-fb377f49201e@levkowetz.com> <A6C1B0DF-EAE0-46DC-9539-F56A3192E336@orandom.net> <43f689a4-7bc5-5e8c-0ca6-0ca785a77c8e@levkowetz.com> <7FAEB626-F120-4A03-91D8-F3FE6FE26001@orandom.net> <ffabdb16-89af-2f62-8d2e-db080a73d7ec@alum.mit.edu>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <b379d083-350f-72eb-0e33-4abe53650e5a@levkowetz.com>
Date: Tue, 21 Jan 2020 18:03:01 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <ffabdb16-89af-2f62-8d2e-db080a73d7ec@alum.mit.edu>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Ox0NLB5i478NUuI9QiF3HU2nc7Lj1a9BN"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: xml2rfc@ietf.org, pkyzivat@alum.mit.edu
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/X77gCMNrEQZl3Fs5GKouV5C2-z4>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
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: Tue, 21 Jan 2020 17:03:16 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--Ox0NLB5i478NUuI9QiF3HU2nc7Lj1a9BN
Content-Type: multipart/mixed; boundary="jlF6ka8kVWoIeBdL2ghBoPE7VdxKbcru7";
 protected-headers="v1"
From: Henrik Levkowetz <henrik@levkowetz.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, xml2rfc@ietf.org
Message-ID: <b379d083-350f-72eb-0e33-4abe53650e5a@levkowetz.com>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net>
 <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com>
 <DA4F22F5-5A43-4671-B69B-EDF61F976623@orandom.net>
 <61971d80-1c1e-bdf7-a986-0cfe9de157e6@levkowetz.com>
 <6C8FDE4E-88F8-4862-A9CC-3D1E9B0DCD4C@orandom.net>
 <fe468ed5-3d9b-88b2-8403-f8482bb1f55b@levkowetz.com>
 <647a593e-8104-0a59-bd0b-fb377f49201e@levkowetz.com>
 <A6C1B0DF-EAE0-46DC-9539-F56A3192E336@orandom.net>
 <43f689a4-7bc5-5e8c-0ca6-0ca785a77c8e@levkowetz.com>
 <7FAEB626-F120-4A03-91D8-F3FE6FE26001@orandom.net>
 <ffabdb16-89af-2f62-8d2e-db080a73d7ec@alum.mit.edu>
In-Reply-To: <ffabdb16-89af-2f62-8d2e-db080a73d7ec@alum.mit.edu>

--jlF6ka8kVWoIeBdL2ghBoPE7VdxKbcru7
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Paul,

On 2020-01-21 17:34, Paul Kyzivat wrote:
> On 1/21/20 8:37 AM, David R. Oran wrote:
>> On 21 Jan 2020, at 3:26, Henrik Levkowetz wrote:
>>=20
>>> Hi Dave,
>>>
>> [snipping out to get to your question]
>>=20
>>> On 2020-01-21 06:51, David R. Oran wrote:
>>>
>>> And yes, having v3 templates would be helpful.  I'll see if I can fix=
 that
>>> too.  Where would you normally grab a template?
>>>
>> well, by googling :-)
>> Probably the home ought to be off the tools home page at tools.ietf.or=
g. There=E2=80=99s already a =E2=80=9Ctemplates=E2=80=9D link on that pag=
e - it=E2=80=99s to Elwyn Davies examples, and ought to have a V3 templat=
e.
>=20
> I've just been lurking, but seems like a good time to comment...
>=20
> I normally get my "template" by starting with some similar document,=20
> either one of my own if I have a suitable one, or from some document I =

> am generally aware of.
>=20
> But that doesn't work well now when there aren't many v3 documents to=20
> crib from.
>=20
> I guess I would be inclined to grab the v2 for some similar document an=
d=20
> convert it. But I guess maybe that won't give optimal style for the new=
=20
> document. So maybe having a recommended source of pure templates and=20
> also some "real" documents that are judged to be "good" examples would =

> be helpful.

The RPC might have some prepublication files that have been edited to
their standards.

For a schema v3 template, I've now run the converter on Elwyn's template
to produce a v3 version, and linked to that from https://tools.ietf.org/.=



	Henrik


--jlF6ka8kVWoIeBdL2ghBoPE7VdxKbcru7--

--Ox0NLB5i478NUuI9QiF3HU2nc7Lj1a9BN
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl4nLsUACgkQTptXS4+7
Fxprng/+NqmzdcBNWIaPjohZPMNWYs6KVa65PhcM5EbKCo9/eLegJo4bDbXrA/2G
DDA2p0acgj5BlMaRGcq1QM3zpuTe5ibROOq7qm2fzNggaQjcMGmMc2L31uDYs6q3
hiAO4qq9r5AHezdktKWTMaLNXtidUCxBWWAnit2xtBGSo2nSrTeSJzRC5bJ4d8PB
oEWSymjzNKTUNBGTfDiT54yCC9a3F3HJW/3X/CVCcO3yxpHjySh2lZDajqXc+Kfu
AnTa0Wx1BuJPiv3M8l8ZGOD0M2rjjj951AfzicvylgA7vs6qcDVS+WDtP0mmq0KY
GJBjRtPgOoypZK9a21nPdSKNLcql3CfrvqkoFR7nAAMZsZrckKbi8+UgrT/h0ba2
uAHYwlu/Sr6Ht5nYPJvHaD2J0gVoPx7MqtHcLAs1dGfv0aqq3JD4wuGI/nlEH/Ti
P6gE2ZM9LhsnxpTNPpXnXaP3+KDd99XBt4rp4QDBIP3vM1WzjXwApVmm6gcHR9oi
L3LoJKKJ8s1TT7QK08E95UU3KIvxaMnm/9mNj+rzPdIFS2ptAa+plE/ryU7MbG+Q
5eFqvNA5PWbNZ5rK1Wiju0XAeLCaeCapTyPuib20SYrYvSXsvL79rkjIF1Flcf2S
b7ENC+PIxL5ht9xXOuSAipPjQQDQlwlBs5YC5UL8mfP41hAdIok=
=ZxR8
-----END PGP SIGNATURE-----

--Ox0NLB5i478NUuI9QiF3HU2nc7Lj1a9BN--


From nobody Wed Jan 22 06:54:18 2020
Return-Path: <pkyzivat@alum.mit.edu>
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 669BB1200E9 for <xml2rfc@ietfa.amsl.com>; Wed, 22 Jan 2020 06:54:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alum.mit.edu
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 UYXjXI2tvDJE for <xml2rfc@ietfa.amsl.com>; Wed, 22 Jan 2020 06:54:13 -0800 (PST)
Received: from NAM10-BN7-obe.outbound.protection.outlook.com (mail-bn7nam10on2041.outbound.protection.outlook.com [40.107.92.41]) (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 6BF7812007C for <xml2rfc@ietf.org>; Wed, 22 Jan 2020 06:54:13 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=KoWLsjy8aIFAJy0RfgE7T+SDQbUnPjVb1lDXdCICh9kFrOueEgQAfwj9lnLX4s1bZMjUuPwT1YE50W/5eQUtYaLACylWF3owQjr3GlQqEnMbYyvPCEE8Ve9M67hc+DzQWZONvzEfKtAFs2Mt684Ce3qGqYO2lGTIHjXddxy3BSJ/c9PFzrt3Jl4BuN+zjsPLpKf/5gOTeXm0kudYDyIwJ5ERBFmK43nou2bI3NzaHKWdpEvcAgWRwVEzXKemwDtWjXSgHTw2Irs1gMGCGuCfUAAFz1DYQEr/QRqkZ1pLoDEiRQeckGc8caWVU95De4Uh2QT7D1w319I9XRB2eTd0Zg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+4+Xu8fZsrtTrt+irbubRpSeQrUpjdhfVrMXIvcXNF8=; b=ULDAhkMaWv/H1hNOX+y9On5vFr+1ZPLaZNfIPKgs57MmKKaB5s7PfUJCJnTePE3p6PiX7YKfKnORS+ktrOwBJKo4GQ8DCRfEQsL0jxc/Q7F8dmxUgxFCdF7sIVgjdEvSfGX9Nns18DPVuQlxKTnbl8zjSjohZf1nltRuGh/sVsxm+1miakF179p91A/JYZ1IlIwrzx/mJIUJXHBY8peo47GPqIuXfCgmrUuqeveZ8prRHJaS3af4qrNCx3MSeCqjIcxJ1XMZarjDjuBfK49FkuMzACrB1LlE4rxYxmpGK/aFbJVhrGvfFiTxgMUeKhzk6XRtv6l/AG2Wrez2PwZShQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 18.7.68.33) smtp.rcpttodomain=levkowetz.com smtp.mailfrom=alum.mit.edu; dmarc=bestguesspass action=none header.from=alum.mit.edu; dkim=none (message not signed); arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alum.mit.edu; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+4+Xu8fZsrtTrt+irbubRpSeQrUpjdhfVrMXIvcXNF8=; b=CE9RTm8/bQ9ek2L6xj1+YSHQGhBmQvVEvqS929Y63hR+3JVKrfMjfefLjkhJfKD9Yu3r2BdUFbYwiFAjAXkUk/uPe8Jww7XjYFPo44Sol9HafT87++L5uhoTHNqY/kAovN5uMv3ttvVGjATXHzCST75c2P7LLxwKy6w3y5tD2pM=
Received: from BN4PR12CA0006.namprd12.prod.outlook.com (2603:10b6:403:2::16) by MWHPR12MB1565.namprd12.prod.outlook.com (2603:10b6:301:b::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2644.18; Wed, 22 Jan 2020 14:54:11 +0000
Received: from SN1NAM02FT022.eop-nam02.prod.protection.outlook.com (2a01:111:f400:7e44::207) by BN4PR12CA0006.outlook.office365.com (2603:10b6:403:2::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2644.19 via Frontend Transport; Wed, 22 Jan 2020 14:54:11 +0000
Authentication-Results: spf=pass (sender IP is 18.7.68.33) smtp.mailfrom=alum.mit.edu; levkowetz.com; dkim=none (message not signed) header.d=none;levkowetz.com; dmarc=bestguesspass action=none header.from=alum.mit.edu;
Received-SPF: Pass (protection.outlook.com: domain of alum.mit.edu designates 18.7.68.33 as permitted sender) receiver=protection.outlook.com;  client-ip=18.7.68.33; helo=outgoing-alum.mit.edu;
Received: from outgoing-alum.mit.edu (18.7.68.33) by SN1NAM02FT022.mail.protection.outlook.com (10.152.72.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2665.18 via Frontend Transport; Wed, 22 Jan 2020 14:54:10 +0000
Received: from Kokiri.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id 00MEs754002978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 22 Jan 2020 09:54:08 -0500
To: Henrik Levkowetz <henrik@levkowetz.com>, xml2rfc@ietf.org
References: <87E86D51-F37A-4800-BC14-6AA7E5E7EA4A@orandom.net> <751dd301-a89b-13b2-27b4-16beaced5de3@levkowetz.com> <DA4F22F5-5A43-4671-B69B-EDF61F976623@orandom.net> <61971d80-1c1e-bdf7-a986-0cfe9de157e6@levkowetz.com> <6C8FDE4E-88F8-4862-A9CC-3D1E9B0DCD4C@orandom.net> <fe468ed5-3d9b-88b2-8403-f8482bb1f55b@levkowetz.com> <647a593e-8104-0a59-bd0b-fb377f49201e@levkowetz.com> <A6C1B0DF-EAE0-46DC-9539-F56A3192E336@orandom.net> <43f689a4-7bc5-5e8c-0ca6-0ca785a77c8e@levkowetz.com> <7FAEB626-F120-4A03-91D8-F3FE6FE26001@orandom.net> <ffabdb16-89af-2f62-8d2e-db080a73d7ec@alum.mit.edu> <b379d083-350f-72eb-0e33-4abe53650e5a@levkowetz.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <d7c37251-3269-d6f6-f09b-278f6294c2d2@alum.mit.edu>
Date: Wed, 22 Jan 2020 09:54:07 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <b379d083-350f-72eb-0e33-4abe53650e5a@levkowetz.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:18.7.68.33; IPV:CAL; SCL:-1; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10009020)(396003)(136003)(376002)(346002)(39860400002)(199004)(189003)(31686004)(5660300002)(75432002)(26005)(186003)(53546011)(8936002)(246002)(26826003)(7596002)(70586007)(70206006)(478600001)(316002)(36906005)(2906002)(356004)(86362001)(966005)(786003)(31696002)(956004)(336012)(2616005)(8676002); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR12MB1565; H:outgoing-alum.mit.edu; FPR:; SPF:Pass; LANG:en; PTR:outgoing-alum.mit.edu; A:1; MX:1; 
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: d6ce63ce-ed46-4c26-fb6a-08d79f4af066
X-MS-TrafficTypeDiagnostic: MWHPR12MB1565:
X-Microsoft-Antispam-PRVS: <MWHPR12MB156594B09B65AEF1E0141231F90C0@MWHPR12MB1565.namprd12.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:8882;
X-Forefront-PRVS: 029097202E
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: TTEhtNU/tursOm1o/mQMeRAXQdGr40RF1i1pixPD7oIHRoLkMs3YohLuJ9m5ypgLNnL2ssjs/3mCZEktUUzRVtlPn0jOyVhs6+ee1z0UOwZezbva4QV9ZypasYzjx6NxzKNVBr9eP7/3q4F6DIS6sLBYt0KOkrb6P6Ay8/0v+CS7SQE3jjxXjwig5F3VRcnZr/tOQ6DO/v3NEPAL6+Uucaep9FxZ7crE1SzfId17Y/QgZFmO6LRVrHaybi++eSXg10M6q3trO5LtakB+xanxTxalE/+vQlAt9jP0YqCl99LCuHD8yEQvXCha8XGMlE+Vyc1sDifatOT27UNv0vLTIZThDkMlSzj+CjeI+xJpq8oLlajUFo5X9x17H5v8dt2EfAD0WJhLIUGYQKjGasyBjDNKHAVIkjIvpiLCLLQ/OSJ0fk8s2MSoSJzP+TP1++4f/AwX+mQCIF4XJeeCKHemzr3IJ5u9O8++4+Hj4lq7a30=
X-OriginatorOrg: alum.mit.edu
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 22 Jan 2020 14:54:10.3749 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: d6ce63ce-ed46-4c26-fb6a-08d79f4af066
X-MS-Exchange-CrossTenant-Id: 3326b102-c043-408b-a990-b89e477d582f
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=3326b102-c043-408b-a990-b89e477d582f; Ip=[18.7.68.33];  Helo=[outgoing-alum.mit.edu]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR12MB1565
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/EFo6dWN1oeN9BjyibxrMe_06g2A>
Subject: Re: [xml2rfc] Novice bad user on device, or Catch-22?
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: Wed, 22 Jan 2020 14:54:17 -0000

I don't have a new draft on the horizon right now, so it will probably 
be awhile till I need a template.

Is there a way to search for drafts with v3 xml posted?
Other than that, I think a pointer to some templates from the tools page 
would be most easily found.

Otherwise, I'd probably be inclined to find a similar document with v2 
xml and convert that as a starting point.

	Thanks,
	Paul

On 1/21/20 12:03 PM, Henrik Levkowetz wrote:
> Hi Paul,
> 
> On 2020-01-21 17:34, Paul Kyzivat wrote:
>> On 1/21/20 8:37 AM, David R. Oran wrote:
>>> On 21 Jan 2020, at 3:26, Henrik Levkowetz wrote:
>>>
>>>> Hi Dave,
>>>>
>>> [snipping out to get to your question]
>>>
>>>> On 2020-01-21 06:51, David R. Oran wrote:
>>>>
>>>> And yes, having v3 templates would be helpful.  I'll see if I can fix that
>>>> too.  Where would you normally grab a template?
>>>>
>>> well, by googling :-)
>>> Probably the home ought to be off the tools home page at tools.ietf.org. There’s already a “templates” link on that page - it’s to Elwyn Davies examples, and ought to have a V3 template.
>>
>> I've just been lurking, but seems like a good time to comment...
>>
>> I normally get my "template" by starting with some similar document,
>> either one of my own if I have a suitable one, or from some document I
>> am generally aware of.
>>
>> But that doesn't work well now when there aren't many v3 documents to
>> crib from.
>>
>> I guess I would be inclined to grab the v2 for some similar document and
>> convert it. But I guess maybe that won't give optimal style for the new
>> document. So maybe having a recommended source of pure templates and
>> also some "real" documents that are judged to be "good" examples would
>> be helpful.
> 
> The RPC might have some prepublication files that have been edited to
> their standards.
> 
> For a schema v3 template, I've now run the converter on Elwyn's template
> to produce a v3 version, and linked to that from https://tools.ietf.org/.
> 
> 
> 	Henrik
> 


From nobody Wed Jan 29 07:48:48 2020
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 1A155120090 for <xml2rfc@ietfa.amsl.com>; Wed, 29 Jan 2020 07:48:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 VurSAO9Bky51 for <xml2rfc@ietfa.amsl.com>; Wed, 29 Jan 2020 07:48:44 -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 C6375120020 for <xml2rfc@ietf.org>; Wed, 29 Jan 2020 07:48:44 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 8DB3962133 for <xml2rfc@ietf.org>; Wed, 29 Jan 2020 10:48:43 -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 HjMI1GUt2Iti for <xml2rfc@ietf.org>; Wed, 29 Jan 2020 10:48:38 -0500 (EST)
Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id C460B62123 for <xml2rfc@ietf.org>; Wed, 29 Jan 2020 10:48:38 -0500 (EST)
To: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
From: Robert Moskowitz <rgm@htt-consult.com>
Message-ID: <64044281-a1cb-87c8-f15d-62af751b6bb8@htt-consult.com>
Date: Wed, 29 Jan 2020 10:48:33 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/pvq9U-2FV9e1uBRnRphhBmzF57U>
Subject: [xml2rfc] Boilerplate error on xml submission
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: Wed, 29 Jan 2020 15:48:47 -0000

Colleague is working on a draft from template I supplied.  It worked for 
me earlier in the month.

We are getting the following idnit:

   Showing Errors (**), Flaws (~~), Warnings (==), and Comments (--).
   Errors MUST be fixed before draft submission.  Flaws SHOULD be fixed 
before draft submission.

   Checking boilerplate required by RFC 5378 and the IETF Trust (see
   https://trustee.ietf.org/license-info):
----------------------------------------------------------------------------

   ** The document seems to lack a License Notice according IETF Trust
      Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009
      Section 6.b -- however, there's a paragraph with a matching beginning.
      Boilerplate error?

      IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(ii), 
paragraph 3:
         This document is subject to BCP 78 and the IETF Trust's Legal 
Provisions
         Relating to IETF Documents
         (https://trustee.ietf.org/license-info) in effect on the date of
         publication of this document.  Please review these documents
         carefully, as they describe your rights and restrictions with
         respect to this document.

      ... text found in draft:
         This document is subject to BCP 78 and the IETF Trust's Legal 
Provisions
         Relating to IETF Documents
         (https://trustee.ietf.org/license-info) in effect on the date of
         publication of this document.
.....................................^


I believe this is due to the following:

<rfc xmlns:xi="http://www.w3.org/2001/XInclude" 
docName="draft-card-tmrid-uas-01"
     category="std" ipr="trust200902" obsoletes="" updates="" 
submissionType="IETF"
     xml:lang="en" tocInclude="true" symRefs="true" sortRefs="true" 
version="3">

Is there something newer to XInclude?  Or is the problem somewhere else?

thanks


From nobody Wed Jan 29 08:01:18 2020
Return-Path: <henrik@levkowetz.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 042AC12011B for <xml2rfc@ietfa.amsl.com>; Wed, 29 Jan 2020 08:01:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 H7aVOp5rLauV for <xml2rfc@ietfa.amsl.com>; Wed, 29 Jan 2020 08:01:13 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50836120833 for <xml2rfc@ietf.org>; Wed, 29 Jan 2020 08:01:09 -0800 (PST)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:57060 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1iwplo-0003R5-1R; Wed, 29 Jan 2020 08:01:08 -0800
To: Robert Moskowitz <rgm@htt-consult.com>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>
References: <64044281-a1cb-87c8-f15d-62af751b6bb8@htt-consult.com>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <9e3a3287-d2d0-8f57-a277-f0696a147597@levkowetz.com>
Date: Wed, 29 Jan 2020 17:00:41 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <64044281-a1cb-87c8-f15d-62af751b6bb8@htt-consult.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: xml2rfc@ietf.org, rgm@htt-consult.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/rfSYRxGBPZGBLAwHCg6IoRnvmIk>
Subject: Re: [xml2rfc] Boilerplate error on xml submission
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: Wed, 29 Jan 2020 16:01:16 -0000

Hi Bob,

Could you send the .txt or .xml file that triggered this?


Best regards,

	Henrik


On 2020-01-29 16:48, Robert Moskowitz wrote:
> Colleague is working on a draft from template I supplied.  It worked for 
> me earlier in the month.
> 
> We are getting the following idnit:
> 
>    Showing Errors (**), Flaws (~~), Warnings (==), and Comments (--).
>    Errors MUST be fixed before draft submission.  Flaws SHOULD be fixed 
> before draft submission.
> 
>    Checking boilerplate required by RFC 5378 and the IETF Trust (see
>    https://trustee.ietf.org/license-info):
> ----------------------------------------------------------------------------
> 
>    ** The document seems to lack a License Notice according IETF Trust
>       Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009
>       Section 6.b -- however, there's a paragraph with a matching beginning.
>       Boilerplate error?
> 
>       IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(ii), 
> paragraph 3:
>          This document is subject to BCP 78 and the IETF Trust's Legal 
> Provisions
>          Relating to IETF Documents
>          (https://trustee.ietf.org/license-info) in effect on the date of
>          publication of this document.  Please review these documents
>          carefully, as they describe your rights and restrictions with
>          respect to this document.
> 
>       ... text found in draft:
>          This document is subject to BCP 78 and the IETF Trust's Legal 
> Provisions
>          Relating to IETF Documents
>          (https://trustee.ietf.org/license-info) in effect on the date of
>          publication of this document.
> .....................................^
> 
> 
> I believe this is due to the following:
> 
> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" 
> docName="draft-card-tmrid-uas-01"
>      category="std" ipr="trust200902" obsoletes="" updates="" 
> submissionType="IETF"
>      xml:lang="en" tocInclude="true" symRefs="true" sortRefs="true" 
> version="3">
> 
> Is there something newer to XInclude?  Or is the problem somewhere else?
> 
> thanks
> 
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc
> 


From nobody Wed Jan 29 08:06:06 2020
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 5659112011A for <xml2rfc@ietfa.amsl.com>; Wed, 29 Jan 2020 08:06:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.599
X-Spam-Level: 
X-Spam-Status: No, score=-1.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_AFFORDABLE=1, RCVD_IN_DNSWL_LOW=-0.7, 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 rAX_OEP_t27A for <xml2rfc@ietfa.amsl.com>; Wed, 29 Jan 2020 08:06:01 -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 895FB1200BA for <xml2rfc@ietf.org>; Wed, 29 Jan 2020 08:06:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 18F1362133; Wed, 29 Jan 2020 11:06:00 -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 qW+Hkt-96cNG; Wed, 29 Jan 2020 11:05:41 -0500 (EST)
Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id AC0C462123; Wed, 29 Jan 2020 11:05:41 -0500 (EST)
To: Henrik Levkowetz <henrik@levkowetz.com>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>
References: <64044281-a1cb-87c8-f15d-62af751b6bb8@htt-consult.com> <9e3a3287-d2d0-8f57-a277-f0696a147597@levkowetz.com>
From: Robert Moskowitz <rgm@htt-consult.com>
Message-ID: <bb193109-8d4a-5d91-9470-cb53eac63843@htt-consult.com>
Date: Wed, 29 Jan 2020 11:05:34 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <9e3a3287-d2d0-8f57-a277-f0696a147597@levkowetz.com>
Content-Type: multipart/mixed; boundary="------------169D1B4F197A890B7408B449"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/YblfGuF6XktgpZF2HPAz1J_eh9c>
Subject: Re: [xml2rfc] Boilerplate error on xml submission
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: Wed, 29 Jan 2020 16:06:04 -0000

This is a multi-part message in MIME format.
--------------169D1B4F197A890B7408B449
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Here is the xml.


On 1/29/20 11:00 AM, Henrik Levkowetz wrote:
> Hi Bob,
>
> Could you send the .txt or .xml file that triggered this?
>
>
> Best regards,
>
> 	Henrik
>
>
> On 2020-01-29 16:48, Robert Moskowitz wrote:
>> Colleague is working on a draft from template I supplied.  It worked for
>> me earlier in the month.
>>
>> We are getting the following idnit:
>>
>>     Showing Errors (**), Flaws (~~), Warnings (==), and Comments (--).
>>     Errors MUST be fixed before draft submission.  Flaws SHOULD be fixed
>> before draft submission.
>>
>>     Checking boilerplate required by RFC 5378 and the IETF Trust (see
>>     https://trustee.ietf.org/license-info):
>> ----------------------------------------------------------------------------
>>
>>     ** The document seems to lack a License Notice according IETF Trust
>>        Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009
>>        Section 6.b -- however, there's a paragraph with a matching beginning.
>>        Boilerplate error?
>>
>>        IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(ii),
>> paragraph 3:
>>           This document is subject to BCP 78 and the IETF Trust's Legal
>> Provisions
>>           Relating to IETF Documents
>>           (https://trustee.ietf.org/license-info) in effect on the date of
>>           publication of this document.  Please review these documents
>>           carefully, as they describe your rights and restrictions with
>>           respect to this document.
>>
>>        ... text found in draft:
>>           This document is subject to BCP 78 and the IETF Trust's Legal
>> Provisions
>>           Relating to IETF Documents
>>           (https://trustee.ietf.org/license-info) in effect on the date of
>>           publication of this document.
>> .....................................^
>>
>>
>> I believe this is due to the following:
>>
>> <rfc xmlns:xi="http://www.w3.org/2001/XInclude"
>> docName="draft-card-tmrid-uas-01"
>>       category="std" ipr="trust200902" obsoletes="" updates=""
>> submissionType="IETF"
>>       xml:lang="en" tocInclude="true" symRefs="true" sortRefs="true"
>> version="3">
>>
>> Is there something newer to XInclude?  Or is the problem somewhere else?
>>
>> thanks
>>
>> _______________________________________________
>> xml2rfc mailing list
>> xml2rfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>


--------------169D1B4F197A890B7408B449
Content-Type: text/xml; charset=UTF-8;
 name="draft-card-tmrid-uas-01.xml"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="draft-card-tmrid-uas-01.xml"

<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>
<?rfc iprnotified="no" ?>
<?rfc strict="no" ?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" docName="draft-card-tmrid-uas-01"
	category="std" ipr="trust200902" obsoletes="" updates="" submissionType="IETF" 
	xml:lang="en" tocInclude="true" symRefs="true" sortRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 2.37.1 -->
<front>
	<title abbrev="UAS Remote ID">UAS Remote ID</title>
	<seriesInfo name="Internet-Draft" value="draft-card-tmrid-uas-00"/>
	<author fullname="Stuart W. Card" initials="S." surname="Card">
	<organization>AX Enterprize</organization>
	<address>
	  <postal>
		<street>4947 Commercial Drive</street>
		<city>Yorkville</city>
		<region>NY</region>
		<code>13495</code>
		<country>USA</country>
	  </postal>
	  <email>stu.card@axenterprize.com</email>
	</address>
	</author>
	<author fullname="Adam Wiethuechter" initials="A." surname="Wiethuechter">
	<organization>AX Enterprize</organization>
	<address>
	  <postal>
		<street>4947 Commercial Drive</street>
		<city>Yorkville</city>
		<region>NY</region>
		<code>13495</code>
		<country>USA</country>
	  </postal>
	  <email>adam.wiethuechter@axenterprize.com</email>
	</address>
	</author>
    <author fullname="Robert Moskowitz" initials="R" surname="Moskowitz">
	<organization>HTT Consulting</organization>
	<address>
	  <postal>
		<street/>
		<city>Oak Park</city>
		<region>MI</region>
		<code>48237</code>
		<country>USA</country>
	  </postal>
	  <email>rgm@labs.htt-consult.com</email>
	</address>
	</author>
    <date year="2020"/>
    <area>Internet</area>
    <workgroup>TMRID</workgroup>
    <keyword>RFC</keyword>
    <keyword>Request for Comments</keyword>
    <keyword>I-D</keyword>
    <keyword>Internet-Draft</keyword>
    <keyword>HIP</keyword>
    <keyword>TMRID</keyword>
<abstract>
<t>
	This document is an Applicability Statement for various IETF 
	Technical Specifications, including the Host Identity Protocol 
	(HIPv2) and the Domain Name System (DNS), complementing emerging 
	external standards for Unmanned Aircraft System (UAS) remote 
	identification (RID). The objectives are: to facilitate use of 
	existing Internet services to support UAS RID and to enable 
	enhanced RID related services; and to enable verification that UAS 
	RID information is trustworthy (to some extent, even in the absence 
	of Internet connectivity at the receiving node).
</t>
</abstract>
</front>
<middle>
<section numbered="true" toc="default"> <name>Introduction</name>
<t>
	Emerging Civil Aviation Authority (CAA) regulations worldwide, 
	exemplified by current United States (US) Federal Aviation 
	Administration (FAA) rulemaking, will soon mandate, and many safety 
	and other considerations dictate (even absent regulations), that 
	Unmanned Aircraft Systems (UAS) be remotely identifiable. CAAs are 
	expected and FAA has stated its intent to require compliance with 
	industry consensus standards.
</t>
<t>  
	ASTM International, Technical Committee F38 (UAS), Subcommittee 
	F38.02 (Aircraft Operations), Work Item WK65041 (UAS Remote ID and 
	Tracking), is a Proposed New Standard <xref target="WK65041" 
	format="default"/>. It defines 2 means of UAS remote identification 
	(RID): Network RID via the Internet; and Broadcast RID via a 
	one-way data link direct from the Unmanned Aircraft (UA) to the 
	observer's device. Network RID depends upon Internet connectivity 
	between the observer and either the UA itself or any of various 
	proxies. Broadcast RID should need Internet (or other Wide Area 
	Network) connectivity only for UAS registry information lookup 
	using the directly locally received UAS ID as a key.
</t>
<t>
	The need for near-universal deployment of UAS RID is pressing. This 
	implies the need to support use by observers of already ubiquitous 
	mobile devices (smartphones and tablets). UA onboard RID devices 
	are severely constrained in Size, Weight and Power (SWaP). Cost is 
	a significant impediment to the necessary near-universal adoption 
	of UAS send and observer receive RID capabilities. To accomodate 
	the most severely constrained cases, all these conspire to motivate 
	system design decisions, especially for the Broadcast RID data 
	link, which complicate the protocol design problem: one-way links; 
	extremely short packets; and Internet-disconnected operation of UA 
	onboard devices. Internet-disconnected operation of observer 
	devices has been deemed by ASTM F38.02 too infrequent to address, 
	but for some users is important and presents further challenges.
</t>
<t>
	Heavyweight security protocols are infeasible, yet trustworthiness 
	of UAS RID information is essential. Even the most basic datum, the 
	UAS ID string (typically number) itself, under <xref 
	target="WK65041" format="default"/>, can be merely an 
	unsubstantiated claim.
</t>
<t>
	Further, an ID is not an end in itself; it exists to enable lookups 
	and provision of services complementing mere identification, e.g. 
	dynamic establishment of secure communications between the observer 
	and the UAS pilot. <xref target="WK65041" format="default"/> 
	neither fully specifies nor appears to facilitate these functions, 
	especially in the case where the observer lacks real time Internet 
	access.
</t>
<t>
	Finally, <xref target="WK65041" format="default"/> proposes the use 
	of plaintext and mostly static UAS ID strings. Even if lookup from 
	these to operator Personally Identifiable Information (PII) is 
	successfully limited to strongly authenticated personnel, properly 
	authorized per policy: static IDs enable trivial correlation of 
	patterns of use, unacceptable in many applications, e.g. package 
	delivery routes of competitors.
</t>
<t>
	IETF can help by providing  expertise as well as mature and 
	evolving standards. Host Identity Protocol (HIPv2) <xref 
	target="RFC7401" format="default"/> and its Domain Name System 
	(DNS) extensions <xref target="RFC8005" format="default"/> can
	complement 	emerging external standards for UAS RID, to facilitate
	utilization of existing and provision of enhanced network services,
	and to enable verification that UAS RID information is trustworthy
	(to some extent, even in the absence of Internet connectivity at the 
	receiving node).
</t>
</section>
<section anchor="terms" numbered="true" toc="default"> <name>Terms and Definitions</name>
<section numbered="true" toc="default"> <name>Requirements Terminology</name>
<t>
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", 
	and "OPTIONAL" in this document are to be interpreted as described 
	in BCP 14 <xref target="RFC2119" format="default"/> <xref 
	target="RFC8174" format="default"/> when, and only when, they 
	appear in all capitals, as shown here.
</t>
</section>
<section numbered="true" toc="default"> <name>Definitions</name>
	<dl newline="true" spacing="normal">
		<dt>CAA</dt>
		<dd>
			Civil Aviation Authority. An example is the Federal 
			Aviation Administration (FAA) in the United States of 
			America.
		</dd>
		<dt>C2</dt>
		<dd>
			Command and Control. A set of organizational and technical 
			attributes and processes that employs human, physical, and 
			information resources to solve problems and accomplish 
			missions. Mainly used in military contexts.
		</dd>
		<dt>GCS</dt>
		<dd>
			Ground Control Station. The part of the UAS that the remote 
			pilot uses to exercise C2 over the UA, whether by remotely 
			exercising UA flight controls to fly the UA, by setting GPS 
			waypoints, or otherwise directing its flight.
		</dd>
		<dt>HI</dt>
		<dd>
			Host Identity. The public key portion of an asymmetric 
			keypair from HIP. In this document it is assumed that the 
			HI is based on a EdDSA25519 keypair. This is supported by 
			new crypto defined in <xref 
			target="I-D.moskowitz-hip-new-crypto" format="default"/>.
		</dd>
		<dt>HIT</dt>
		<dd>
			Host Identity Tag. A 128 bit handle on the HI. Defined in 
			HIPv2 <xref target="RFC7401" format="default"/>.
		</dd>
		<dt>HHIT</dt>
		<dd>
			Hierarchical Host Identity Tag. A HIT with extra 
			information not found in a standard HIT. Defined in <xref 
			target="I-D.moskowitz-hip-hierarchical-hit" 
			format="default"/>.
		</dd>
		<dt>UA</dt>
		<dd>
			Unmanned Aircraft. Typically a military or commercial 
			"drone" but can include any and all aircraft that are 
			unmanned.
		</dd>
		<dt>UAS</dt>
		<dd>
			Unmanned Aircraft System. Composed of UA, all required 
			on-board subsystems, payload, control station, other 
			required off-board subsystems, any required launch and 
			recovery equipment, all required crew members, and C2 links 
			between UA and control station.
		</dd>
		<dt>UTM</dt>
		<dd>
			UAS Traffic Management. A "traffic management" ecosystem 
			for "uncontrolled" UAS operations separate from, but 
			complementary to, the FAA's Air Traffic Management (ATM) 
			system for "controlled" operations of manned aircraft.
		</dd>
		<dt>USS</dt>
		<dd>
			UAS Service Supplier. Provide UTM services to support the 
			UAS community, to connect Operators and other entities to 
			enable information flow across the USS network, and to 
			promote shared situational awareness among UTM 
			participants. (From FAA UTM ConOps V1, May 2018).
		</dd>
		<dt>RID</dt>
		<dd>
			Remote ID. System for identifying UA during flight by other parties.
		</dd>
		<dt>Observer</dt>
		<dd>
			Referred to in other UAS documents as a "user", but there 
			are also other classes of RID users, so we prefer 
			"observer" to denote an individual who has observed an UA 
			and wishes to know something about it, starting with its 
			ID.
		</dd>
		<dt>UAS ID</dt>
		<dd>
			Unique UAS identifier. Per <xref target="WK65041" 
			format="default"/>, maximum length of 20 bytes.
		</dd>
		<dt>UAS ID Type</dt>
		<dd>
			Identifier type index. Per <xref target="WK65041" 
			format="default"/>, 4 bits, values 0-3 already specified.
		</dd>
		<dt>RID SP</dt>
		<dd>
			UAS RID Service Provider. System component that compiles 
			information from various sources (and methods) in its given 
			service area.
		</dd>
		<dt>RID DP</dt>
		<dd>
			UAS RID Display Provider. System component that requests 
			data from one or more RID SP and aggregates them to display 
			to a user application on a device.
		</dd>
		<dt>UAS RID Verification Service</dt>
		<dd>
			System component designed to handle the authentication 
			requirements of RID by offloading verification to a web 
			hosted service.
		</dd>
	</dl>
</section>
</section>
<section numbered="true" toc="default"> <name>UAS RID Problem Space</name>
<t>
	UA may be fixed wing Short Take-Off and Landing (STOL), rotary wing 
	(e.g. helicopter) Vertical Take-Off and Landing (VTOL), or hybrid. 
	They may be single engine or multi engine. The most common today 
	are multicopters: rotary wing, multi engine. The explosion in UAS 
	was enabled by hobbyist development, for multicopters, of advanced 
	flight stability algorithms, enabling even inexperienced pilots tp 
	take off, fly to a location of interest, hover, and return to the 
	take-off location or land at a distance. UAS can be remotely 
	piloted by a human (e.g. with a joystick) or programmed to proceed 
	from Global Positioning System (GPS) waypoint to waypoint in a weak 
	form of autonomy; stronger autonomy is coming. UA are "low 
	observable": they typically have a small radar cross section; they 
	make noise quite noticeable at short range but difficult to detect 
	at distances they can quickly close (500 meters in under 17 seconds 
	at 60 knots); they typically fly at low altitudes (for the small 
	UAS to which RID applies, under 400 feet Above Ground Level in the 
	US); they are highly maneuverable so can fly under trees and 
	between buildings.
</t>
<t>
	UA can carry payloads including sensors, cyber and kinetic weapons 
	or can be used themselves as weapons by flying them into targets. 
	They can be flown by clueless, careless or criminal operators. Thus 
	the most basic function of UAS RID is "Identification Friend or 
	Foe" to mitigate the significant threat they present. Numerous 
	other applications can be enabled or facilitated by RID: consider 
	the importance of identifiers in many Internet protocols and 
	services.
</t>
<t>
	Network RID from the UA itself (rather than from a proxy) and 
	Broadcast RID require one or more wireless data links from the UA, 
	but such communications are challenging due to $SWaP constraints 
	and low altitude flight amidst structures and foliage over terrain.
</t>
<section numbered="true" toc="default"> <name>Network RID</name>
<t>
	Network RID has several variants. The UA may have persistent onboard
    Internet connectivity, in which case it can consistently source RID
    information directly over the Internet. The UA may have intermittent
    onboard Internet connectivity, in which case a proxy must source RID
    information whenever the UA itself is offline. The UA may not have
    Internet connectivity of its own, but have instead some other form
    of communications to a (typically ground) node that can relay RID
    information to the Internet; this would typically be the GCS (which
    to perform its function must know where the UA is) or USS (which in
    the UTM system is required to be kept informed by the UAS operator).
    The UA may have no means of sourcing RID information, in which case
    the GCS, USS or other proxy may source it. In the extreme case, this
    would be the pilot using a web browser to designate, to a USS or
    other UTM entity, a time-bounded airspace volume in which an
    operation will be conducted; this may impede disambiguation of ID if
    multiple UAS operate in the same or overlapping spatio-temporal
    volumes.
</t>
<t>
	In most cases in the near term, if the RID information is fed to 
	the Internet directly by the UA or remote pilot, the first hop data 
	links will be cellular Long Term Evolution (LTE) or WiFi, but 
	provided the data link can support at least IP and ideally TCP, its 
	type is generally immaterial to the higher layer protocols. The 
	ultimate source of Network RID information feeds a RID Service 
	Provider (SP), which essentially proxies for that and other 
	sources; the ultimate consumer of  Network RID information obtains 
	it from a RID Display Provider (DP). Each DP aggregates information 
	from all SPs that have UA currently operating in the airspace for 
	which that DP is cognizant.
</t>
<t>
	Network RID is the more flexible and less constrained of the UAS 
	RID means specified in <xref target="WK65041" format="default"/>. 
	Any IETF work needed to support or leverage it is left for later 
	efforts; it is not further addressed herein or in other initial 
	tm-rid documents.
</t>
</section>
<section numbered="true" toc="default"> <name>Broadcast RID</name>
<t>
	<xref target="WK65041" format="default"/> specifies 3 Broadcast RID 
	data links: Bluetooth 4.X; Bluetooth 5.X Long Range; and Wifi with 
	Neighbor Awareness Networking (NAN). For compliance with this 
	standard, an UA must broadcast (using advertisement mechanisms 
	where no other option supports broadcast) on at least one of these; 
	if broadcasting on Bluetooth 5.x, it is also required concurrently 
	to do so on 4.x (referred to in <xref target="WK65041" 
	format="default"/> as Bluetooth Legacy).
</t>
<t>
	The selection of the Broadcast medium was driven by research into 
	what is commonly available on 'ground' units (smartphones and 
	tablets) and what was found as prevalent or 'affordable' in UA. 
	Further, there must be an API for the UAS receiving application to 
	have access to these messages.  At this time, only Bluetooth 4.X 
	support is readily available, thus the current focus is on working 
	within the 26 byte limit of the Bluetooth 4.X "Broadcast Frame" 
	that goes out on the  beacon channels.
</t>
<t>
	Finally, the 26 byte limit of the Bluetooth 4.1 "Broadcast Frame" 
	strictly enforces the RID maximum length of 20 bytes.
</t>
</section>
      <!-- This section need to get reworded to be more broad or removed -->
<section numbered="true" toc="default"> <name>TM-RID Focus Problem Space</name>
<t>
	TM-RID will focus on adding immediate usability, thus trust to, 
	Broadcast RID. The one-way nature of Broadcast RID precludes any 
	stateful security protocol. Under <xref target="WK65041" 
	format="default"/>, any UA can announce a RID and an observer would 
	be seriously challenged to validate it or any other information 
	about the UA looked up from it. Thus providing trust in the RID and 
	related trust for all Broadcast messages is critical for the safe 
	and secure operation of UAs.
</t>
<t>
	Three levels of functionality will be considered:
</t>
<ol spacing="normal" type="1">
	<li>
		verify that HHIT is duly registered with a known registry AND 
		that any messages signed with its key came from it;
	</li>
	<li>    
		look up not only static UAS registry and dynamic UTM 
		information but also Intenet direct contact information for 
		services relating to the UA, its current mission, etc., 
		including communications with the remote pilot (or proxy) and 
		USS;
	</li>
	<li>
		dynamically establish strongly mutually authenticated, E2E 
		strongly encrypted communications with the UAS RID sender and 
		entities looked up via (2) above.
	</li>
</ol>
</section>
</section>
<section numbered="true" toc="default"> <name>Alternatives for IETF work on Trustworthy IDs</name>
<section numbered="true" toc="default"> <name>Requirements of Trustworthy IDs</name>
<t>
	Just a couple of requirements:
</t>
<ol spacing="normal" type="1">
	<!-- 3 levels:
    1 verify that HHIT is duly registered with a known registry AND
    that any messages signed with its key came from it
    2 look up not only static UAS registry and dynamic UTM information
    but also Intenet direct contact information for services relating to
    the UA, its current mission, etc., including communications with the
    remote pilot (or proxy) & USS
    3 dynamically establish strongly mutually authenticated, E2E
    strongly encrypted communications with the UAS RID sender & entities
    looked up via (2) above
    -->
	<li>
		The ID MUST be 20 bytes or smaller.
	</li>
	<li>
		It MUST be non-spoofable within the context of Remote ID 
		broadcast messages (some collection of messages provides proof 
		of UA ownership of ID).
	</li>
	<li>
		In context (that is in a Remote ID Broadcast message), just the 
		ID provides enough information on how at least the observer's 
		USS (UAS Service Provider / Display Provider) can provide both 
		public and private information on the UAS.
	</li>
</ol>
</section>
<section numbered="true" toc="default"> <name>Currently selected IDs by ASTM</name>
<t>
	Now a little 'context' setting.  ASTM has already defined a set of 
	textual Remote IDs: 
</t>
<ol spacing="normal" type="%d">
	<li>
		Serial Number <xref target="CTA2063A" format="default"/>
	</li>
	<li>
		CAA Assigned ID <!-- need ref here -->
	</li>
	<li>
		UTM Assigned ID <xref target="RFC4122" format="default"/> <!-- ??? -->
	</li>
</ol>
<t>
	The work here MUST surpass these in terms of Trustworthiness.
</t>
</section>
<section numbered="true" toc="default"> <name>Options for Trustworthy IDs</name>
<t>
	The options found are:
</t>
<ol spacing="normal" type="1">
	<li>
		X.509 certs where something like the cert sequenceNumber is the 
		Remote ID.
	</li>
	<li>
		Naming Things with Hashes, Section 8.2 of <xref 
		target="RFC6920" format="default"/>
	</li>
	<li>                                      
		SSH keyID
	</li>
	<li>
		HIT (Host Identity Tag) <xref target="RFC7401" format="default"/>
	</li>
</ol>
<t>
	Option 1 is no better than what ASTM/FAA is considering for any of 
	the current proposed types.  Somehow, there will be a PKI and from 
	that knowledge of the UAS is gained.  This REQUIRES Internet Access 
	(think disaster or other non-Internet situations) and a GLOBAL PKI 
	(the UA flew from Canada to the US or UK to France post Brexit).
</t>
<t>
	Option 2 meets requirements 1 and 2, but needs to be augmented so 
	that the Hash provides context for 3.  Is it supported for IPsec 
	and/or QUIC for UAS/observer secure communications (NetworkID).
</t>
</section>
      <!-- end Options -->
</section>
    <!-- end alternatives -->
<section anchor="IANA" numbered="true" toc="default"> <name>IANA Considerations</name>
<t>
	It is likely that an IPv6 prefix will be needed for the HHIT (or 
	other identifier) space; this will be specified in other drafts.
</t>
</section>
<section numbered="true" toc="default"> <name>Security Considerations</name>
<t>
	UAS RID is all about safety and security, so content pertaining to 
	such is not limited to this section. UAS RID information must be 
	divided into 2 classes: that which, to achieve the purpose, must be 
	published openly in plaintext, for the benefit of any observer; and 
	that which must be protected (e.g. PII of pilots) but made 
	available to properly authorized parties (e.g. public safety 
	personnel who urgently need to contact pilots in emergencies). 
	Details of the protection mechanisms will be provided in other 
	drafts. Classifying the information will be addressed primarily in 
	external standards but also herein as needed.
</t>
</section>
<section numbered="true" toc="default"> <name>Acknowledgments</name>
<t>
	The work of the FAA's UAS Identification and Tracking (UAS ID) 
	Aviation Rulemaking Committee (ARC) is the foundation of later ASTM 
	and proposed IETF efforts. The work of ASTM F38.02 in balancing the 
	interests of diverse stakeholders is essential to the necessary 
	rapid and widespread deployment of UAS RID.
</t>
</section>
</middle>
<back>
<references> <name>References</name>
<references> <name>Normative References</name>
	<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
	<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7401.xml"/>
	<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8005.xml"/>
	<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
</references>
<references> <name>Informative References</name>
	<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6920.xml"/>
	<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.moskowitz-hip-hierarchical-hit.xml"/>
	<!--  <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.moskowitz-hip-hhit-registries.xml"/> -->
	<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.moskowitz-hip-new-crypto.xml"/>
	<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4122.xml"/>
	<reference anchor="CTA2063A" target="">
	<front>
		<title>Small Unmanned Aerial Systems Serial Numbers</title>
		<author>
			<organization>ANSI</organization>
		</author>
		<date month="09" year="2019"/>
	</front>
	</reference>
	<reference anchor="WK65041" target="">
	<front>
		<title>Standard Specification for Remote ID and Tracking</title>
		<author>
			<organization>ASTM</organization>
		</author>
		<date month="09" year="2019"/>
	</front>
	</reference>
</references>
</references>
</back>
</rfc>

--------------169D1B4F197A890B7408B449--


From nobody Wed Jan 29 08:07:00 2020
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 C5732120118 for <xml2rfc@ietfa.amsl.com>; Wed, 29 Jan 2020 08:06:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 0HZkfTf4rXdj for <xml2rfc@ietfa.amsl.com>; Wed, 29 Jan 2020 08:06:56 -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 6FBDA1200BA for <xml2rfc@ietf.org>; Wed, 29 Jan 2020 08:06:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id C89076216A; Wed, 29 Jan 2020 11:06:55 -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 hFbZBLRr05gN; Wed, 29 Jan 2020 11:06:50 -0500 (EST)
Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 78B4A62123; Wed, 29 Jan 2020 11:06:50 -0500 (EST)
To: Henrik Levkowetz <henrik@levkowetz.com>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>
References: <64044281-a1cb-87c8-f15d-62af751b6bb8@htt-consult.com> <9e3a3287-d2d0-8f57-a277-f0696a147597@levkowetz.com>
From: Robert Moskowitz <rgm@htt-consult.com>
Message-ID: <27f1c1de-29df-1bd6-eea1-cf00bb0c1248@htt-consult.com>
Date: Wed, 29 Jan 2020 11:06:49 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <9e3a3287-d2d0-8f57-a277-f0696a147597@levkowetz.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/OcD74OtqFfUlbEn_Mg0BCRYag2U>
Subject: Re: [xml2rfc] Boilerplate error on xml submission
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: Wed, 29 Jan 2020 16:06:59 -0000

Oh, the .txt was generated with the --v3 switch.

On 1/29/20 11:00 AM, Henrik Levkowetz wrote:
> Hi Bob,
>
> Could you send the .txt or .xml file that triggered this?
>
>
> Best regards,
>
> 	Henrik
>
>
> On 2020-01-29 16:48, Robert Moskowitz wrote:
>> Colleague is working on a draft from template I supplied.  It worked for
>> me earlier in the month.
>>
>> We are getting the following idnit:
>>
>>     Showing Errors (**), Flaws (~~), Warnings (==), and Comments (--).
>>     Errors MUST be fixed before draft submission.  Flaws SHOULD be fixed
>> before draft submission.
>>
>>     Checking boilerplate required by RFC 5378 and the IETF Trust (see
>>     https://trustee.ietf.org/license-info):
>> ----------------------------------------------------------------------------
>>
>>     ** The document seems to lack a License Notice according IETF Trust
>>        Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009
>>        Section 6.b -- however, there's a paragraph with a matching beginning.
>>        Boilerplate error?
>>
>>        IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(ii),
>> paragraph 3:
>>           This document is subject to BCP 78 and the IETF Trust's Legal
>> Provisions
>>           Relating to IETF Documents
>>           (https://trustee.ietf.org/license-info) in effect on the date of
>>           publication of this document.  Please review these documents
>>           carefully, as they describe your rights and restrictions with
>>           respect to this document.
>>
>>        ... text found in draft:
>>           This document is subject to BCP 78 and the IETF Trust's Legal
>> Provisions
>>           Relating to IETF Documents
>>           (https://trustee.ietf.org/license-info) in effect on the date of
>>           publication of this document.
>> .....................................^
>>
>>
>> I believe this is due to the following:
>>
>> <rfc xmlns:xi="http://www.w3.org/2001/XInclude"
>> docName="draft-card-tmrid-uas-01"
>>       category="std" ipr="trust200902" obsoletes="" updates=""
>> submissionType="IETF"
>>       xml:lang="en" tocInclude="true" symRefs="true" sortRefs="true"
>> version="3">
>>
>> Is there something newer to XInclude?  Or is the problem somewhere else?
>>
>> thanks
>>
>> _______________________________________________
>> xml2rfc mailing list
>> xml2rfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>


From nobody Wed Jan 29 08:29:21 2020
Return-Path: <henrik@levkowetz.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 8001912009C for <xml2rfc@ietfa.amsl.com>; Wed, 29 Jan 2020 08:29:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 ZZILgXVf0cN1 for <xml2rfc@ietfa.amsl.com>; Wed, 29 Jan 2020 08:29:16 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A1D9120088 for <xml2rfc@ietf.org>; Wed, 29 Jan 2020 08:29:16 -0800 (PST)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:57135 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1iwqD1-00078E-1b; Wed, 29 Jan 2020 08:29:15 -0800
To: Robert Moskowitz <rgm@htt-consult.com>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>
References: <64044281-a1cb-87c8-f15d-62af751b6bb8@htt-consult.com> <9e3a3287-d2d0-8f57-a277-f0696a147597@levkowetz.com> <bb193109-8d4a-5d91-9470-cb53eac63843@htt-consult.com>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <51970e6c-9f98-ccf7-b755-cb0823e17926@levkowetz.com>
Date: Wed, 29 Jan 2020 17:28:47 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <bb193109-8d4a-5d91-9470-cb53eac63843@htt-consult.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: xml2rfc@ietf.org, rgm@htt-consult.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/o_fdP3fBTpo2FDIbCKEqQ8vkdXI>
Subject: Re: [xml2rfc] Boilerplate error on xml submission
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: Wed, 29 Jan 2020 16:29:20 -0000

Hi Bob,

This is a flaw in the current idnits, caused by a page break after a
complete sentence in the boilerplate:

---------------------------------------------------------------------------

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.



Card, et al.              Expires 1 August 2020                 [Page 1]
^L
Internet-Draft                UAS Remote ID                 January 2020


   Please review these documents carefully, as they describe your rights

---------------------------------------------------------------------------

The remedy is silly:  Make the abstract one line shorter or longer.

This will be fixed when the rewrite of idnits in python is complete and
deployed.


Best regards,

	Henrik


On 2020-01-29 17:05, Robert Moskowitz wrote:
> Here is the xml.
> 
> 
> On 1/29/20 11:00 AM, Henrik Levkowetz wrote:
>> Hi Bob,
>>
>> Could you send the .txt or .xml file that triggered this?
>>
>>
>> Best regards,
>>
>> 	Henrik
>>
>>
>> On 2020-01-29 16:48, Robert Moskowitz wrote:
>>> Colleague is working on a draft from template I supplied.  It worked for
>>> me earlier in the month.
>>>
>>> We are getting the following idnit:
>>>
>>>     Showing Errors (**), Flaws (~~), Warnings (==), and Comments (--).
>>>     Errors MUST be fixed before draft submission.  Flaws SHOULD be fixed
>>> before draft submission.
>>>
>>>     Checking boilerplate required by RFC 5378 and the IETF Trust (see
>>>     https://trustee.ietf.org/license-info):
>>> ----------------------------------------------------------------------------
>>>
>>>     ** The document seems to lack a License Notice according IETF Trust
>>>        Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009
>>>        Section 6.b -- however, there's a paragraph with a matching beginning.
>>>        Boilerplate error?
>>>
>>>        IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(ii),
>>> paragraph 3:
>>>           This document is subject to BCP 78 and the IETF Trust's Legal
>>> Provisions
>>>           Relating to IETF Documents
>>>           (https://trustee.ietf.org/license-info) in effect on the date of
>>>           publication of this document.  Please review these documents
>>>           carefully, as they describe your rights and restrictions with
>>>           respect to this document.
>>>
>>>        ... text found in draft:
>>>           This document is subject to BCP 78 and the IETF Trust's Legal
>>> Provisions
>>>           Relating to IETF Documents
>>>           (https://trustee.ietf.org/license-info) in effect on the date of
>>>           publication of this document.
>>> .....................................^
>>>
>>>
>>> I believe this is due to the following:
>>>
>>> <rfc xmlns:xi="http://www.w3.org/2001/XInclude"
>>> docName="draft-card-tmrid-uas-01"
>>>       category="std" ipr="trust200902" obsoletes="" updates=""
>>> submissionType="IETF"
>>>       xml:lang="en" tocInclude="true" symRefs="true" sortRefs="true"
>>> version="3">
>>>
>>> Is there something newer to XInclude?  Or is the problem somewhere else?
>>>
>>> thanks
>>>
>>> _______________________________________________
>>> xml2rfc mailing list
>>> xml2rfc@ietf.org
>>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>>
> 


From nobody Fri Jan 31 03:41:46 2020
Return-Path: <henrik@levkowetz.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 ACB8412081D; Fri, 31 Jan 2020 03:41:39 -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 jvI-pO_Ip9zh; Fri, 31 Jan 2020 03:41:38 -0800 (PST)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5018A12081A; Fri, 31 Jan 2020 03:41:38 -0800 (PST)
Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1ixUg6-0007pw-2Z; Fri, 31 Jan 2020 03:41:38 -0800
To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
Message-Id: <E1ixUg6-0007pw-2Z@durif.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Fri, 31 Jan 2020 03:41:38 -0800
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Rcpt-To: rfc-markdown@ietf.org, xml2rfc-dev@ietf.org, xml2rfc@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on durif.tools.ietf.org); SAEximRunCond expanded to false
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/-KQDoS3THGL0na_0er8CLAGytHA>
Subject: [xml2rfc] New xml2rfc release: v2.39.0
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: Fri, 31 Jan 2020 11:41:40 -0000

Hi,

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

Release notes:

xml2rfc (2.39.0) ietf; urgency=medium


  * Provided a rendering for <xref> with reference targets which are part of 
    a <referencegroup> and don't have a reference tag.

  * Added a --pdf-help command-like option, and tweaked the order of some 
    command-line options in the --help output.

  * Added a new filter for pdf-gneration library warnings, to avoid it 
    appearing on every xml2rfc invocation.

  * Added a v2v3 converter for dates with non-numeric years.

  * Added an error for attempting to insert a missing XInclude namespace 
    prefix when 'xi' is already defined as something else.

  * Fixed a bug introduced with the refactoring in [3438].

 -- Henrik Levkowetz <henrik@levkowetz.com>  31 Jan 2020 10:03:13 +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 http://svn.tools.ietf.org/svn/tools/xml2rfc/tags/cli/2.39.0'

Regards,

	Henrik
	(via the mkrelease script)


From nobody Fri Jan 31 04:49:31 2020
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 6AF011200B3; Fri, 31 Jan 2020 04:49:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 (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 NlbDdULvuszN; Fri, 31 Jan 2020 04:49:18 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 E4F25120804; Fri, 31 Jan 2020 04:49:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1580474955; bh=cus10TVYjSaw2e+ICRJaVTkCFYvMZir8rSkQxYFQ7KA=; h=X-UI-Sender-Class:Subject:From:To:Cc:References:Date:In-Reply-To; b=OzW7R9ZJx9zhmA86JKr96Q1/goivKiWMN/i53yGngWdJi7ro++8WUX4Vtohx7vnis 8yZgOfOpbC7hQsuKjqVNVFwQlk26QEi/j+eUPa+xWNE0EIZsaSpdctd25nwpkiugt6 CFu3ciWkyR7wDyPF4GY6ILVF3KgxNEAEtqqHqiP8=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.1.81] ([217.91.35.233]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MmUHj-1jOHyl45B3-00iPja; Fri, 31 Jan 2020 13:49:15 +0100
From: Julian Reschke <julian.reschke@gmx.de>
To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
References: <E1itZ3Q-0003b8-Q5@durif.tools.ietf.org> <973bc456-19af-76e8-d8e5-ef506f587fe7@gmx.de>
Message-ID: <3725603a-fe71-adbc-4c66-8669e2bce292@gmx.de>
Date: Fri, 31 Jan 2020 13:49:10 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2
MIME-Version: 1.0
In-Reply-To: <973bc456-19af-76e8-d8e5-ef506f587fe7@gmx.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:tJx1qS5rahqCamZLq17SsWzS5IR4uoBaEsyUWjKScYjsKwDajRV fOly+wHbZHqHM2RS2vSi+OdensTinTRWL9v3iFGE49NIs+YaomR6gKigI1yhjYs5XYXSx1k KDjYWuYMHmz3PNBRqI55vNOpmV29x2dPl8eGQNONip027bKrnhu3P0AkAjhD1KgOx2CD8dU 4CFmc4qeOp+rsPmCyQB5w==
X-UI-Out-Filterresults: notjunk:1;V03:K0:kFTpbfBxuRM=:pcMtC1OOBf8vgeb5ZWDl/M ms8lLbRZ1wTe1VJjpL40gAIxxq+aneiVjuHWHjRZnLcJ+FtnxsP7Rp+Sj8XLNPAPA6yI+EIuP dvkKLC9V0iCq4a0mazPBIK45ijOYL5aCN/rO8Uiqi/4yztNQqFDSUd89oGSKI60h+IZpBgj7p cUBhH4QkwZ58W9YTFgOaWXtNZzS2FDeLVXN3AQTUDTl7mbTRZALOR8UmzVtBOQtLjX/FE8/Po U5mgpltXtvX1UhqaoplTTKYPKovKi1FkLR0ulO0ebMR7M9jv3nbMqzu4T1Vektp4NCl5u6AA/ 3Whsc/Ndabs1/+CYiSVDlo/+aWviL9i7dWWCCbxcdzasdiOlOW2bWUWA2e2Lxj+mU9Kv5R8z6 pYLsXKB5D+K2byk3QCHebNZOQQvdJ+S4w7oW98aXfrWqqvUXbVawvXwEvd4Vx+4n2nCRjOkQa MQZsKQWflZ8cLx0wxaG/2y84rkb7B3a3PkDc+YonsZVLf+4rVa7IISVxs3JV+J3nywBk2yaLS FHKvL3UBi/akZs5uaXZMTk6I0oSwHVeiqqjmZuFS7F30ctkuRoZo7EFhH82IdTr4PX5jZ35IK qeMCiLclBvuyWQL1GYD8INJyrdEM2wS8mqH/+JZLA0YmIP1WwkamPQgn0JzEPYe+afC3rAqRd wjR+R7Y/fGoR9Su7ZvyUSU9e6ATPZKtW36ImMSaiCuU3HH+KArohprvU2RggdJRmfZlv5rWNz EqovCFv8khf4BRhH1dvbXcEaNbWlatg4RyBWnrkEDE20TLPBdzVpJUWs+t3+ybdqv61B8ySgq EyYG2n6qxQ49x+YiwEljstSpMaZMZmEATEZfsrKhcICLPluuGX/wLhffodiXnuSdE6rqp79cR J5QXaf3QVpfDDhmt5cRWx8okJiNd4/9H5rm5E3gTBUU/mGAuK0Piq2UwQJeezpWzIPTEuhzuM fRexJOhAgmY3QMQLSNyudyPqrVV1nCnnVJD9p7dm+IkDmAzfB50Mg+hlpSJ+9GUawj9MCSIWf Qy8ZUmd6BUaP3ASMD1t00YySf4AMJS+OFqqiTsS8pqVhBh/osq4jl35bgTUFDBuRQtgXnJO5F xgeEbtIpGqKO19d9V2fh5ygEvvmut0uQvKmf4DqaPD4ATtlZu+zVvjENaQdNzqR+vAjLiBXop JIUKZq+YBtBr64jycnGYNfMk87EMwxGHIi1/eGV0PI6MQ9ksvb9RBMBzSi0KxZ6xhMJ7l6hH3 xHH4ir9ABzlEhx5+9
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/zF1H8hmBMtVlPPcNBepfsHssiEA>
Subject: Re: [xml2rfc] [xml2rfc-dev] New xml2rfc release: v2.38.1
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: Fri, 31 Jan 2020 12:49:21 -0000

On 20.01.2020 19:33, Julian Reschke wrote:
> On 20.01.2020 16:33, Henrik Levkowetz wrote:
>>
>> Hi,
>>
>> This is an automatic notification about a new xml2rfc release,
>> v2.38.1, generated when running the mkrelease script.
>>
>> Release notes:
>>
>> xml2rfc (2.38.1) ietf; urgency=3Dmedium
>>
>> =C2=A0=C2=A0 * Added a preptool check for numbered sections occurring a=
fter or
>> under
>> =C2=A0=C2=A0=C2=A0=C2=A0 unnumbered sections, and changed the code for =
Reference sections to
>> =C2=A0=C2=A0=C2=A0=C2=A0 not emit section numbers if the previous secti=
on was unnumbered.
>> =C2=A0=C2=A0=C2=A0=C2=A0 Fixes issue #433
>>
>> =C2=A0=C2=A0 * Refactored the code for reference anchor to display stri=
ng mapping,
>> =C2=A0=C2=A0=C2=A0=C2=A0 locating it in a base class method.=C2=A0 Upda=
ted it to honour the
>> symRefs
>> =C2=A0=C2=A0=C2=A0=C2=A0 setting.=C2=A0 Fixes issue #476.
>> ...
>
> The above may have broken <xref>s to children of <reference-group>. See
> <https://trac.tools.ietf.org/tools/xml2rfc/trac/attachment/ticket/487/>.
> ...

I note that I didn't get a reply, and the bug that I reported is still
labeled "new".

In 2.39 the behavior indeed changed again; the processor now doesn't
abort anymore, but the text inserted for reference group members lacks
the brackets ("[....]").

Best regards, Julian

