From nobody Thu Aug 1 18:34:31 2019 Return-Path: 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 4B183120089 for ; Thu, 1 Aug 2019 18:34:30 -0700 (PDT) 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 ksuFiB_KJby3 for ; Thu, 1 Aug 2019 18:34:27 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 697F512001A for ; Thu, 1 Aug 2019 18:34:27 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id BB22060D1B; Thu, 1 Aug 2019 21:34:25 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ahl5mnDiTlJm; Thu, 1 Aug 2019 21:34:18 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 5D74660964; Thu, 1 Aug 2019 21:34:18 -0400 (EDT) To: "Andrew G. Malis" Cc: "xml2rfc@ietf.org" , Carsten Bormann References: <08a2115c-54a4-b049-02ea-340f8e7dce20@htt-consult.com> From: Robert Moskowitz Message-ID: <3f9c98f8-5f9e-f4cb-9226-77cf57280b40@htt-consult.com> Date: Thu, 1 Aug 2019 21:34:11 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------08ACC0D90228B968597BE344" Content-Language: en-US Archived-At: Subject: Re: [xml2rfc] xml to markdown? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Aug 2019 01:34:30 -0000 This is a multi-part message in MIME format. --------------08ACC0D90228B968597BE344 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Report on my first real experience reading a kramdown draft (what is the difference between kramdown and markdown?). The .md file of my .xml is cryptic.  There is a lot of assumed knowledge.  Stuff you have to remember to format right. Well xml has to be formatted right, but it is a rigorous structure that your editor can pretty much tell you have it right, even before you run xml2rfc. Perhaps there is a plugin for Geany, but with xml, it is easy to close the sections I am not working on and be able to focus on the work at hand.  My time writing and moving around in the draft is thus more focused and better spent. I suppose things grow on us.  I will continue to look at this new stuff, but for now will stay with xml. On 7/31/19 2:33 PM, Andrew G. Malis wrote: > Bob, > > While I don't have such a tool (although Carsten may), I do have a > draft that uses a lot of kramdown features, please feel free to use it > as a template. I use the tools at > https://xml2rfc.tools.ietf.org/experimental.html for converting > kramdown to text. In the top dialog box, "Convert Your XML Source", > choose kramdown rather than xml2rfc as the input type. I go straight > to text rather than generating xml as an intermediate step, although > that option is available further down on that same page. > > I've attached my draft source and output so that you can compare them > side by side. > > Cheers, > Andy > > > On Wed, Jul 31, 2019 at 2:10 PM Robert Moskowitz > wrote: > > I am having to work with people that prefer markdown for creating > their > IDs.  They go the md -> xml -> ID route. > > I have yet to figure out how to read markdown drafts let alone > work with > that format. > > Is there a tool I can use to convert my xml to markdown so that I can > see what I have been doing looks like in markdown and see if all > the xml > features I use (like hangtext in defs) are mapped to markdown? > > thanks > > _______________________________________________ > xml2rfc mailing list > xml2rfc@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc > --------------08ACC0D90228B968597BE344 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Report on my first real experience reading a kramdown draft (what is the difference between kramdown and markdown?).

The .md file of my .xml is cryptic.  There is a lot of assumed knowledge.  Stuff you have to remember to format right.

Well xml has to be formatted right, but it is a rigorous structure that your editor can pretty much tell you have it right, even before you run xml2rfc.

Perhaps there is a plugin for Geany, but with xml, it is easy to close the sections I am not working on and be able to focus on the work at hand.  My time writing and moving around in the draft is thus more focused and better spent.

I suppose things grow on us.  I will continue to look at this new stuff, but for now will stay with xml.

On 7/31/19 2:33 PM, Andrew G. Malis wrote:
Bob,

While I don't have such a tool (although Carsten may), I do have a draft that uses a lot of kramdown features, please feel free to use it as a template. I use the tools at https://xml2rfc.tools.ietf.org/experimental.html for converting kramdown to text. In the top dialog box, "Convert Your XML Source", choose kramdown rather than xml2rfc as the input type. I go straight to text rather than generating xml as an intermediate step, although that option is available further down on that same page.

I've attached my draft source and output so that you can compare them side by side.

Cheers,
Andy


On Wed, Jul 31, 2019 at 2:10 PM Robert Moskowitz <rgm@htt-consult.com> wrote:
I am having to work with people that prefer markdown for creating their
IDs.  They go the md -> xml -> ID route.

I have yet to figure out how to read markdown drafts let alone work with
that format.

Is there a tool I can use to convert my xml to markdown so that I can
see what I have been doing looks like in markdown and see if all the xml
features I use (like hangtext in defs) are mapped to markdown?

thanks

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

--------------08ACC0D90228B968597BE344-- From nobody Thu Aug 1 18:49:40 2019 Return-Path: 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 ACCA812006F for ; Thu, 1 Aug 2019 18:49:39 -0700 (PDT) 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 5CrD5czjeUKU for ; Thu, 1 Aug 2019 18:49:38 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68B0712001A for ; Thu, 1 Aug 2019 18:49:38 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 56B6760D1C for ; Thu, 1 Aug 2019 21:49:37 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id yKjmyr42jPYi for ; Thu, 1 Aug 2019 21:49:32 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id B15C060964 for ; Thu, 1 Aug 2019 21:49:29 -0400 (EDT) To: "xml2rfc@ietf.org" From: Robert Moskowitz Message-ID: <20a68c06-a55b-9f4a-0a30-eca35000c5fc@htt-consult.com> Date: Thu, 1 Aug 2019 21:49:18 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: [xml2rfc] Problems with tools pointing to BCP14/ X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Aug 2019 01:49:40 -0000 Carsten pointed out that my BCP14 boilerplate in my xml was old. And I see it was.  So I went to look up BCP14: https://tools.ietf.org/html/bcp14 And it points to RFC 2119.  Shouldn't that now resolve to 8174? Who maintains the bcp listing? From nobody Thu Aug 1 21:44:40 2019 Return-Path: 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 318D11200A1 for ; Thu, 1 Aug 2019 21:44:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=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 VKgtxvVbqQHY for ; Thu, 1 Aug 2019 21:44:37 -0700 (PDT) Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (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 15CEB120074 for ; Thu, 1 Aug 2019 21:44:37 -0700 (PDT) Received: by mail-qt1-x82b.google.com with SMTP id 44so41633027qtg.11 for ; Thu, 01 Aug 2019 21:44:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=i9ziWZh9gQzUb/PEzWjDj0+/PgVs92LTO3NjWsvoI0Q=; b=fL0DdbD5ka1hU9ykITohK5n9MpYh0AaAELlIOryBCBcQdab+NghUBSWbVrcftOOCy1 OBPNyI7kswMyF4m5LgVJSc5aQChOg+zRCaAkUp5gjqFrdrja2FA7jahVARshL8fpMztp O0xQUn76v/Q0l72+UspcOjNs8DCLmN02NrnLb8GkLFWkAUTqi13VVrZX7bMW1pn5p8+M WxzWuICh8h2zCbXxyB9nVAl4WEVbJ8nMMDX8VuQf9eVuKXXN4NEsBw8kcflrSxKe8vpZ 2JVBg+EymOW38Vk/EQnXp9SWc62RMaZuc/dJ2T4/ggEN9/Y2lkAmuSMvNcKW2v5BsQ1t TbJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=i9ziWZh9gQzUb/PEzWjDj0+/PgVs92LTO3NjWsvoI0Q=; b=KlYQPfUc1ZHQ7txs0cCRVqx2cBOlcYzcscI/4IRgb3gXnIKtd+EOw0MP6Ng0w0WqHn iFVqA/FuD4qTO4ZBD+n8br1JAPIdnkr+aO8PjvuuljaQ4EAtsF6mALXf8BHJnLFAX9sh eZchyLeS/ilSBJI5+sLKEifuhKkYArvg2n7f02inkVQCWJ806KTHHYOP5IKiNJpbYwt8 GjIPGhyNLxhYaJnE2LsVPlyxQ1LuQnxiSFI/v2D3HMyKuJx5Sb2XWNmiOjCNtKGU8+zD XcgTNOtr9hzbUg/+XQ3OL51Fbi/ugUxY3meB5Z2nVVc5fSnA7DF/7w9fOyhYgw88ClVP 5jOA== X-Gm-Message-State: APjAAAVPYWZPclLVqL3VHMim1OScfD//CiexP0t5oLkPSQGcST8K5JdB CYSKtF00U9M/GVSXhXhgSm2UfMBXI9+7bBnzACJAzsibnwk= X-Google-Smtp-Source: APXvYqzYm7d+DLAokxdPvYuYJAiNORNWODmek8uD+MM3VLRbMUtzTHrEV1tbfCpqHVIFpPL9KC9RfYPHTg274yRLhFw= X-Received: by 2002:aed:2ac2:: with SMTP id t60mr11404633qtd.173.1564721076049; Thu, 01 Aug 2019 21:44:36 -0700 (PDT) MIME-Version: 1.0 References: <20a68c06-a55b-9f4a-0a30-eca35000c5fc@htt-consult.com> In-Reply-To: <20a68c06-a55b-9f4a-0a30-eca35000c5fc@htt-consult.com> From: "Andrew G. Malis" Date: Fri, 2 Aug 2019 00:44:25 -0400 Message-ID: To: Robert Moskowitz Cc: "xml2rfc@ietf.org" Content-Type: multipart/alternative; boundary="000000000000e91b3e058f1b0397" Archived-At: Subject: Re: [xml2rfc] Problems with tools pointing to BCP14/ X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Aug 2019 04:44:39 -0000 --000000000000e91b3e058f1b0397 Content-Type: text/plain; charset="UTF-8" Bob, That URL actually points to both RFCs. It says at the top "[Note that this file is a concatenation of more than one RFC.]", and indeed if you scroll down, you'll see them both. Perhaps not the most user-friendly way to do it, but they are both there. BTW, the current BCP14 text is: 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 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. Cheers, Andy On Thu, Aug 1, 2019 at 9:49 PM Robert Moskowitz wrote: > Carsten pointed out that my BCP14 boilerplate in my xml was old. And I > see it was. So I went to look up BCP14: > > https://tools.ietf.org/html/bcp14 > > And it points to RFC 2119. Shouldn't that now resolve to 8174? > > Who maintains the bcp listing? > > > _______________________________________________ > xml2rfc mailing list > xml2rfc@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc > --000000000000e91b3e058f1b0397 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Bob,

That URL actually points to both R= FCs. It says at the top "[Note that this file is a concatenation of more than one RFC.]"= ;, and indeed if you scroll down, you'll see them both. Perhaps not the= most user-friendly way to do it, but they are both there.

BTW, the current BCP1= 4 text is:

=C2=A0 =C2=A0The key words "MUST", &q= uot;MUST NOT", "REQUIRED", "SHALL", "SHALL NO= T",
=C2=A0 =C2=A0"SHOULD", "SHOULD NOT", "= RECOMMENDED", "NOT RECOMMENDED", "MAY", and
=C2= =A0 =C2=A0"OPTIONAL" in this document are to be interpreted as de= scribed in BCP
=C2=A0 =C2=A014 [RFC2119] [RFC8174] when, and only when, = they appear in all
=C2=A0 =C2=A0capitals, as shown here.
<= br>
Cheers,
Andy


On Thu, Aug 1, 201= 9 at 9:49 PM Robert Moskowitz <rg= m@htt-consult.com> wrote:
Carsten pointed out that my BCP14 boilerplate in my xml wa= s old. And I
see it was.=C2=A0 So I went to look up BCP14:

https://tools.ietf.org/html/bcp14

And it points to RFC 2119.=C2=A0 Shouldn't that now resolve to 8174?
Who maintains the bcp listing?


_______________________________________________
xml2rfc mailing list
xml2rfc@ietf.org<= br> https://www.ietf.org/mailman/listinfo/xml2rfc
--000000000000e91b3e058f1b0397-- From nobody Thu Aug 1 23:17:46 2019 Return-Path: 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 7EB1C12003E for ; Thu, 1 Aug 2019 23:17:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.198 X-Spam-Level: X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 ghJgV6yliBLN for ; Thu, 1 Aug 2019 23:17:42 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 708FA12002E for ; Thu, 1 Aug 2019 23:17:42 -0700 (PDT) Received: from [192.168.217.110] (p548DCCB9.dip0.t-ipconnect.de [84.141.204.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 460H5J480sz10c2; Fri, 2 Aug 2019 08:17:40 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Carsten Bormann In-Reply-To: <3f9c98f8-5f9e-f4cb-9226-77cf57280b40@htt-consult.com> Date: Fri, 2 Aug 2019 08:17:40 +0200 Cc: "Andrew G. Malis" , "xml2rfc@ietf.org" X-Mao-Original-Outgoing-Id: 586419456.75985-fdef382c278b492111f317a7614a06f6 Content-Transfer-Encoding: quoted-printable Message-Id: References: <08a2115c-54a4-b049-02ea-340f8e7dce20@htt-consult.com> <3f9c98f8-5f9e-f4cb-9226-77cf57280b40@htt-consult.com> To: Robert Moskowitz X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [xml2rfc] xml to markdown? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Aug 2019 06:17:44 -0000 On Aug 2, 2019, at 03:34, Robert Moskowitz wrote: >=20 > Report on my first real experience reading a kramdown draft (what is = the difference between kramdown and markdown?). kramdown is an implementation of a markdown processor. kramdown-rfc2629 (or kramdown-rfc for short) is a tool that uses = kramdown as its markdown implementation and generates RFCXML. > The .md file of my .xml is cryptic. There is a lot of assumed = knowledge. Stuff you have to remember to format right. Right, there is the markdown syntax (which many of us use daily anyway), = and then there is some syntax to support referencing and other = RFC-specific things. Syntax that gets in the way much less than XML = does. > Well xml has to be formatted right, but it is a rigorous structure = that your editor can pretty much tell you have it right, even before you = run xml2rfc. Markdown syntax is supported by many editors. But there is little need = for that, as markdown syntax is intuitive (*). (*) intuitive is another word for familiar. If you don=E2=80=99t = encounter markdown in your daily life a lot, there is some learning = involved for it to become familiar=E2=80=A6 More importantly, markdown lends itself to a slightly different style of = working than XML: Just write. You can always worry about syntax later. XML-supporting editors tend to provide this straightjacket that you have = to work in, so you are concerned with the syntax before you actually can = lay down text. (And then, there are things like PIs where they don=E2=80=99= t help at all.) (Interestingly, I=E2=80=99m a zero tolerance guy when it comes to the = actual writing, but I don=E2=80=99t care about tool syntax very much = while doing so =E2=80=94 the focus is on the text.) > Perhaps there is a plugin for Geany, Geany plugins don=E2=80=99t seem to be able to support code folding. > but with xml, it is easy to close the sections I am not working on and = be able to focus on the work at hand. =20 It seems the code folding built in to Geany doesn=E2=80=99t support = markdown (tried with 1.33). I don=E2=80=99t run surveys on things like this but it seems most = editors these days do support markdown, including code folding where = that is a standard feature of the editor (e.g., use the TAB key in emacs = markdown-mode). Too bad that Geany doesn=E2=80=99t. > My time writing and moving around in the draft is thus more focused = and better spent. An editor that supports code folding is indeed a useful tool to have. > I suppose things grow on us. I will continue to look at this new = stuff, but for now will stay with xml. So no need to convert the other XML file? Gr=C3=BC=C3=9Fe, Carsten From nobody Fri Aug 2 09:12:29 2019 Return-Path: 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 31BB61201DE for ; Fri, 2 Aug 2019 09:12:28 -0700 (PDT) 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 j-lQ6mI9fmnT for ; Fri, 2 Aug 2019 09:12:25 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B2511201CB for ; Fri, 2 Aug 2019 09:12:25 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 714136096F; Fri, 2 Aug 2019 12:12:23 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id VIbROc0TqLH3; Fri, 2 Aug 2019 12:12:17 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id D79F960964; Fri, 2 Aug 2019 12:12:14 -0400 (EDT) To: "Andrew G. Malis" Cc: "xml2rfc@ietf.org" References: <20a68c06-a55b-9f4a-0a30-eca35000c5fc@htt-consult.com> From: Robert Moskowitz Message-ID: <8d6c6a11-6406-eb92-1bf9-b85ef39706f4@htt-consult.com> Date: Fri, 2 Aug 2019 12:12:10 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------D7E49345394CBCBA87D6CCF8" Content-Language: en-US Archived-At: Subject: Re: [xml2rfc] Problems with tools pointing to BCP14/ X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Aug 2019 16:12:28 -0000 This is a multi-part message in MIME format. --------------D7E49345394CBCBA87D6CCF8 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit On 8/2/19 12:44 AM, Andrew G. Malis wrote: > Bob, > > That URL actually points to both RFCs. It says at the top "[Note that > this file is a concatenation of more than one RFC.]", and indeed if > you scroll down, you'll see them both. Perhaps not the most > user-friendly way to do it, but they are both there. Dah.  I still think the RFCs should be in reverse order in the BCP. > > BTW, the current BCP14 text is: > >    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 [RFC2119] [RFC8174] when, and only when, they appear in all >    capitals, as shown here. Got that now. thanks > > Cheers, > Andy > > > On Thu, Aug 1, 2019 at 9:49 PM Robert Moskowitz > wrote: > > Carsten pointed out that my BCP14 boilerplate in my xml was old. > And I > see it was.  So I went to look up BCP14: > > https://tools.ietf.org/html/bcp14 > > And it points to RFC 2119.  Shouldn't that now resolve to 8174? > > Who maintains the bcp listing? > > > _______________________________________________ > xml2rfc mailing list > xml2rfc@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc > --------------D7E49345394CBCBA87D6CCF8 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

On 8/2/19 12:44 AM, Andrew G. Malis wrote:
Bob,

That URL actually points to both RFCs. It says at the top "[Note that this file is a concatenation of more than one RFC.]", and indeed if you scroll down, you'll see them both. Perhaps not the most user-friendly way to do it, but they are both there.

Dah.  I still think the RFCs should be in reverse order in the BCP.


BTW, the current BCP14 text is:

   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 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Got that now.

thanks


Cheers,
Andy


On Thu, Aug 1, 2019 at 9:49 PM Robert Moskowitz <rgm@htt-consult.com> wrote:
Carsten pointed out that my BCP14 boilerplate in my xml was old. And I
see it was.  So I went to look up BCP14:

https://tools.ietf.org/html/bcp14

And it points to RFC 2119.  Shouldn't that now resolve to 8174?

Who maintains the bcp listing?


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

--------------D7E49345394CBCBA87D6CCF8-- From nobody Fri Aug 2 09:23:55 2019 Return-Path: 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 340BE12020A for ; Fri, 2 Aug 2019 09:23:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.198 X-Spam-Level: X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 zSBWI7s6YFgl for ; Fri, 2 Aug 2019 09:23:52 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6935312016E for ; Fri, 2 Aug 2019 09:23:52 -0700 (PDT) Received: from [192.168.217.110] (p548DCCB9.dip0.t-ipconnect.de [84.141.204.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 460XXk4WLtzydD; Fri, 2 Aug 2019 18:23:50 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Carsten Bormann In-Reply-To: <8d6c6a11-6406-eb92-1bf9-b85ef39706f4@htt-consult.com> Date: Fri, 2 Aug 2019 18:23:50 +0200 Cc: "Andrew G. Malis" , "xml2rfc@ietf.org" X-Mao-Original-Outgoing-Id: 586455825.8651021-18c3f11041e3b663b4f0779100a1b0b2 Content-Transfer-Encoding: quoted-printable Message-Id: <451982CF-FF82-47B3-973B-E6F0B37F577C@tzi.org> References: <20a68c06-a55b-9f4a-0a30-eca35000c5fc@htt-consult.com> <8d6c6a11-6406-eb92-1bf9-b85ef39706f4@htt-consult.com> To: Robert Moskowitz X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [xml2rfc] Problems with tools pointing to BCP14/ X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Aug 2019 16:23:54 -0000 On Aug 2, 2019, at 18:12, Robert Moskowitz wrote: >=20 > Dah. I still think the RFCs should be in reverse order in the BCP. Don=E2=80=99t know about that, but a TOC in the head box with links to = the pieces would be great. Gr=C3=BC=C3=9Fe, Carsten From nobody Fri Aug 2 09:31:23 2019 Return-Path: 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 4468A12068A for ; Fri, 2 Aug 2019 09:31:22 -0700 (PDT) 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 kXsQAnc_Yift for ; Fri, 2 Aug 2019 09:31:19 -0700 (PDT) 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 3715A120687 for ; Fri, 2 Aug 2019 09:31:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1564763474; bh=7CBOGJRIXeWgQUnLJgG6KzYQaRv8kA5JxEGTV/0DBS0=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=es5Aen4wAvb7CHfqam38LZn1CgLBslaSE7ujQdeLKvrnwGD9OuWErI1OYmrUeRzSU uhY4NK3FOhxg5E0bUkwEnGF9EAeSwJ2krH4fj42vLYruDQISYqs3tMN0FF7Of7w9qk /eoZhI8sgl1T00zhXjEYYuiiaOW27KPkpSnGT9uM= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [10.10.160.139] ([208.131.168.244]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MmUHj-1ibxhY3YsT-00iQA4 for ; Fri, 02 Aug 2019 18:31:14 +0200 To: xml2rfc@ietf.org References: <20a68c06-a55b-9f4a-0a30-eca35000c5fc@htt-consult.com> <8d6c6a11-6406-eb92-1bf9-b85ef39706f4@htt-consult.com> <451982CF-FF82-47B3-973B-E6F0B37F577C@tzi.org> From: Julian Reschke Message-ID: <81e76802-cdb6-36c5-d082-e2b84b44acce@gmx.de> Date: Fri, 2 Aug 2019 18:31:09 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <451982CF-FF82-47B3-973B-E6F0B37F577C@tzi.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:AEn2W5b7ltHJaOi73Aq3jhs5uxaOcmVB97E07Ce80duOkGyJ0Nb VcGzHAsTKWt43Kg/BRzV07Pn8tuQOPoZjFyFvEYetrWNlR9DB7VVX43EqfeWi6v3RqMAVoJ Rzdr3OJafe93fEq3+fsWgk4NIneRI5ki9El+6fGLpeZRBOpMeU1cqH4LWTHt2vlW4FukVmk BwQQlf11H/VJJKj+IC41Q== X-UI-Out-Filterresults: notjunk:1;V03:K0:cTnfG22WtPY=:OGYUVZvodSU0ONRyX8pr23 oj/2SqAwbaukyf+9iZUjz7Xi7SSjOY62+CwyQLFsnN4ySRpS6VYL1xwdkfZftv2D+O3YzE2zn tF/F91iArpFCpv6zUxtYiX8NHvjUhTZwnKL9MtaJs81j8KIOciHUbM+B5t9dGKxxDDR+7uUGg 7styB/QXcXSWWPfTke8o8PBI9chAELuOqEjadW6wbYR4vTgXPx2UTV1iSiBQhviAMfHyy8T/1 oM+waGsB1gfO3D26eiK3wJ0GYGZ6HotFR+29eXZ1ZcK/cmmftDE9LPs0ADlnWMOJKtjxXD2T+ NODIZL0iLF1q8hO9TjOldhCu7MBDbNmjptZACeD4mUmwMpB43iyQEOQVxWscJvSRGvY+Y4P4+ F7KixsrmZTIsMcVQFyDtzpzatrnHaFb1RqZRrmHlpv7mJnkr46dnXjyORjsgWnZImcm0zBLln u5zc9f8+GS9EiBaLp5fi3FvoICkZ4Yh3twZwvHkvmlWgRCJL/NpFWTHGPTkncNLa712Sm/l2i xKLvZ0Gjsiq2BRg6gWOkgk+MpC6BaKroB/Fbn9obDwSwydhqieSdreRxMfKBaGhMDsDUEdY85 UELWCpkOVu+pKFWkbai4N1JFgaFQuB3nhesVXUr8sv+VbuvI8fuhuUoSi6UU+IIjaT5MKmc6f +46ThnlA3TUr4X5i0QUQflCQZhFrA6aD6RfOG7oMB0eNr6ldgaGI0itnjW6NwhwVadQe+vH43 RtIRkPxUelz/IWp7PYy6UlFDN/LPVAsfcwX6uwdpcX0bE1LNoEWYIr8JYHa9Dsy1vwjMPey5m /EAz0wj+fg9mKAboT0XU0lunWBaBbnM0DO+E+3aCYUHatws+zJgbiEtpQSwK/w7vS/N6KYEix gCuTKjMlt8PoDAnVaPf1ybnpvbkdoqaL+BmnP0ki8ZL5NqSNJirVDzL5sOzfiaRGQ7eQZO5h2 +JUTQcRYol0EYZgVtVzV8S/BmZpfiXe8hwwWoNT/lNDbdBY2rc89jwGxS/hSIsW38z9eMANIr w0TOFaX13Xauw2Dyeg2gVRDp1iRacwhfdLjf8wFHCCIvnaabFAbCfdTELbKXtmPLPo1CVXZjq vuLadAQHw43szd0rKtgTBoILVo2NKs0qyjxOJ3l5ha3D+05MSbh01t1w4qe3YS8EF0BDNf5cW oXRs4= Archived-At: Subject: Re: [xml2rfc] Problems with tools pointing to BCP14/ X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Aug 2019 16:31:22 -0000 Am 02.08.2019 um 18:23 schrieb Carsten Bormann: > On Aug 2, 2019, at 18:12, Robert Moskowitz wrote: >> >> Dah. I still think the RFCs should be in reverse order in the BCP. > > Don=E2=80=99t know about that, but a TOC in the head box with links to t= he pieces would be great. ...an we should have a plan how this will work with the v3 HTML output (there are problems to solve, such as overall doc structure and anchor handling). Best regards, Julian From nobody Fri Aug 2 09:51:51 2019 Return-Path: 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 990BD120694 for ; Fri, 2 Aug 2019 09:51:50 -0700 (PDT) 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 cpCUDI6R0ndQ for ; Fri, 2 Aug 2019 09:51:48 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF89C12068B for ; Fri, 2 Aug 2019 09:51:48 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 6E46D6096F; Fri, 2 Aug 2019 12:51:47 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 2qobHE+64PQs; Fri, 2 Aug 2019 12:51:41 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id C0E2060964; Fri, 2 Aug 2019 12:51:39 -0400 (EDT) To: Carsten Bormann Cc: "Andrew G. Malis" , "xml2rfc@ietf.org" References: <08a2115c-54a4-b049-02ea-340f8e7dce20@htt-consult.com> <3f9c98f8-5f9e-f4cb-9226-77cf57280b40@htt-consult.com> From: Robert Moskowitz Message-ID: <3c3659b1-1120-82f8-a099-9a44333d8349@htt-consult.com> Date: Fri, 2 Aug 2019 12:51:31 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [xml2rfc] xml to markdown? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Aug 2019 16:51:51 -0000 On 8/2/19 2:17 AM, Carsten Bormann wrote: > On Aug 2, 2019, at 03:34, Robert Moskowitz wrote: >> Report on my first real experience reading a kramdown draft (what is the difference between kramdown and markdown?). > kramdown is an implementation of a markdown processor. > kramdown-rfc2629 (or kramdown-rfc for short) is a tool that uses kramdown as its markdown implementation and generates RFCXML. Only kramdown rpm is rubygem-kramdown.  I doubt if that will help me. > >> The .md file of my .xml is cryptic. There is a lot of assumed knowledge. Stuff you have to remember to format right. > Right, there is the markdown syntax (which many of us use daily anyway), and then there is some syntax to support referencing and other RFC-specific things. Syntax that gets in the way much less than XML does. Is there a manual for the syntax and special content like how the address structure works and things like the BCP14 boilerplate? To me, the xml syntax helps me visualize the data structure of the document.  But then I am dyslexic. >> Well xml has to be formatted right, but it is a rigorous structure that your editor can pretty much tell you have it right, even before you run xml2rfc. > Markdown syntax is supported by many editors. But there is little need for that, as markdown syntax is intuitive (*). > > (*) intuitive is another word for familiar. If you don’t encounter markdown in your daily life a lot, there is some learning involved for it to become familiar… > > More importantly, markdown lends itself to a slightly different style of working than XML: That last point is putting it mildly.  I have NO other encounters with markdown in my daily life let alone monthly life!  Whereas xml is like html and I do hand coding of my web pages (see www.htt-consult.com, particularly the 'new' stuff). And there is nothing intuitive about markdown.  It is all rout learning.  IMHO. > Just write. You can always worry about syntax later. > > XML-supporting editors tend to provide this straightjacket that you have to work in, so you are concerned with the syntax before you actually can lay down text. (And then, there are things like PIs where they don’t help at all.) I find it easy.  Create a section with anchor, make a text block, and start writing.    And much of that is copy and paste. What is PIs? > (Interestingly, I’m a zero tolerance guy when it comes to the actual writing, but I don’t care about tool syntax very much while doing so — the focus is on the text.) The focus is not just the text but the flow of the document.  As I write, I want to work at seeing that one part flows into another. > >> Perhaps there is a plugin for Geany, > Geany plugins don’t seem to be able to support code folding. I installed the geany-markdown plugin.  All it seems to do is colorize some command text and does not get all that kramdown uses. And no 'folding' (I assume this is the term for collapsing a block of text) >> but with xml, it is easy to close the sections I am not working on and be able to focus on the work at hand. > It seems the code folding built in to Geany doesn’t support markdown (tried with 1.33). And the markdown pluging does not help. > I don’t run surveys on things like this but it seems most editors these days do support markdown, including code folding where that is a standard feature of the editor (e.g., use the TAB key in emacs markdown-mode). Too bad that Geany doesn’t. Can you provide names of a couple?  I will also ask on the  Fedora user list. > >> My time writing and moving around in the draft is thus more focused and better spent. > An editor that supports code folding is indeed a useful tool to have. > >> I suppose things grow on us. I will continue to look at this new stuff, but for now will stay with xml. > So no need to convert the other XML file? I did send you a 2nd one last night. From nobody Fri Aug 2 11:01:08 2019 Return-Path: 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 4D77C120792 for ; Fri, 2 Aug 2019 11:01:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.198 X-Spam-Level: X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 FAVaWVJNztV1 for ; Fri, 2 Aug 2019 11:01:04 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18F22120791 for ; Fri, 2 Aug 2019 11:01:04 -0700 (PDT) Received: from [192.168.217.110] (p548DCCB9.dip0.t-ipconnect.de [84.141.204.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 460Zht3PLSzyQp; Fri, 2 Aug 2019 20:01:02 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Carsten Bormann In-Reply-To: <3c3659b1-1120-82f8-a099-9a44333d8349@htt-consult.com> Date: Fri, 2 Aug 2019 20:01:01 +0200 Cc: "Andrew G. Malis" , "xml2rfc@ietf.org" X-Mao-Original-Outgoing-Id: 586461659.995509-7ed97798ec80afb1824b5e7c5e262225 Content-Transfer-Encoding: quoted-printable Message-Id: References: <08a2115c-54a4-b049-02ea-340f8e7dce20@htt-consult.com> <3f9c98f8-5f9e-f4cb-9226-77cf57280b40@htt-consult.com> <3c3659b1-1120-82f8-a099-9a44333d8349@htt-consult.com> To: Robert Moskowitz X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [xml2rfc] xml to markdown? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Aug 2019 18:01:06 -0000 Hi Bob, > On Aug 2, 2019, at 18:51, Robert Moskowitz = wrote: >=20 > Only kramdown rpm is rubygem-kramdown. I doubt if that will help me. The recommended way to install kramdown-rfc2629 is gem install kramdown-rfc2629 (Some platforms need a sudo here; you=E2=80=99ll notice if it doesn=E2=80=99= t work without.) Of course, there is also the web service, but given that the tool is so = easy to install, I would recommend trying that first. (A little more work for Windows users=E2=80=A6) > Is there a manual for the syntax and special content like how the = address structure works and things like the BCP14 boilerplate? Writing a manual is on my backlog. Up to then, try http://rfc.space > What is PIs? Processing instructions, things like and = (the second one is = not the usual way to write these, BTW). >> (Interestingly, I=E2=80=99m a zero tolerance guy when it comes to the = actual writing, but I don=E2=80=99t care about tool syntax very much = while doing so =E2=80=94 the focus is on the text.) >=20 > The focus is not just the text but the flow of the document. As I = write, I want to work at seeing that one part flows into another. Which is easy to see in the unobliterated view that markdown provides=E2=80= =A6 But, yeah, folding helps. >> I don=E2=80=99t run surveys on things like this but it seems most = editors these days do support markdown, including code folding where = that is a standard feature of the editor (e.g., use the TAB key in emacs = markdown-mode). Too bad that Geany doesn=E2=80=99t. >=20 > Can you provide names of a couple? I will also ask on the Fedora = user list. Since I=E2=80=99ve been pretty much wed to emacs for the last 31 years, = I don=E2=80=99t analyze the scene a lot. Atom (and sublime) are the tools that my students like, if they don=E2=80=99= t go all the way to emacs (or vim, but that is a different story). >>> My time writing and moving around in the draft is thus more focused = and better spent. >> An editor that supports code folding is indeed a useful tool to have. >>=20 >>> I suppose things grow on us. I will continue to look at this new = stuff, but for now will stay with xml. >> So no need to convert the other XML file? >=20 > I did send you a 2nd one last night. Will do, then. Gr=C3=BC=C3=9Fe, Carsten From nobody Fri Aug 2 14:44:59 2019 Return-Path: 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 780F212013B for ; Fri, 2 Aug 2019 14:44:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=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 i9dlm9R0P8gm for ; Fri, 2 Aug 2019 14:44:54 -0700 (PDT) Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (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 74A6B120168 for ; Fri, 2 Aug 2019 14:44:54 -0700 (PDT) Received: by mail-qt1-x832.google.com with SMTP id k10so6298682qtq.1 for ; Fri, 02 Aug 2019 14:44:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Q4szC+X8UnepGznEKegGk4Fnxvg4wlpd1Ks+T3R+jiU=; b=csPvQPXU/LkYyFx48tLMI9ORxV8vTyJrqwJTgijujfmq4k6fCj7M+aGshvorsudl2P O+h9nHp7JDposCNz4i0m9zjX+YUHa3KOfobiZfuSZxNzxBeTiZWXS2BQonAdGRFBf8RA gJ9CushLkJN9fwY+LTuz4hIsoEfrRMn7rBzyNcqaaswhC2CvIpF3q78CnsL5WYsx2Hqx +dO/lAp/3lJtkMMiE0TuMkTpdqgtbIpAUS48p6XFk6TSPMX/4d7xy2WDKOCpd7UH8V8O aMPXsR4OZmNDUyT6LI5fjVuaCgppNhMGqQ70Z05j9v6scSIrCdjzI2ovOQpVxytOQ1Ac krOQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Q4szC+X8UnepGznEKegGk4Fnxvg4wlpd1Ks+T3R+jiU=; b=S47Cor0OblCCywgNx41PlQ1qnyxAoGfjB07U0dOOr91JSZDnSKieYBrK7o8k8XJORU 6Yh+MNqMYgyFRNkBuilKN8y2l/IVY6F/tTAvNi9A16OIo8Ch2DZRhXOEU5V+9rak/QuH vVZtw7D8bdeqrxJm7bs4+1JdhG9TZpzP2gnMhHAvkrW5yaP9BGyleeRKwq2wTFn7mO7M yRoQS/hIRXbb8QyeA+Hl5fn1srCxGLKT4FrRbPTwusCRYww/8IZLCMB93GqGVxVGN+61 RgGIy9cmO+Ui1qnM1PdQxcByJLa+FltYQKJL1wRjCsU1ZEb9QiFvQrLUUvismSdnHhbK SCWg== X-Gm-Message-State: APjAAAWKUPtyT7nzNyeDPEUwiIDwVa1hDGooYb5EJBRUCeOxidYwPzeD lY1EQ6jiKsLjl96N9YWcaUzJjqTfmTimt4yC1qfmQxta X-Google-Smtp-Source: APXvYqzKCmoda6ehb5RBPg63EiXUUefz3jJONbOTxQnHeElCWP7CXStjZTqMftK9CgIyabdcjl9NgeXeXZABvf1MYdw= X-Received: by 2002:a05:6214:601:: with SMTP id z1mr2845124qvw.197.1564782293406; Fri, 02 Aug 2019 14:44:53 -0700 (PDT) MIME-Version: 1.0 References: <08a2115c-54a4-b049-02ea-340f8e7dce20@htt-consult.com> <3f9c98f8-5f9e-f4cb-9226-77cf57280b40@htt-consult.com> <3c3659b1-1120-82f8-a099-9a44333d8349@htt-consult.com> In-Reply-To: <3c3659b1-1120-82f8-a099-9a44333d8349@htt-consult.com> From: "Andrew G. Malis" Date: Fri, 2 Aug 2019 17:44:42 -0400 Message-ID: To: Robert Moskowitz Cc: Carsten Bormann , "xml2rfc@ietf.org" Content-Type: multipart/alternative; boundary="000000000000bfe03f058f29442e" Archived-At: Subject: Re: [xml2rfc] xml to markdown? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Aug 2019 21:44:58 -0000 --000000000000bfe03f058f29442e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Bob, Did you try reading the markdown source that I sent you? It's "native" source written from scratch rather than converted from XML. You might find it easier as a semi-tutorial. I find it extremely straightforward to write in markdown. Cheers, Andy On Fri, Aug 2, 2019 at 12:51 PM Robert Moskowitz wrote: > > > On 8/2/19 2:17 AM, Carsten Bormann wrote: > > On Aug 2, 2019, at 03:34, Robert Moskowitz wrote: > >> Report on my first real experience reading a kramdown draft (what is > the difference between kramdown and markdown?). > > kramdown is an implementation of a markdown processor. > > kramdown-rfc2629 (or kramdown-rfc for short) is a tool that uses > kramdown as its markdown implementation and generates RFCXML. > > Only kramdown rpm is rubygem-kramdown. I doubt if that will help me. > > > > >> The .md file of my .xml is cryptic. There is a lot of assumed > knowledge. Stuff you have to remember to format right. > > Right, there is the markdown syntax (which many of us use daily anyway)= , > and then there is some syntax to support referencing and other RFC-specif= ic > things. Syntax that gets in the way much less than XML does. > > Is there a manual for the syntax and special content like how the > address structure works and things like the BCP14 boilerplate? > > To me, the xml syntax helps me visualize the data structure of the > document. But then I am dyslexic. > > >> Well xml has to be formatted right, but it is a rigorous structure tha= t > your editor can pretty much tell you have it right, even before you run > xml2rfc. > > Markdown syntax is supported by many editors. But there is little need > for that, as markdown syntax is intuitive (*). > > > > (*) intuitive is another word for familiar. If you don=E2=80=99t encou= nter > markdown in your daily life a lot, there is some learning involved for it > to become familiar=E2=80=A6 > > > > More importantly, markdown lends itself to a slightly different style o= f > working than XML: > > That last point is putting it mildly. I have NO other encounters with > markdown in my daily life let alone monthly life! Whereas xml is like > html and I do hand coding of my web pages (see www.htt-consult.com, > particularly the 'new' stuff). > > And there is nothing intuitive about markdown. It is all rout > learning. IMHO. > > > Just write. You can always worry about syntax later. > > > > XML-supporting editors tend to provide this straightjacket that you hav= e > to work in, so you are concerned with the syntax before you actually can > lay down text. (And then, there are things like PIs where they don=E2=80= =99t help > at all.) > > I find it easy. Create a section with anchor, make a text block, and > start writing. And much of that is copy and paste. > > What is PIs? > > > (Interestingly, I=E2=80=99m a zero tolerance guy when it comes to the a= ctual > writing, but I don=E2=80=99t care about tool syntax very much while doing= so =E2=80=94 the > focus is on the text.) > > The focus is not just the text but the flow of the document. As I > write, I want to work at seeing that one part flows into another. > > > > >> Perhaps there is a plugin for Geany, > > Geany plugins don=E2=80=99t seem to be able to support code folding. > > I installed the geany-markdown plugin. All it seems to do is colorize > some command text and does not get all that kramdown uses. And no > 'folding' (I assume this is the term for collapsing a block of text) > > >> but with xml, it is easy to close the sections I am not working on and > be able to focus on the work at hand. > > It seems the code folding built in to Geany doesn=E2=80=99t support mar= kdown > (tried with 1.33). > > And the markdown pluging does not help. > > > I don=E2=80=99t run surveys on things like this but it seems most edito= rs these > days do support markdown, including code folding where that is a standard > feature of the editor (e.g., use the TAB key in emacs markdown-mode). To= o > bad that Geany doesn=E2=80=99t. > > Can you provide names of a couple? I will also ask on the Fedora user > list. > > > > >> My time writing and moving around in the draft is thus more focused an= d > better spent. > > An editor that supports code folding is indeed a useful tool to have. > > > >> I suppose things grow on us. I will continue to look at this new > stuff, but for now will stay with xml. > > So no need to convert the other XML file? > > I did send you a 2nd one last night. > > > --000000000000bfe03f058f29442e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Bob,

Did you try reading the markdown s= ource that I sent you? It's "native" source written from scra= tch rather than converted from XML. You might find it easier as a semi-tuto= rial. I find it extremely straightforward to write in markdown.
<= br>
Cheers,
Andy


On Fri, Aug 2, 201= 9 at 12:51 PM Robert Moskowitz <r= gm@htt-consult.com> wrote:


On 8/2/19 2:17 AM, Carsten Bormann wrote:
> On Aug 2, 2019, at 03:34, Robert Moskowitz <rgm@htt-consult.com> wrote:
>> Report on my first real experience reading a kramdown draft (what = is the difference between kramdown and markdown?).
> kramdown is an implementation of a markdown processor.
> kramdown-rfc2629 (or kramdown-rfc for short) is a tool that uses kramd= own as its markdown implementation and generates RFCXML.

Only kramdown rpm is rubygem-kramdown.=C2=A0 I doubt if that will help me.<= br>
>
>> The .md file of my .xml is cryptic.=C2=A0 There is a lot of assume= d knowledge.=C2=A0 Stuff you have to remember to format right.
> Right, there is the markdown syntax (which many of us use daily anyway= ), and then there is some syntax to support referencing and other RFC-speci= fic things.=C2=A0 Syntax that gets in the way much less than XML does.

Is there a manual for the syntax and special content like how the
address structure works and things like the BCP14 boilerplate?

To me, the xml syntax helps me visualize the data structure of the
document.=C2=A0 But then I am dyslexic.

>> Well xml has to be formatted right, but it is a rigorous structure= that your editor can pretty much tell you have it right, even before you r= un xml2rfc.
> Markdown syntax is supported by many editors.=C2=A0 But there is littl= e need for that, as markdown syntax is intuitive (*).
>
> (*) intuitive is another word for familiar.=C2=A0 If you don=E2=80=99t= encounter markdown in your daily life a lot, there is some learning involv= ed for it to become familiar=E2=80=A6
>
> More importantly, markdown lends itself to a slightly different style = of working than XML:

That last point is putting it mildly.=C2=A0 I have NO other encounters with=
markdown in my daily life let alone monthly life!=C2=A0 Whereas xml is like=
html and I do hand coding of my web pages (see www.htt-consult.com, particularly the 'new' stuff).

And there is nothing intuitive about markdown.=C2=A0 It is all rout
learning.=C2=A0 IMHO.

> Just write.=C2=A0 You can always worry about syntax later.
>
> XML-supporting editors tend to provide this straightjacket that you ha= ve to work in, so you are concerned with the syntax before you actually can= lay down text.=C2=A0 (And then, there are things like PIs where they don= =E2=80=99t help at all.)

I find it easy.=C2=A0 Create a section with anchor, make a text block, and =
start writing.=C2=A0=C2=A0=C2=A0 And much of that is copy and paste.

What is PIs?

> (Interestingly, I=E2=80=99m a zero tolerance guy when it comes to the = actual writing, but I don=E2=80=99t care about tool syntax very much while = doing so =E2=80=94 the focus is on the text.)

The focus is not just the text but the flow of the document.=C2=A0 As I write, I want to work at seeing that one part flows into another.

>
>> Perhaps there is a plugin for Geany,
> Geany plugins don=E2=80=99t seem to be able to support code folding.
I installed the geany-markdown plugin.=C2=A0 All it seems to do is colorize=
some command text and does not get all that kramdown uses. And no
'folding' (I assume this is the term for collapsing a block of text= )

>> but with xml, it is easy to close the sections I am not working on= and be able to focus on the work at hand.
> It seems the code folding built in to Geany doesn=E2=80=99t support ma= rkdown (tried with 1.33).

And the markdown pluging does not help.

> I don=E2=80=99t run surveys on things like this but it seems most edit= ors these days do support markdown, including code folding where that is a = standard feature of the editor (e.g., use the TAB key in emacs markdown-mod= e).=C2=A0 Too bad that Geany doesn=E2=80=99t.

Can you provide names of a couple?=C2=A0 I will also ask on the=C2=A0 Fedor= a user
list.

>
>> My time writing and moving around in the draft is thus more focuse= d and better spent.
> An editor that supports code folding is indeed a useful tool to have.<= br> >
>> I suppose things grow on us.=C2=A0 I will continue to look at this= new stuff, but for now will stay with xml.
> So no need to convert the other XML file?

I did send you a 2nd one last night.


--000000000000bfe03f058f29442e-- From nobody Mon Aug 5 11:42:30 2019 Return-Path: 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 13CE612004A for ; Mon, 5 Aug 2019 11:42:29 -0700 (PDT) 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bangj.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 kqkddxjmo7lP for ; Mon, 5 Aug 2019 11:42:27 -0700 (PDT) Received: from oj.bangj.com (69-77-154-174.static.skybest.com [69.77.154.174]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8391B12003E for ; Mon, 5 Aug 2019 11:42:27 -0700 (PDT) Received: from [172.16.25.146] (69-77-155-155.static.skybest.com [69.77.155.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id 9A11D317FE for ; Mon, 5 Aug 2019 14:42:26 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bangj.com; s=201907; t=1565030546; bh=maWzcLpD2YkeDeAaimC/E+1LrilsKRyWPajAMaMRyBM=; h=From:Subject:Date:To:From; b=E3mJM0XR1RbNRy3JdmfQ4cxhULoK79GizFQpfpk9gctYO3tT8GTD3xzvtqNP75dFw YrfE/sLdAGNYt0pBvvQjZKGlnGcT5h8sBNfylF2Tn6pGBH9JpC4s0Jb0Hily7vweC0 Mi8avCM4kiL15YJXJUQj8R3fez4uEAb/cgnJP3MKAXywHdIxK4M81CH25h8wYWtJGH TZ3RGwVKN1W4hfHuNsPkfj7QTHNAK4vTi172chU7SXFufkGuvBkkWwWMc//rvdW0VY uFKdhFlLinG+dkV+WDfdOtRQhHangqNVvfeMMIVFrtsi8QmpmE4eueov895rPUXgSI L2Np0ropdbYcg== From: Tom Pusateri Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3570.1\)) Message-Id: <4B64AFBF-B429-4C1E-8001-B4DEB6D59BFC@bangj.com> Date: Mon, 5 Aug 2019 14:42:26 -0400 To: XML2RFC Interest Group X-Mailer: Apple Mail (2.3570.1) Archived-At: Subject: [xml2rfc] new element help X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2019 18:42:29 -0000 I tried to convert to the new format (which isn=E2=80=99t defined in = the xml2rfc v2 vocabulary) and I get this error for the following input: TTL=E2=89=A50 xml2rfc draft-ietf-dnssd-push.xml -o draft-ietf-dnssd-push.txt --text Parsing file draft-ietf-dnssd-push.xml Error: Expected expansion parts to include at least "num", but = found format=3D"{char}" Error: Expected expansion parts to include at least "num", but = found format=3D"{char}" Created file draft-ietf-dnssd-push.txt This seems like it would be valid in: = https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-note= s-09#appendix-A.1 So I=E2=80=99m not sure how I=E2=80=99m supposed to just get the = GREATER-THAN OR EQUAL without quotes and without the number notation. Thanks, Tom From nobody Mon Aug 5 13:30:55 2019 Return-Path: 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 0F7DA1200FF for ; Mon, 5 Aug 2019 13:30:54 -0700 (PDT) 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=unavailable 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 v9NKf2UeK2ij for ; Mon, 5 Aug 2019 13:30:52 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24E8B120047 for ; Mon, 5 Aug 2019 13:30:52 -0700 (PDT) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:52207 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1hujd0-000641-SB; Mon, 05 Aug 2019 13:30:50 -0700 To: Tom Pusateri , XML2RFC Interest Group References: <4B64AFBF-B429-4C1E-8001-B4DEB6D59BFC@bangj.com> From: Henrik Levkowetz Message-ID: <244979f3-e3fc-506f-3859-671617b829fd@levkowetz.com> Date: Mon, 5 Aug 2019 22:30:37 +0200 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: <4B64AFBF-B429-4C1E-8001-B4DEB6D59BFC@bangj.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="r5B4j0fInKG2qOnMe584N0lf6CohBuh23" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: xml2rfc@ietf.org, pusateri=40bangj.com@dmarc.ietf.org 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: Subject: Re: [xml2rfc] new element help X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2019 20:30:54 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --r5B4j0fInKG2qOnMe584N0lf6CohBuh23 Content-Type: multipart/mixed; boundary="AvEdOaLueWB0WVrSAi270RPhvCnlfdcfm"; protected-headers="v1" From: Henrik Levkowetz To: Tom Pusateri , XML2RFC Interest Group Message-ID: <244979f3-e3fc-506f-3859-671617b829fd@levkowetz.com> Subject: Re: [xml2rfc] new element help References: <4B64AFBF-B429-4C1E-8001-B4DEB6D59BFC@bangj.com> In-Reply-To: <4B64AFBF-B429-4C1E-8001-B4DEB6D59BFC@bangj.com> --AvEdOaLueWB0WVrSAi270RPhvCnlfdcfm Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Tom, Short answer: This requires math support, and is not covered by the functionality provided by the element, as the intention of that element is to _always_ provide a rendering-agnostic codepoint value in order to make the use of non-ASCII codepoints in protocol specifications explicit, independent of the rendering format. Math support has been discussed; I think it's a good idea, and I have a proposal, but it's not currently part of any specification. The best way, currently, to achieve what you want in a v3 XML source, is to present the full equation as or . One more point inline: On 2019-08-05 20:42, Tom Pusateri wrote: > I tried to convert to the new format (which isn=E2=80=99t defined i= n the xml2rfc v2 vocabulary) and I get this error for the following input= : >=20 > TTL=E2=89=A50 >=20 > xml2rfc draft-ietf-dnssd-push.xml -o draft-ietf-dnssd-push.txt --text > Parsing file draft-ietf-dnssd-push.xml > Error: Expected expansion parts to include at least "num", bu= t found format=3D"{char}" > Error: Expected expansion parts to include at least "num", bu= t found format=3D"{char}" > Created file draft-ietf-dnssd-push.txt >=20 > This seems like it would be valid in: >=20 > https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-n= otes-09#appendix-A.1 Yes, that should point out that 'num' always is required with . I'll add that. It's mentioned for the simplified format (in A.1.1) but should= also be mentioned in A.1.2. Regards, Henrik > So I=E2=80=99m not sure how I=E2=80=99m supposed to just get the GREATE= R-THAN OR EQUAL without quotes and without the number notation. >=20 > Thanks, > Tom >=20 > _______________________________________________ > xml2rfc mailing list > xml2rfc@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc >=20 --AvEdOaLueWB0WVrSAi270RPhvCnlfdcfm-- --r5B4j0fInKG2qOnMe584N0lf6CohBuh23 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl1Ike0ACgkQTptXS4+7 FxqjnRAAwCY2C/gTwtQ57pIiFXb5aHfJEJfb5qIm7Wf7lID3IzQKmCc3IAgott9z vOlAic2zvx7WzSWeHz0S/dqrauo+DCp7qndzZlg6Qs7Bfy+9QknpBh+g/hyxfi+i Z4N8z2tF5Q/65wLThRP8k542TMo2BZy23KLzteyPWqTYfxMWQlJo7GlfwLGnBHIX AUY63wy0z1AS/rXky/MJuzAlaY1VnZNRpQW3MghIIs0wiMwIu9IhiS1IoGVv47km Uq9cdPoYvu9n9HHo2th3BrfR73Wc7hSAONyjODX0jBZuSK1uVfAdMWLr2stWAsbG TitptKLzCUQsffm9b98m8zMhgL8rVw7DcOx/ed7qQ92lwIC9bCtBXkAvJjP3uljT ScLHxu2ApvB1EaHgiz7brQ0O3r2eA3QypOehCZ+x+MuKaHpjrNs3hqfuhg8OgCts DrOHEzsviB7wzWAE6/ZS9vmVBRTFh8hnpE8BW5H6Zz3ZoSvCPfq6Btuso+wW54a3 apfAk7raI3G1CyMLPmaCU84jiQVS0/Mix87g7v+8m7vkHEyqKlerFBU43XGa3SgY p626PzL4+yJCgdxA2q3gew/hoyRvlOKL4l5s9E195v/UTqjc9g1Jwmcjs6zs60/5 EKkdWzUy29j+Cc25mxWrMr/gHN+10eVI7h2t6X88UpDAr+2naDc= =8HOU -----END PGP SIGNATURE----- --r5B4j0fInKG2qOnMe584N0lf6CohBuh23-- From nobody Sat Aug 10 08:24:12 2019 Return-Path: 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 721D0120043; Sat, 10 Aug 2019 08:23:56 -0700 (PDT) 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 M3L3d1ZYG35T; Sat, 10 Aug 2019 08:23:54 -0700 (PDT) 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 748B812001B; Sat, 10 Aug 2019 08:23:54 -0700 (PDT) Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from ) id 1hwTDm-00064V-6E; Sat, 10 Aug 2019 08:23:54 -0700 To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org Message-Id: From: Henrik Levkowetz Date: Sat, 10 Aug 2019 08:23:54 -0700 X-SA-Exim-Connect-IP: 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: Subject: [xml2rfc] New xml2rfc release: v2.24.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Aug 2019 15:23:57 -0000 Hi, This is an automatic notification about a new xml2rfc release, v2.24.0, generated when running the mkrelease script. Release notes: xml2rfc (2.24.0) ietf; urgency=medium This release addresses a number of issues and minor feature requests from the RFC Editor. Excerpt from the commit log: * Added a switch --rfc-reference-base-url to specify an alternative base url when using section links. * Stabilized XML and HTML output attribute order. With lxml 4.40, the handling of attribute order changed for Py 3.6 and higher, to match the use of ordered dictionaries in Py3.6+. Initial attributes set on an element are now sorted by key value. This matches what lxml did previously, and still does for Py 2.7 and Py 3.[0-5]. Enforcing sorted initial attributes under Py 3.6+ makes our output more stable under varying versions of lxml and Python. * Added support for section references in the v3 text formatter. Refactored some of the xref handling in preptool. Added warnings for some xref attribute and content combinations that don't make sense. * Tweaked the error message for use of -o with multiple output formats. * Tweaked the layout of v3 text front page to correctly handle unicode codepoints of different width than 1, in order to get correct line lengths for authors with CJK names. * Handled a problem with an unwanted space between year and the following comma in HTML rendering. * When using the built-in lxml Element remove() method, it unexpectedly removes not only the element, but also the element's tail. Dealt with this by using our own remove() where needed. * Added pilcrows on
, to match pilcrows on other list entries. * Removed address lines with only punctuation from the author address rendering, eliminating for instance lines containing only a comma. * Added a viewport meta tag, to improve rendering on some devices. * Added class 'selfRef' on some Figure and Table links that were missing it. * Changed the address format to always start with the author name, according to a conversation with the RFC-Editor staff in Prague. * Changed the V3 writer note() method to obey quiet and verbose in the same manner as log.note(). * Changed the v3 validate() from being separate methods for the v2v3 converter and the preptool to a common method on BaseV3Writer. * Tweaked the handling to make year ranges and fuzzy dates possible. * Fixed an issue where text was lost when immediately preceded by . * Added a --bom text format option, to insert a BOM mark at the beginning of the text format output. Also added a BOM test, and removed some irrelevant switches. * Made the line spacing of the same as for . * Removed stripping of horizontal whitespace at the start of artwork in list items. * Removed an unwanted attribute inheritance of 'ulEmpty' for
    . * Fixed an issue with the CSS stylesheet for compact
    lists. * Removed an unintentional change that would permit a 'contributor' author role. -- Henrik Levkowetz 10 Aug 2019 08:22:35 -0700 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.24.0' Regards, Henrik (via the mkrelease script) From nobody Mon Aug 12 15:13:45 2019 Return-Path: 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 D9B21120D28 for ; Mon, 12 Aug 2019 15:13:43 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 vjBhpChYhjXR for ; Mon, 12 Aug 2019 15:13:42 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD0E2121DFC for ; Mon, 12 Aug 2019 09:34:16 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 2684960964 for ; Mon, 12 Aug 2019 12:34:14 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id tFPohFk1llJG for ; Mon, 12 Aug 2019 12:34:10 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 0EFFE60933 for ; Mon, 12 Aug 2019 12:34:10 -0400 (EDT) To: "xml2rfc@ietf.org" From: Robert Moskowitz Message-ID: Date: Mon, 12 Aug 2019 12:34:04 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: [xml2rfc] Where can I get instructions in using CODE BEGIN/END? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Aug 2019 22:13:44 -0000 In my draft-moskowitz-eddsa-pki, I have LOTS of blocks of command line commands and some .cnf file content. Elliot Lear recommended I change my use of
    or
    file “somefilename" But I am not having success finding help on using code begins. Can someone provide some pointers? thanks From nobody Mon Aug 12 16:26:50 2019 Return-Path: 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 8F689120018 for ; Mon, 12 Aug 2019 16:26:49 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 hSAqVJmPC5ew for ; Mon, 12 Aug 2019 16:26:48 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92F0812000E for ; Mon, 12 Aug 2019 16:26:48 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id BE1BC615E6 for ; Mon, 12 Aug 2019 19:26:47 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id X4UwkwCQxwSs for ; Mon, 12 Aug 2019 19:26:43 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id F422160964 for ; Mon, 12 Aug 2019 19:26:41 -0400 (EDT) To: "xml2rfc@ietf.org" References: From: Robert Moskowitz Message-ID: Date: Mon, 12 Aug 2019 19:26:33 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [xml2rfc] Where can I get instructions in using CODE BEGIN/END? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Aug 2019 23:26:49 -0000 On 8/12/19 12:34 PM, Robert Moskowitz wrote: > In my draft-moskowitz-eddsa-pki, I have LOTS of blocks of command line > commands and some .cnf file content. > > Elliot Lear recommended I change my use of > >
    > > or > >
    > with > > file “somefilename" > > But I am not having success finding help on using code begins. > > Can someone provide some pointers? > > thanks I tried a couple things and nothing worked.
    stuff
    Did not work, and that SEEMS to be what is said in the rfc. From nobody Mon Aug 12 22:23:27 2019 Return-Path: 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 34C5C120077 for ; Mon, 12 Aug 2019 22:23:26 -0700 (PDT) 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 kuox0j6W0s8P for ; Mon, 12 Aug 2019 22:23:25 -0700 (PDT) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 E9B74120073 for ; Mon, 12 Aug 2019 22:23:24 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from ) id 1hxPHG-0004Bu-Iv; Tue, 13 Aug 2019 05:23:22 +0000 Date: Mon, 12 Aug 2019 22:23:22 -0700 Message-ID: From: Randy Bush To: Robert Moskowitz Cc: "xml2rfc@ietf.org" In-Reply-To: References: User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.2 Mule/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Archived-At: Subject: Re: [xml2rfc] Where can I get instructions in using CODE BEGIN/END? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Aug 2019 05:23:26 -0000 i am using From nobody Mon Aug 12 22:58:40 2019 Return-Path: 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 F281B120089 for ; Mon, 12 Aug 2019 22:58:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.198 X-Spam-Level: X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 Jt_rG3j8WPHA for ; Mon, 12 Aug 2019 22:58:36 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E730C120077 for ; Mon, 12 Aug 2019 22:58:35 -0700 (PDT) Received: from [192.168.217.110] (p548DCCB9.dip0.t-ipconnect.de [84.141.204.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4672896rr3z10g2; Tue, 13 Aug 2019 07:58:33 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Carsten Bormann In-Reply-To: Date: Tue, 13 Aug 2019 07:58:33 +0200 Cc: "xml2rfc@ietf.org" X-Mao-Original-Outgoing-Id: 587368711.908594-f64360842cd5e3ba75c8bf1575be2726 Content-Transfer-Encoding: quoted-printable Message-Id: <0CF631C2-880C-47F9-B884-AC8BCA8399C6@tzi.org> References: To: Robert Moskowitz X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [xml2rfc] Where can I get instructions in using CODE BEGIN/END? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Aug 2019 05:58:38 -0000 You are not saying whether this is v2 or v3. You can=E2=80=99t remove the XML (
    in v2). The etc. is actual content (it should be in the CDATA of = the artwork, or you will need to escape the <). It is just misleading that it almost looks like an XML tag. Gr=C3=BC=C3=9Fe, Carsten > On Aug 12, 2019, at 18:34, Robert Moskowitz = wrote: >=20 > In my draft-moskowitz-eddsa-pki, I have LOTS of blocks of command line = commands and some .cnf file content. >=20 > Elliot Lear recommended I change my use of >=20 >
    >=20 > or >=20 >
    =20 > with >=20 > file =E2=80=9Csomefilename" >=20 > But I am not having success finding help on using code begins. >=20 > Can someone provide some pointers? >=20 > thanks >=20 > _______________________________________________ > xml2rfc mailing list > xml2rfc@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc >=20 >=20 From nobody Tue Aug 13 02:30:02 2019 Return-Path: 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 F05551200D8 for ; Tue, 13 Aug 2019 02:30:00 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 KdbThx0Pd7kn for ; Tue, 13 Aug 2019 02:29:58 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FF7312008F for ; Tue, 13 Aug 2019 02:29:58 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 82C9F615E6; Tue, 13 Aug 2019 05:29:56 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id mMGZIldA7INp; Tue, 13 Aug 2019 05:29:50 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 1FCF3607A5; Tue, 13 Aug 2019 05:29:47 -0400 (EDT) To: Carsten Bormann Cc: "xml2rfc@ietf.org" References: <0CF631C2-880C-47F9-B884-AC8BCA8399C6@tzi.org> From: Robert Moskowitz Message-ID: Date: Tue, 13 Aug 2019 05:29:44 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <0CF631C2-880C-47F9-B884-AC8BCA8399C6@tzi.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [xml2rfc] Where can I get instructions in using CODE BEGIN/END? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Aug 2019 09:30:01 -0000 The pip --update gets me v2... Which seems to be Python 2 which is EOL the end of this year. So the actually appears in your draft.  OK.  So what is the RFC talking about (sec 2.48)? That kind of breaks up the flow of reading the draft, especially my e_dsa-pki drafts that have LOTS of separate commands and this was recommended to make it easier than select and copy by using tools. But is there some way to perhaps name to file extracted like command1.sh or something like that so the .sh will inform the tool that this is a script and to set -x on the attribute? On 8/13/19 1:58 AM, Carsten Bormann wrote: > You are not saying whether this is v2 or v3. > > You can’t remove the XML (
    in v2). > The etc. is actual content (it should be in the CDATA of the artwork, or you will need to escape the <). > It is just misleading that it almost looks like an XML tag. > > Grüße, Carsten > > >> On Aug 12, 2019, at 18:34, Robert Moskowitz wrote: >> >> In my draft-moskowitz-eddsa-pki, I have LOTS of blocks of command line commands and some .cnf file content. >> >> Elliot Lear recommended I change my use of >> >>
    >> >> or >> >>
    > >> with >> >> file “somefilename" >> >> But I am not having success finding help on using code begins. >> >> Can someone provide some pointers? >> >> thanks >> >> _______________________________________________ >> xml2rfc mailing list >> xml2rfc@ietf.org >> https://www.ietf.org/mailman/listinfo/xml2rfc >> >> > From nobody Tue Aug 13 03:18:52 2019 Return-Path: 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 87B8F1200FF for ; Tue, 13 Aug 2019 03:18:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.198 X-Spam-Level: X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 OBuTxaM7dHa9 for ; Tue, 13 Aug 2019 03:18:48 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E93F51200FA for ; Tue, 13 Aug 2019 03:18:47 -0700 (PDT) Received: from [192.168.217.110] (p548DCCB9.dip0.t-ipconnect.de [84.141.204.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4677wP6zwqz10gH; Tue, 13 Aug 2019 12:18:45 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Carsten Bormann In-Reply-To: Date: Tue, 13 Aug 2019 12:18:46 +0200 Cc: "xml2rfc@ietf.org" X-Mao-Original-Outgoing-Id: 587384324.981181-89df66a39fc4c65e3a0fc822b2b1421e Content-Transfer-Encoding: quoted-printable Message-Id: References: <0CF631C2-880C-47F9-B884-AC8BCA8399C6@tzi.org> To: Robert Moskowitz X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [xml2rfc] Where can I get instructions in using CODE BEGIN/END? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Aug 2019 10:18:50 -0000 On Aug 13, 2019, at 11:29, Robert Moskowitz wrote: >=20 > The pip --update gets me v2... >=20 > Which seems to be Python 2 which is EOL the end of this year. I was not talking about the Python version, but the RFCXML version. The xml2rfc you get with pip --update does RFCXMLv2 by default and = RFCXMLv3 when giving the --v3 option. > So the actually appears in your draft. OK. So what is the = RFC talking about (sec 2.48)? =E2=80=9CThe RFC=E2=80=9D is probably the RFXMLv3 RFC? > That kind of breaks up the flow of reading the draft, especially my = e_dsa-pki drafts that have LOTS of separate commands and this was = recommended to make it easier than select and copy by using tools. But = is there some way to perhaps name to file extracted like command1.sh or = something like that so the .sh will inform the tool that this is a = script and to set -x on the attribute? I generally collect the source code in an appendix, so I can use the = code again unimpeded from etc. in the text of the draft. = RFC 5662, the numerically first RFC to use the convention, = does otherwise; it=E2=80=99s not too bad either. Gr=C3=BC=C3=9Fe, Carsten From nobody Tue Aug 13 05:01:09 2019 Return-Path: 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 387C312013B for ; Tue, 13 Aug 2019 05:01:08 -0700 (PDT) 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 Qyu5ye2Bs_P7 for ; Tue, 13 Aug 2019 05:01:06 -0700 (PDT) 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 79233120125 for ; Tue, 13 Aug 2019 05:01:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1565697657; bh=bnCjbaKCiRFOGU5EgLY2fxFm336IQT/L4eEaN0KWr8k=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=A+MRGHX+RB0bQKdfZishkjNE0iAZ1hXur7WdPmfpzpN+inDZNnimjeIH5EC/dWyaG iQKSK1IPWvFWYDw5bLyXk+o1rRVb8qrOqRT7aDXfkIF0o6UMCEGgJQrQzVOZnGH8gU DoeRngfJKTesXvPvde316DyNP9HhQFkIaxsfGyEg= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [10.10.160.139] ([208.131.168.244]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1M9Wys-1huDgz0vPY-005YNn for ; Tue, 13 Aug 2019 14:00:57 +0200 To: xml2rfc@ietf.org References: <0CF631C2-880C-47F9-B884-AC8BCA8399C6@tzi.org> From: Julian Reschke Message-ID: Date: Tue, 13 Aug 2019 14:00:48 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:x0lcZZOPlX/0ti68R72ZuCxXfAkUj7RNtUDqETHGHl/odhIuqsS UoQ4R7SnClnPSxNR0Lr68ikLay1uf6ZaCjjU/ZIS8BHPdiiEm2hNxdZnRNv9+Hu+7NVnJ0k Hfx8MShwWS0MBsN0FxZIEIKX0C3M0o0CceNM9AbR0TruCBbhhvLwl61WAb3Mawn4vD33MkK ISi4ip2QTEzrxB/W7veNQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:jxk1LKRrlEs=:POg0ygCYq1cMCFUIs6/BfD Lsf+gaewHMzX2W+/Gc/Juylu64juL6L7EnKbbZk6tmQHhGcc9UecmCiBp3D4fpUflbRJvg6LN NikFaPzRNC6uPTcTZ7xifqHBHdPPmWUQF7OceHpZGgACtSid2AhakIzmZyNYH4ql0RmeUvfBD l+BflZTjeILBqchHJzX2/Jtmlv9T/DJ3WdviYcI95Wz31WEpTYIRvuOermYInjtYjfZ9egebd M1zs2uxWRhwy7usWmaIEOD1lezA0FG5QC8ykOj+NXu3BWkS1JgQS9nrV5PVYhp7ZIKJ3nhsmY z9m56kmT2+SABNzynoxvF4mxSpd89+je2dnEnyI6u6+FIR2y/Vvmpj0b85jfJjGpzLCcPdXQv SNXkbDnINeDtplpndKVurHTU4Xy/tF0P04mYoa7Qilz1XgT1iLqZ4WcJZ+gNpwtJStwFSyIiX qugBgtwiJoJKB3GND0uRpzCzkQc6bUJsFT0xhKNbxLClfry6XSRw/V+l/Mm6/lIM4EHOPTSt3 NKJy1LA2f7In10UfCdRHeGIQQZfIEjdjx4GGczcBI4pL93IRNWxdSB5S3RhbCGd2RkYcP999I eJueKxcr1r5itpktv2Ml1/7Sz9BsHDn7UgfEjMDTvNmqY/niCQP8cm2QHVYGh3DaG/DNuLiML NMxAHoU4wDlj/yjJvzNaWyQHv5mrexwnveH3UYB4RVQEbp2dNExryEyuQX+FjAJqhsekv6CKi kAIYY2hF8bNHnZc7f8y7wSObn9rrkQfeFMJQzFYelMvudxoliC/usRls7MAeRPOvmX+fTobgu TlRq39qaWVaWFc9xsDo3CDsZ7SaNXpYijWFIAsX40NZqnKTmN5NXsHrkw1ynApxSCPeb3VMVV 9bboKnhJGNkgMVn+hO2Fnl70iOQ30Rqa5t9CSJGb9Nl8fg9RkzY9USNv5R+uD1ujCBIL1xQZ5 ctBda6LjBbm9YQYr1KHKEfEkFMSkSTNSoV+ed2Wd9ClOAtSlkDhvzonNJ2dE/3hkAz6CyUUxl kSC2dYBRnferKpVHF0xp6xLHN/XzFB3ggePot4Ezgn70rJQJoHln20T22mkBVmBRd6KL4ebUk HjN3zQmzsPk/QiT8J/xrzZBTmkVLab6SR01koW3MYGdNLQUIcbq1vvs3msGzUOf0A0/+8eG1o +XYZo= Archived-At: Subject: Re: [xml2rfc] Where can I get instructions in using CODE BEGIN/END? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Aug 2019 12:01:08 -0000 Am 13.08.2019 um 11:29 schrieb Robert Moskowitz: > The pip --update gets me v2... > > Which seems to be Python 2 which is EOL the end of this year. > > So the actually appears in your draft.=C2=A0 OK.=C2=A0 So wha= t is the > RFC talking about (sec 2.48)? > > That kind of breaks up the flow of reading the draft, especially my > e_dsa-pki drafts that have LOTS of separate commands and this was > recommended to make it easier than select and copy by using tools. But > ... AFAIC, and in general, this is bad advice. CODE BEGINS etc is only needed under certain cirumstances when it's not clear wether something falls under the rules of allowable source code extraction from the RFC. It is *not* a way to markup things so that they can be more easily extracted from the TXT version. Best regards, Julian From nobody Tue Aug 13 05:37:58 2019 Return-Path: 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 66F5A120130 for ; Tue, 13 Aug 2019 05:37:57 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 GkdHy0O5hOPl for ; Tue, 13 Aug 2019 05:37:54 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E65F120125 for ; Tue, 13 Aug 2019 05:37:54 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id C51AF615E6; Tue, 13 Aug 2019 08:37:52 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id HJwuXR1A1qQw; Tue, 13 Aug 2019 08:37:47 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 23B68607A5; Tue, 13 Aug 2019 08:37:47 -0400 (EDT) To: Julian Reschke , xml2rfc@ietf.org References: <0CF631C2-880C-47F9-B884-AC8BCA8399C6@tzi.org> From: Robert Moskowitz Message-ID: <40f5cecb-007e-0b3a-89b3-989e9ddf7378@htt-consult.com> Date: Tue, 13 Aug 2019 08:37:41 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [xml2rfc] Where can I get instructions in using CODE BEGIN/END? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Aug 2019 12:37:57 -0000 On 8/13/19 8:00 AM, Julian Reschke wrote: > Am 13.08.2019 um 11:29 schrieb Robert Moskowitz: >> The pip --update gets me v2... >> >> Which seems to be Python 2 which is EOL the end of this year. >> >> So the actually appears in your draft.  OK.  So what is the >> RFC talking about (sec 2.48)? >> >> That kind of breaks up the flow of reading the draft, especially my >> e_dsa-pki drafts that have LOTS of separate commands and this was >> recommended to make it easier than select and copy by using tools. But > > ... > > AFAIC, and in general, this is bad advice. CODE BEGINS etc is only > needed under certain cirumstances when it's not clear wether something > falls under the rules of allowable source code extraction from the RFC. I kind of wondered about this.  The commentor recommended something like: file “somefilename" And  for "tools like xym" If you look at draft-moskowitz-eddsa-pki, and draft-moskowitz-ecdsa-pki, they are filled with sections of command lines. It is quite clear that the reader would want to copy this and paste it into a terminal window, or for the setting of environment variables (these are scattered throughout), first into an editor were the readers specific values can be set. Only the appendices with their large .cnf files might make sense of the tools are able to strip out the page headers and footers.  The .cnf files are tool large to fit on a single page. Now compare this with some of my howto web pages like: http://www.htt-consult.com/CentOS7-armv7.html http://www.htt-consult.com/CentOS7-armv7-odroid.html There I have the commands in textboxes with specific CSS and javascript that when you click on the box, the content is either selected or selected and copied to the clipboard.  I provided the option of action because one of my security colleagues waxed eloquently on how a browser should never directly work with the system outside of the browser (e.g. the clipboard), so I offered the choice. Since I do upload the xml for my drafts, I could maybe add an addendum to point to readers to it for easier extraction of command blocks, and specifically easier extraction of the .cnf files that would not have the page headers and footers... In fact, adding to datatracker tools the option to get the draft's xml might be good. thanks > > It is *not* a way to markup things so that they can be more easily > extracted from the TXT version. > > Best regards, Julian > > _______________________________________________ > xml2rfc mailing list > xml2rfc@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc From nobody Sun Aug 18 13:55:52 2019 Return-Path: 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 091FB1200B9 for ; Sun, 18 Aug 2019 13:55:51 -0700 (PDT) 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 hGeBXU-bCl8f for ; Sun, 18 Aug 2019 13:55:49 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 637A012004E for ; Sun, 18 Aug 2019 13:55:49 -0700 (PDT) Received: from localhost ([::1]:57264 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1hzSDN-0003mQ-0k; Sun, 18 Aug 2019 13:55:49 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com, ietf@augustcellars.com X-Trac-Project: xml2rfc Date: Sun, 18 Aug 2019 20:55:49 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/413 Message-ID: <070.268ff901cfe53a9d92e12075dad9482a@tools.ietf.org> X-Trac-Ticket-ID: 413 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, ietf@augustcellars.com, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: [xml2rfc] #413 (Version 2 cli): eref omits angle brackets in text mode X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Aug 2019 20:55:51 -0000 #413: eref omits angle brackets in text mode When producing with --text, eref no longer encapsulates the URI with a pair of angle brackets. I found this in 2.24.0 but it is probably around longer I used v3 vocabulary. My instance that I found this for was in a at the front of the file Can be seen in the note in https://tools.ietf.org/html/draft-ietf-cose- rfc8152bis-struct-05 I don't know if this is new designed behavior or not. -- ------------------------------------+---------------------------------- Reporter: ietf@augustcellars.com | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.10.x Keywords: | ------------------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Sun Aug 18 14:08:24 2019 Return-Path: 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 BCBDB1200B9 for ; Sun, 18 Aug 2019 14:08:22 -0700 (PDT) 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 X9bm6apClVv1 for ; Sun, 18 Aug 2019 14:08:20 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E907A120047 for ; Sun, 18 Aug 2019 14:08:20 -0700 (PDT) Received: from localhost ([::1]:57717 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1hzSPU-0004Or-H2; Sun, 18 Aug 2019 14:08:20 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com, ietf@augustcellars.com X-Trac-Project: xml2rfc Date: Sun, 18 Aug 2019 21:08:20 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/414 Message-ID: <070.d25d5b84782a8e17c38b2e75c851307a@tools.ietf.org> X-Trac-Ticket-ID: 414 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, ietf@augustcellars.com, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: [xml2rfc] #414 (Version 2 cli): --legacy-list-symbols errors with v3 input X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Aug 2019 21:08:23 -0000 #414: --legacy-list-symbols errors with v3 input I did not provide the --v3 option, but the input was a v3 file and marked as such. There was an error message You can only use --legacy_list_symbols with v3 text output. -- ------------------------------------+---------------------------------- Reporter: ietf@augustcellars.com | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.10.x Keywords: | ------------------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Mon Aug 19 05:26:54 2019 Return-Path: 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 258A8120019 for ; Mon, 19 Aug 2019 05:26:52 -0700 (PDT) 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 iS_yaEGurr7j for ; Mon, 19 Aug 2019 05:26:51 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 087D2120013 for ; Mon, 19 Aug 2019 05:26:51 -0700 (PDT) Received: from localhost ([::1]:53537 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1hzgkM-0000Qz-LR; Mon, 19 Aug 2019 05:26:50 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com X-Trac-Project: xml2rfc Date: Mon, 19 Aug 2019 12:26:50 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: /ticket/414#comment:1 Message-ID: <085.9cc83e4130ece04c16b358ca9cf4d9e9@tools.ietf.org> References: <070.d25d5b84782a8e17c38b2e75c851307a@tools.ietf.org> X-Trac-Ticket-ID: 414 In-Reply-To: <070.d25d5b84782a8e17c38b2e75c851307a@tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [xml2rfc] #414 (Version 2 cli): --legacy-list-symbols errors with v3 input X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Aug 2019 12:26:52 -0000 #414: --legacy-list-symbols errors with v3 input Changes (by henrik@levkowetz.com): * status: new => closed * resolution: => fixed Comment: Fixed in [3208]: The --legacy-list-symbols option was checked for validity before the version attribute of the input file was seen. Moved this check (and some similar cases) later, in order to permit it to be used with v3 input without giving the --v3 option. Fixes issue #414. -- -------------------------------------+---------------------------------- Reporter: ietf@augustcellars.com | Owner: henrik@levkowetz.com Type: defect | Status: closed Priority: medium | Milestone: Component: Version 2 cli | Version: 2.10.x Resolution: fixed | Keywords: -------------------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Mon Aug 19 05:34:36 2019 Return-Path: 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 CCB12120020 for ; Mon, 19 Aug 2019 05:34:34 -0700 (PDT) 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 NRCN4Fa7ciNw for ; Mon, 19 Aug 2019 05:34:33 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D57D120019 for ; Mon, 19 Aug 2019 05:34:33 -0700 (PDT) Received: from localhost ([::1]:53652 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1hzgrn-0000xD-SS; Mon, 19 Aug 2019 05:34:31 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org, rfc-editor@rfc-editor.org, arusso@amsl.com, sginoza@amsl.com Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com X-Trac-Project: xml2rfc Date: Mon, 19 Aug 2019 12:34:31 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/413#comment:1 Message-ID: <085.ea254e0a2df25c9a37e1ef316bdf876e@tools.ietf.org> References: <070.268ff901cfe53a9d92e12075dad9482a@tools.ietf.org> X-Trac-Ticket-ID: 413 In-Reply-To: <070.268ff901cfe53a9d92e12075dad9482a@tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, rfc-editor@rfc-editor.org, arusso@amsl.com, sginoza@amsl.com, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [xml2rfc] #413 (Version 2 cli): eref omits angle brackets in text mode X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Aug 2019 12:34:35 -0000 #413: eref omits angle brackets in text mode Changes (by henrik@levkowetz.com): * cc: rfc-editor@rfc-editor.org, arusso@amsl.com, sginoza@amsl.com (added) Comment: I've dithered about this, whether or not to enclose URLs in angle brackets in text mode. The change was triggered by a desire to keep the text and HTML output reasonably similar (the angle brackets are not supposed to be present in the HTML rendering) but the change could nevertheless be unwanted. At one point when working on the v3 text renderer, I went back to rendering text with angle brackets, and then undid that change again. This is probably the point where we ask the RFC Editor what's wanted. -- -------------------------------------+---------------------------------- Reporter: ietf@augustcellars.com | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.10.x Resolution: | Keywords: -------------------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Mon Aug 19 05:44:46 2019 Return-Path: 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 6DECE120019 for ; Mon, 19 Aug 2019 05:44:44 -0700 (PDT) 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 w9mYEnX54DQO for ; Mon, 19 Aug 2019 05:44:42 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D3D3120013 for ; Mon, 19 Aug 2019 05:44:42 -0700 (PDT) Received: from localhost ([::1]:53821 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1hzh1c-0003ol-Mn; Mon, 19 Aug 2019 05:44:40 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org, rfc-editor@rfc-editor.org, arusso@amsl.com, sginoza@amsl.com Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com, julian.reschke@gmx.de X-Trac-Project: xml2rfc Date: Mon, 19 Aug 2019 12:44:40 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/413#comment:2 Message-ID: <085.c915be5966f4515a1515edc890dcb648@tools.ietf.org> References: <070.268ff901cfe53a9d92e12075dad9482a@tools.ietf.org> X-Trac-Ticket-ID: 413 In-Reply-To: <070.268ff901cfe53a9d92e12075dad9482a@tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, julian.reschke@gmx.de, rfc-editor@rfc-editor.org, arusso@amsl.com, sginoza@amsl.com, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [xml2rfc] #413 (Version 2 cli): eref omits angle brackets in text mode X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Aug 2019 12:44:45 -0000 #413: eref omits angle brackets in text mode Comment (by julian.reschke@gmx.de): My 2 cents: I believe keeping the text content for HTML and TXT output in sync is a good goal. Otherwise there may be surprises when people copy & paste from different output format into email. For rfc2629.xslt and v2 time, that meant for me to always use angle brackets, as the TXT output was the default publication format, and I didn't want the HTML output to be differ. For the future, as TXT output is not considered ... that important anymore, I would proposed to reverse that: meaning no angle brackets in both formats. In any case, I believe both should be consistent. And yes, that's something the RFC Editor should decide (and the document). -- -------------------------------------+---------------------------------- Reporter: ietf@augustcellars.com | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.10.x Resolution: | Keywords: -------------------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Mon Aug 19 11:43:04 2019 Return-Path: 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 A7D70120898 for ; Mon, 19 Aug 2019 11:43:02 -0700 (PDT) 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 82dUxr2Zno-h for ; Mon, 19 Aug 2019 11:43:01 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0772612089D for ; Mon, 19 Aug 2019 11:43:01 -0700 (PDT) Received: from localhost ([::1]:34162 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1hzmcO-0005RU-22; Mon, 19 Aug 2019 11:43:00 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org, rfc-editor@rfc-editor.org, arusso@amsl.com, sginoza@amsl.com Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com, julian.reschke@gmx.de, ietf@augustcellars.com X-Trac-Project: xml2rfc Date: Mon, 19 Aug 2019 18:43:00 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/413#comment:3 Message-ID: <085.a588bbbd77d812c560ed6bd4c0556de6@tools.ietf.org> References: <070.268ff901cfe53a9d92e12075dad9482a@tools.ietf.org> X-Trac-Ticket-ID: 413 In-Reply-To: <070.268ff901cfe53a9d92e12075dad9482a@tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, julian.reschke@gmx.de, ietf@augustcellars.com, rfc-editor@rfc-editor.org, arusso@amsl.com, sginoza@amsl.com, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [xml2rfc] #413 (Version 2 cli): eref omits angle brackets in text mode X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Aug 2019 18:43:03 -0000 #413: eref omits angle brackets in text mode Comment (by ietf@augustcellars.com): My 2 cents: I believe that the important thing is to highlight it is a URI and that is the fact that should be kept in sync rather than the exact set of characters that are displayed. I don't remember what, if any, decisions where made for em et al are where currently you get things like _foo_ in the text version. I agree - it should be pushed to the RFC editor. -- -------------------------------------+---------------------------------- Reporter: ietf@augustcellars.com | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.10.x Resolution: | Keywords: -------------------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Tue Aug 20 01:37:14 2019 Return-Path: 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 679BC120911 for ; Tue, 20 Aug 2019 01:37:13 -0700 (PDT) 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 YmQiY6pQ_VH7 for ; Tue, 20 Aug 2019 01:37:12 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 259661208FF for ; Tue, 20 Aug 2019 01:37:12 -0700 (PDT) Received: from localhost ([::1]:50613 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1hzzdf-0005rJ-5M; Tue, 20 Aug 2019 01:37:11 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com, miek@miek.nl X-Trac-Project: xml2rfc Date: Tue, 20 Aug 2019 08:37:11 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/415 Message-ID: <060.ee68972e559c2b052116eda28280677d@tools.ietf.org> X-Trac-Ticket-ID: 415 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, miek@miek.nl, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: [xml2rfc] #415 (Version 2 cli): show all validation errrors X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Aug 2019 08:37:14 -0000 #415: show all validation errrors I looks like xml2rfc stops at the first validation error. This is somewhat annoying if you have a *really* long document, but making a validate becomes a game of whack a mole. {{{ Parsing file learninggo.xml learninggo.xml(3479): Error: Did not expect element blockquote there, at /rfc/middle/section[7]/section[4]/aside/blockquote learninggo.xml(3): Error: Invalid document before running preptool. Cannot continue, quitting now }}} -- ---------------------------+---------------------------------- Reporter: miek@miek.nl | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.10.x Keywords: | ---------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Tue Aug 20 03:41:37 2019 Return-Path: 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 1D78112001B for ; Tue, 20 Aug 2019 03:41:36 -0700 (PDT) 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 WbwOF8RvIN9N for ; Tue, 20 Aug 2019 03:41:34 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A6EF12001A for ; Tue, 20 Aug 2019 03:41:34 -0700 (PDT) Received: from localhost ([::1]:53080 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1i01a1-0000iI-2G; Tue, 20 Aug 2019 03:41:33 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com X-Trac-Project: xml2rfc Date: Tue, 20 Aug 2019 10:41:31 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/415#comment:1 Message-ID: <075.a9a9e8e7d2d27fa12903848a8006121e@tools.ietf.org> References: <060.ee68972e559c2b052116eda28280677d@tools.ietf.org> X-Trac-Ticket-ID: 415 In-Reply-To: <060.ee68972e559c2b052116eda28280677d@tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [xml2rfc] #415 (Version 2 cli): show all validation errrors X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Aug 2019 10:41:36 -0000 #415: show all validation errrors Comment (by henrik@levkowetz.com): Replying to [ticket:415 miek@…]: > I looks like xml2rfc stops at the first validation error. This is somewhat annoying if you have a *really* long document, but making a validate becomes a game of whack a mole. This was (and is) the case for v2 input. For v3 input, it should not be the case; I've gone to quite a bit of effort changing that behaviour. Could you provide the input document that shows this, please? -- ----------------------------+---------------------------------- Reporter: miek@miek.nl | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.10.x Resolution: | Keywords: ----------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Wed Aug 21 10:04:10 2019 Return-Path: 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 17501120BF7 for ; Wed, 21 Aug 2019 10:04:08 -0700 (PDT) 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 IMmaOg9ElmW3 for ; Wed, 21 Aug 2019 10:04:06 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8140120CC4 for ; Wed, 21 Aug 2019 10:03:56 -0700 (PDT) Received: from localhost ([::1]:35445 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1i0U1c-00006j-Ci; Wed, 21 Aug 2019 10:03:56 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: julian.reschke@gmx.de X-Trac-Project: xml2rfc Date: Wed, 21 Aug 2019 17:03:56 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/416 Message-ID: <069.7f7a90309b511b0c6a175bef9f0a18fd@tools.ietf.org> X-Trac-Ticket-ID: 416 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: julian.reschke@gmx.de, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: [xml2rfc] #416 (Version_3_cli_html): cannot create non-ASCII characters in acknowledgments X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Aug 2019 17:04:08 -0000 #416: cannot create non-ASCII characters in acknowledgments Desired output as per . Actual output: "The following people contributed significant text to early versions of this draft: Patrik Faeltstroem (Faltstrom), 陈智昌 (William Chan), and Fred Baker." command line: --v3 --html -- -----------------------------------+-------------------- Reporter: julian.reschke@gmx.de | Owner: Type: defect | Status: new Priority: medium | Milestone: Component: Version_3_cli_html | Version: 2.23.* Keywords: | -----------------------------------+-------------------- Ticket URL: xml2rfc From nobody Wed Aug 21 10:06:36 2019 Return-Path: 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 D335F120CDC for ; Wed, 21 Aug 2019 10:06:33 -0700 (PDT) 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=unavailable 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 AdEtX_E1rCDM for ; Wed, 21 Aug 2019 10:06:33 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 BD1211208DB for ; Wed, 21 Aug 2019 10:06:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1566407169; bh=3lcftqSgT9rC8gM8SrKgxh3MiCE2Pv7JXM4BS+NnO0Q=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=IbL9KZn1clfqFmahC4eX2sPZ8cdiSRwthDBJ//L6TRvBhdkOD3ReYmwzGzFSqeAOO gcZU6xP1umESIYQpt8VHJ+r8ko0scD/QJA0uN3O5OPNzXpBUAyUx7qwkogokx4eOLE K/gIGDm7gRGwEI9bEleeDVBh3fasWiJ6zSh1+6qM= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.124] ([84.171.156.110]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0M4GND-1iIQU61o4B-00rpkH; Wed, 21 Aug 2019 19:06:09 +0200 To: Henrik Levkowetz , Tom Pusateri , XML2RFC Interest Group References: <4B64AFBF-B429-4C1E-8001-B4DEB6D59BFC@bangj.com> <244979f3-e3fc-506f-3859-671617b829fd@levkowetz.com> From: Julian Reschke Message-ID: <3e3e6575-d92c-e778-1144-c412fe99b1d4@gmx.de> Date: Wed, 21 Aug 2019 19:06:06 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <244979f3-e3fc-506f-3859-671617b829fd@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:PqeQVUo70XFrxejXbS14/P4KqPA7cp4eQuDZguiyu6u+Nf8rTWC BryzFKSEJbGqzci6mFAUrY8ccBvkyx8phssYcnV/6ju39GnjavUl5dRpjwhfxUhr8f8E+7j JIIqxojJub0eCRi1aGOfOFzjxdng/RbrXU2TZzwFdX4xZ2b6FGXgRr8SP6IFk7v5SM6r+Vs BNIAx53gB1DBrN0H64hnQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:7E3gMb/Xi3Y=:pPHcsDucUI6/91nG83e/Q5 ja5X7ARyw8rKk+ce1sYLzl4NhBj3/G+1XBxiUCbeZoB6YABd8jqECEbyPYzDmj5bjbjCj49CR SvkTsibtkuGqFhZhBb4KiC5Cx1lhMFKXwF6jFiE43/ZmhJ1zWs9qGWruFoxD/+ZgKl3dgOPFL qKz0CGLGTkk7GREKE9xoe9BPp8Nj74ojNYN9RLYdPrDL3oBO2hfWas2gRdfng2RUbA3i9hoXA wAL5OI6gL6zn8SV803Lpv5x0gX9S8s/hWjzZfcDSGXLbWyKHlUZxAvBAVq+tHtlOeOTjv9j8b ZS/9cGev3AQ/ep94G9QtLetVU2T+NOqa8/O7UpWxwalacqQPwAzihl51NhN8GXgcQjqP/Ruky H89qkoSGi9ysPAsOLGIIMXgo+nToUNPjkynS8Ygm1Roc8sMdxBbr3XOY5H/SZqehqL8uhtADs uRUBWo3Lf5rXFRMwiPywR2xe8O0UH/PdloOD5ylfANgI6/75bj3cVKykNPe4bC8IUCeQqomMc IEOSNLNfOE0IG9SRL9td6llfeZTIK0AWgkJFgZaf7OBzrMBP5nrrlvlU245y+S+YwdQ80jmJp vGhTtHHygXW89EfyjBs07ajkhb3XjUVsTsLQpmYlh/8B58tl8Uc+4gWQ0pgP+gBA/8iiDzo1Q A69xuV+rRyB/KWIp3zx7kS6yavMsB/Dlbed80YTBRBjjXj9yD2G+w886ZP76X1HE+jXUKT6yo LcbcH8NUrsv6yJ4l35qf0ZvROY2my5e3n7KYZii22FAg6/XKvlG5Fwox9yZOQyIa69SQcWINI UsE5ZpDNc06uu6SifiRYUwR8kN/+tbtACBBrZlCxXTjKdfqE77DMfoDdBb4CS1vy1AZwiAhBQ WDQNRhnlMOFGIFvWohks2sC0QHq2OgnjmCV8D7aqV4J96GBJTBWEx3F4ZxaW8r0leKx8ILwqS 30syP5Gl3CqH1Pok1SFvBzN+tGtloLq94h/gMjBal/hfUjS1jgSrPThsGDc/CH+MUW8engCmr 4EyURi4l/RRC7qs1CRs/KlOLgn7aDFjbqR4eNExheNE0VEYJaI0UtbD8p9MsAte910YZlAtJw eoivY3a0JwSpJ7a0Nfmlt2o6DZjMASJx+cPZfvjXIqmAyOmM7YJtQpT3KvLAsEOSr13xG/Y7n h8DzY= Archived-At: Subject: Re: [xml2rfc] new element help X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Aug 2019 17:06:34 -0000 On 05.08.2019 22:30, Henrik Levkowetz wrote: > Hi Tom, > > Short answer: This requires math support, and is not covered by the > functionality provided by the element, as the intention of that > element is to _always_ provide a rendering-agnostic codepoint value > in order to make the use of non-ASCII codepoints in protocol > specifications explicit, independent of the rendering format. > > Math support has been discussed; I think it's a good idea, and I have > a proposal, but it's not currently part of any specification. > > The best way, currently, to achieve what you want in a v3 XML source, > is to present the full equation as or . > ... Which reminds me that the current definition of is not in sync with RFC 7997; see . Best regards, Julian From nobody Wed Aug 21 10:21:59 2019 Return-Path: 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 0A29D120D0F for ; Wed, 21 Aug 2019 10:21:57 -0700 (PDT) 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 wcMfYzNakJDs for ; Wed, 21 Aug 2019 10:21:55 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85B8D120D2A for ; Wed, 21 Aug 2019 10:21:55 -0700 (PDT) Received: from localhost ([::1]:35724 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1i0UJ0-0000wk-Ux; Wed, 21 Aug 2019 10:21:54 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: julian.reschke@gmx.de X-Trac-Project: xml2rfc Date: Wed, 21 Aug 2019 17:21:54 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/416#comment:1 Message-ID: <084.e7af9373f5311544fd4ae0b26032e9e6@tools.ietf.org> References: <069.7f7a90309b511b0c6a175bef9f0a18fd@tools.ietf.org> X-Trac-Ticket-ID: 416 In-Reply-To: <069.7f7a90309b511b0c6a175bef9f0a18fd@tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: julian.reschke@gmx.de, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [xml2rfc] #416 (Version_3_cli_html): cannot create non-ASCII characters in acknowledgments X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Aug 2019 17:21:57 -0000 #416: cannot create non-ASCII characters in acknowledgments Changes (by julian.reschke@gmx.de): * version: 2.23.* => 2.24.* -- ------------------------------------+-------------------- Reporter: julian.reschke@gmx.de | Owner: Type: defect | Status: new Priority: medium | Milestone: Component: Version_3_cli_html | Version: 2.24.* Resolution: | Keywords: ------------------------------------+-------------------- Ticket URL: xml2rfc From nobody Thu Aug 22 05:29:21 2019 Return-Path: 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 B625E1200E9 for ; Thu, 22 Aug 2019 05:29:19 -0700 (PDT) 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 Ckl_N7CB1uGo for ; Thu, 22 Aug 2019 05:29:18 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE7D412003E for ; Thu, 22 Aug 2019 05:29:17 -0700 (PDT) Received: from localhost ([::1]:57613 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1i0mDN-0007os-7N; Thu, 22 Aug 2019 05:29:17 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com, julian.reschke@gmx.de X-Trac-Project: xml2rfc Date: Thu, 22 Aug 2019 12:29:17 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/417 Message-ID: <069.c6079aa1731c1e2f1bf2249638029f43@tools.ietf.org> X-Trac-Ticket-ID: 417 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, julian.reschke@gmx.de, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: [xml2rfc] #417 (Version 2 cli): stack trace for deprecated element X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Aug 2019 12:29:20 -0000 #417: stack trace for deprecated element (for xml2rfc --v3) (don't take the input file seriously; it's just a work-in-progress artefact of format conversios; however xml2rfc should not fail the way it does) {{{ c: '' Traceback (most recent call last): File "/bin/xml2rfc", line 10, in sys.exit(main()) File "/usr/lib/python2.7/site-packages/xml2rfc/run.py", line 560, in main writer.write(filename) File "/usr/lib/python2.7/site-packages/xml2rfc/writers/text.py", line 229, in write lines = self.render(self.root, width=72, joiners=joiners) File "/usr/lib/python2.7/site-packages/xml2rfc/writers/text.py", line 272, in render res = func(e, width, **kwargs) File "/usr/lib/python2.7/site-packages/xml2rfc/writers/text.py", line 2852, in render_rfc lines = self.ljoin(lines, c, width, **kwargs) File "/usr/lib/python2.7/site-packages/xml2rfc/writers/text.py", line 450, in ljoin res = mklines(self.render(e, width, **kwargs), e) File "/usr/lib/python2.7/site-packages/xml2rfc/writers/text.py", line 272, in render res = func(e, width, **kwargs) File "/usr/lib/python2.7/site-packages/xml2rfc/writers/text.py", line 2039, in render_middle lines = self.ljoin(lines, c, width, **kwargs) File "/usr/lib/python2.7/site-packages/xml2rfc/writers/text.py", line 450, in ljoin res = mklines(self.render(e, width, **kwargs), e) File "/usr/lib/python2.7/site-packages/xml2rfc/writers/text.py", line 272, in render res = func(e, width, **kwargs) File "/usr/lib/python2.7/site-packages/xml2rfc/writers/text.py", line 3120, in render_section lines = self.ljoin(lines, c, width, **kwargs) File "/usr/lib/python2.7/site-packages/xml2rfc/writers/text.py", line 450, in ljoin res = mklines(self.render(e, width, **kwargs), e) File "/usr/lib/python2.7/site-packages/xml2rfc/writers/text.py", line 272, in render res = func(e, width, **kwargs) File "/usr/lib/python2.7/site-packages/xml2rfc/writers/text.py", line 3488, in render_t text = fill(self.inner_text_renderer(e), width=width, **kwargs) File "/usr/lib/python2.7/site-packages/xml2rfc/writers/text.py", line 508, in inner_text_renderer text += self.render(c, width, **kwargs) File "/usr/lib/python2.7/site-packages/xml2rfc/writers/text.py", line 268, in render self.warn(e, "Was asked to render a deprecated element: <%s>", (e.tag, )) TypeError: warn() takes exactly 3 arguments (4 given) }}} -- -----------------------------------+---------------------------------- Reporter: julian.reschke@gmx.de | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.24.* Keywords: | -----------------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Thu Aug 22 14:28:23 2019 Return-Path: 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 8665312012A for ; Thu, 22 Aug 2019 14:28:17 -0700 (PDT) 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 Otvws8YgftDQ for ; Thu, 22 Aug 2019 14:28:15 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0800812029C for ; Thu, 22 Aug 2019 14:28:15 -0700 (PDT) Received: from localhost ([::1]:44493 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1i0ucw-0006Ut-Lr; Thu, 22 Aug 2019 14:28:14 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com X-Trac-Project: xml2rfc Date: Thu, 22 Aug 2019 21:28:14 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: /ticket/417#comment:1 Message-ID: <084.9d19c3f98a33bd9af44f2eac98548aa8@tools.ietf.org> References: <069.c6079aa1731c1e2f1bf2249638029f43@tools.ietf.org> X-Trac-Ticket-ID: 417 In-Reply-To: <069.c6079aa1731c1e2f1bf2249638029f43@tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [xml2rfc] #417 (Version 2 cli): stack trace for deprecated element X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Aug 2019 21:28:18 -0000 #417: stack trace for deprecated element Changes (by henrik@levkowetz.com): * status: new => closed * resolution: => fixed Comment: Fixed in [3227]: Fixed a string formatting error. Fixes issue #417. -- ------------------------------------+---------------------------------- Reporter: julian.reschke@gmx.de | Owner: henrik@levkowetz.com Type: defect | Status: closed Priority: medium | Milestone: Component: Version 2 cli | Version: 2.24.* Resolution: fixed | Keywords: ------------------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Fri Aug 23 08:26:14 2019 Return-Path: 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 B1E00120074 for ; Fri, 23 Aug 2019 08:26:12 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 VPyDJbLH2CUU for ; Fri, 23 Aug 2019 08:26:11 -0700 (PDT) Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA6E312004D for ; Fri, 23 Aug 2019 08:26:10 -0700 (PDT) Received: from [192.168.1.17] (ppp-94-69-228-254.home.otenet.gr [94.69.228.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 02CC1853ED; Fri, 23 Aug 2019 17:26:08 +0200 (CEST) To: xml2rfc@ietf.org From: Fernando Gont Openpgp: preference=signencrypt Autocrypt: addr=fernando@gont.com.ar; prefer-encrypt=mutual; keydata= mQINBE5so2gBEACzBQBLUy8nzgAzSZn6ViXT6TmZBFNYNqTpPRvTVtUqF6+tkI+IEd9N2E8p pXUXCd0W4dkxz6o7pagnK63m4QSueggvp881RVVHOF8oTSHOdnGxLfLeLNJFKE1FOutU3vod GK/wG/Fwzkv9MebdXpMlLV8nnJuAt66XGl/lU1JrNfrKO4SoYQi4TsB/waUQcygh7OR/PEO0 EttiU8kZUbZNv58WH+PAj/rdZCrgUSiGXiWUQQKShqKnJxLuAcTcg5YRwL8se/V6ciW0QR9i /sr52gSmLLbW5N3hAoO+nv1V/9SjJAUvzXu43k8sua/XlCXkqU7uLj41CRR72JeUZ4DQsYfP LfNPC98ZGTVxbWbFtLXxpzzDDT8i3uo7w1LJ2Ij/d5ezcARqw01HGljWWxnidUrjbTpxkJ9X EllcsH94mer728j/HKzC9OcTuz6WUBP3Crgl6Q47gY5ZIiF0lsmd9/wxbaq5NiJ+lGuBRZrD v0dQx9KmyI0/pH2AF8cW897/6ypvcyD/1/11CJcN+uAGIrklwJlVpRSbKbFtGC6In592lhu7 wnK8cgyP5cTU+vva9+g6P1wehi4bylXdlKc6mMphbtSA+T3WBNP557+mh3L62l4pGaEGidcZ DLYT2Ud18eAJmxU3HnM8P3iZZgeoK7oqgb53/eg96vkONXNIOwARAQABtCVGZXJuYW5kbyBH b250IDxmZ29udEBzaTZuZXR3b3Jrcy5jb20+iQJBBBMBAgArAhsjBQkSzAMABgsJCAcDAgYV CAIJCgsEFgIDAQIeAQIXgAUCTmylpQIZAQAKCRCuJQ1VHU50kv7wD/9fuNtTfxSLk3B3Hs3p ixTy8YXVjdkVwWlnJjFd7BOWmg7sI+LDhpjGfT6+ddOiwkumnvUZpObodj4ysH0i8c7P4C5t F9yu7WjklSlrB5Rth2CGChg5bKt541z2WHkFFxys9qBLmCSYDeKQkzLqhCjIUJizY2kOJ2GI MnSFDzJjhSFEh//oW830Y8fel1xnf/NVF+lBVtRMtMOfoWUqDjvP3sJ1G4zgkDCnF0CfncLx +hq2Mv26Uq9OTzvLH9aSQQ/f067BOkKAJKsfHdborX4E96ISTz57/4xECRSMr5dVsKVm4Y// uVIsb+L5z+a32FaiBZIAKDgnJO7Z8j6CV5e5yfuBTtX52Yi9HjYYqnYJGSDxYd6igD4bWu+7 xmJPHjkdqZgGV6dQIgiUfqkU+s5Cv350vK48CMaT/ZLo2BdsMhWsmaHmb+waePUMyq6E4E9x 9Js+EJb9ZiCfxS9exgieZQpet1L36IvhiwByvkQM009ywfa30JeMOltUtfLi5V06WQWsTzPL 5C+4cpkguSuAJVDTctjCA0moIeVDOpJ8WH9voQ4IeWapQnX35OIoj1jGJqqYdx65gc1ygbyx b8vw+pJ9E5GLse5TQnYifOWpXzX9053dtbwp/2OVhU4KLlzfCPCEsoTyfu9nIZxdI2PMwiL5 M85BfjX4NmwBLmPGoLkCDQRObKNoARAAqqXCkr250BchRDmi+05F5UQFgylUh10XTAJxBeaQ UNtdxZiZRm6jgomSrqeYtricM9t9K0qb4X2ZXmAMW8o8AYW3RrQHTjcBwMnAKzUIEXXWaLfG cid/ygmvWzIHgMDQKP+MUq1AGQrnvt/MRLvZLyczAV1RTXS58qNaxtaSpc3K/yrDozh/a4pu WcUsVvIkzyx43sqcwamDSBb6U8JFoZizuLXiARLLASgyHrrCedNIZdWSx0z0iHEpZIelA2ih AGLiSMtmtikVEyrJICgO81DkKNCbBbPg+7fi23V6M24+3syHk3IdQibTtBMxinIPyLFF0byJ aGm0fmjefhnmVJyCIl/FDkCHprVhTme57G2/WdoGnUvnT7mcwDRb8XY5nNRkOJsqqLPemKjz kx8mXdQbunXtX9bKyVgd1gIl+LLsxbdzRCch773UBVoortPdK3kMyLtZ4uMeDX3comjx+6VL bztUdJ1Zc9/njwVG8fgmQ+0Kj5+bzQfUY+MmX0HTXIx3B4R1I1a8QoOwi1N+iZNdewV5Zfq+ 29NlQLnVPjCRCKbaz9k6RJ2oIti55YUI6zSsL3lmlOXsRbXN5bRswFczkNSCJxJMlDiyAUIC WOay7ymzvgzPa+BY/mYn94vRaurDQ4/ljOfj6oqgfjts+dJev4Jj89vp8MQI3KJpZPEAEQEA AYkCJQQYAQIADwUCTmyjaAIbDAUJEswDAAAKCRCuJQ1VHU50km4xEACho45PZrUjY4Zl2opR DFNo5a6roTOPpgwO9PcBb3I5F8yX2Dnew+9OhgWXbBhAFq4DCx+9Gjs43Bn60qbZTDbLGJ/m 8N4PwEiq0e5MKceYcbetEdEUWhm5L6psU9ZZ82GR3UGxPXYe+oifEoJjOXQ39avf9S8p3yKP Diil0E79rn7LbJjMcgMLyjFg9SDoJ6pHLtniJoDhEAaSSgeV7Y745+gyMIdtQmrFHfqrFdjq D6G0HE+Z68ywc5KN67YxhvhBmSycs1ZSKAXv1zLDlXdmjHDHkU3xMcB+RkuiTba8yRFYwb/n j62CC4NhFTuIKOc4ta3dJsyXTGh/hO9UjWUnmAGfd0fnzTBZF8Qlnw/8ftx5lt4/O+eqY1EN RITScnPzXE/wMOlTtdkddQ+QN6xt6jyR2XtAIi7aAFHypIqA3lLI9hF9x+lj4UQ2yA9LqpoX 6URpPOd13JhAyDe47cwsP1u9Y+OBvQTVLSvw7Liu2b4KjqL4lx++VdBi7dXsjJ6kjIRjI6Lb WVpxe8LumMCuVDepTafBZ49gr7Fgc4F9ZSCo6ChgQNLn6WDzIkqFX+42KuHz90AHWhuW+KZR 1aJylERWeTcMCGUSBptd48KniWmD6kPKpzwoMkJtEXTuO2lVuborxzwuqOTNuYg9lWDl7zKt wPI9brGzquUHy4qRrA== Message-ID: <8af742c9-8273-0d9a-e776-9c8e763ffd2e@gont.com.ar> Date: Fri, 23 Aug 2019 18:26:03 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Archived-At: Subject: [xml2rfc] IRTF boilerplate? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2019 15:26:13 -0000 Folks, I'm authoring an IRTF draft. I've set: But it seems the output is the same as if I don't set this variable (and hence it takes de default value of "IETF"). Is this the intented result? Or should bol¡ilerplates for IRTF documents be different from IETF documents? Thanks! Cheers, -- Fernando Gont e-mail: fernando@gont.com.ar || fgont@si6networks.com PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1 From nobody Fri Aug 23 08:47:11 2019 Return-Path: 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 87CE7120105 for ; Fri, 23 Aug 2019 08:47:10 -0700 (PDT) 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 hohXsYPwl1-q for ; Fri, 23 Aug 2019 08:47:09 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3870812008A for ; Fri, 23 Aug 2019 08:47:09 -0700 (PDT) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:61336 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1i1BmN-0007rW-DR; Fri, 23 Aug 2019 08:47:07 -0700 To: Fernando Gont , xml2rfc@ietf.org References: <8af742c9-8273-0d9a-e776-9c8e763ffd2e@gont.com.ar> From: Henrik Levkowetz Message-ID: <68d11ca7-0644-07d4-4824-a179a70869ec@levkowetz.com> Date: Fri, 23 Aug 2019 17:46:58 +0200 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: <8af742c9-8273-0d9a-e776-9c8e763ffd2e@gont.com.ar> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="w3edIQFiDhKixqUwb8AtjBct0eBCg6Sxq" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: xml2rfc@ietf.org, fernando@gont.com.ar 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: Subject: Re: [xml2rfc] IRTF boilerplate? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2019 15:47:10 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --w3edIQFiDhKixqUwb8AtjBct0eBCg6Sxq Content-Type: multipart/mixed; boundary="1Sbjg8Qe34As9JAtns9g8FPXIQlCSCg6A"; protected-headers="v1" From: Henrik Levkowetz To: Fernando Gont , xml2rfc@ietf.org Message-ID: <68d11ca7-0644-07d4-4824-a179a70869ec@levkowetz.com> Subject: Re: [xml2rfc] IRTF boilerplate? References: <8af742c9-8273-0d9a-e776-9c8e763ffd2e@gont.com.ar> In-Reply-To: <8af742c9-8273-0d9a-e776-9c8e763ffd2e@gont.com.ar> --1Sbjg8Qe34As9JAtns9g8FPXIQlCSCg6A Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Fernando, On 2019-08-23 17:26, Fernando Gont wrote: > Folks, >=20 > I'm authoring an IRTF draft. I've set: > >=20 > But it seems the output is the same as if I don't set this variable (an= d > hence it takes de default value of "IETF"). >=20 > Is this the intented result? Or should bol=C2=A1ilerplates for IRTF doc= uments > be different from IETF documents? In the v2 formatters, I think the only difference is in the stream name, the top left of the front page (if no group name has been set), and the consensus text. In the v3 formatters, the boilerplate should also change= to mention IRTF instead of IETF. If this doesn't match what you're seeing, please provide details of the text you'd expect to be different, and the input XML file for debugging. Best regards, Henrik --1Sbjg8Qe34As9JAtns9g8FPXIQlCSCg6A-- --w3edIQFiDhKixqUwb8AtjBct0eBCg6Sxq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl1gCnIACgkQTptXS4+7 Fxrm6w//eZwwWTL+Z0eVxfH06JHI1nOD9ljtRRs6fnFYBi51HFZQcZPivl6VsuMh fPKae8eaAWe0W4sAcT/FrHqK5Bv6UuWcrE8x6Q46Qp0LNOiLwZ8qhjkMAW9lW9ru FLR4UO83ULFBA38EB5PMi2BFDCOu+smWNHxpYoeBAFHqiHaz66rldQ22vi94odpT 0Z9Y16MMb+6PRWC01yimCyjxWwGWpG7z574bbqCIAuxvT+a99R87AsMJC/Qq4jsX mZ6LRlGE5a+lU6PHJQs5LT+vo9qMonTWxDaUxlzh7F128CTAsGKkGWz07ohcjT0t ianauDBSSa+o3o8rgexFbqKfN58M4Oex6aWIywbS2ytdNM4fEND0WJvxd7h9KgVW LymlFsZpMXnv+1Auqfc+XcQNEBHbkzJgHdrwV/+czIZYU5qWyhjtJaFiJfc5acmk oRr+l/aBRY+9eHfoErifueV2DadaiXLxyJSatD8BKXQUuHJhq/isXEveEd7zK9Ma XR++3vdKKnR7eI7Qa1mlshM+Qhyzj4V8CDXDIp9pRXPC//Tt0rxD0JzgibG1JOlu RtbnTB4boPhNci/ZILtbgKNwl6kI41J/PXh/05Sf2gEjUxIqQBqYTcPdvfSMslaK iDvrfO5aD0a/GkCzMgvRcrNIEJTv/bL7sJodON56x2Y3glFUuEs= =CEfU -----END PGP SIGNATURE----- --w3edIQFiDhKixqUwb8AtjBct0eBCg6Sxq-- From nobody Fri Aug 23 09:35:20 2019 Return-Path: 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 7F822120025 for ; Fri, 23 Aug 2019 09:35:18 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 zu7Ilhvch8e3 for ; Fri, 23 Aug 2019 09:35:16 -0700 (PDT) Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B825120020 for ; Fri, 23 Aug 2019 09:35:15 -0700 (PDT) Received: from [192.168.1.17] (ppp-94-69-228-254.home.otenet.gr [94.69.228.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id B672285FC4; Fri, 23 Aug 2019 18:35:13 +0200 (CEST) To: Henrik Levkowetz , xml2rfc@ietf.org References: <8af742c9-8273-0d9a-e776-9c8e763ffd2e@gont.com.ar> <68d11ca7-0644-07d4-4824-a179a70869ec@levkowetz.com> From: Fernando Gont Openpgp: preference=signencrypt Autocrypt: addr=fernando@gont.com.ar; prefer-encrypt=mutual; keydata= mQINBE5so2gBEACzBQBLUy8nzgAzSZn6ViXT6TmZBFNYNqTpPRvTVtUqF6+tkI+IEd9N2E8p pXUXCd0W4dkxz6o7pagnK63m4QSueggvp881RVVHOF8oTSHOdnGxLfLeLNJFKE1FOutU3vod GK/wG/Fwzkv9MebdXpMlLV8nnJuAt66XGl/lU1JrNfrKO4SoYQi4TsB/waUQcygh7OR/PEO0 EttiU8kZUbZNv58WH+PAj/rdZCrgUSiGXiWUQQKShqKnJxLuAcTcg5YRwL8se/V6ciW0QR9i /sr52gSmLLbW5N3hAoO+nv1V/9SjJAUvzXu43k8sua/XlCXkqU7uLj41CRR72JeUZ4DQsYfP LfNPC98ZGTVxbWbFtLXxpzzDDT8i3uo7w1LJ2Ij/d5ezcARqw01HGljWWxnidUrjbTpxkJ9X EllcsH94mer728j/HKzC9OcTuz6WUBP3Crgl6Q47gY5ZIiF0lsmd9/wxbaq5NiJ+lGuBRZrD v0dQx9KmyI0/pH2AF8cW897/6ypvcyD/1/11CJcN+uAGIrklwJlVpRSbKbFtGC6In592lhu7 wnK8cgyP5cTU+vva9+g6P1wehi4bylXdlKc6mMphbtSA+T3WBNP557+mh3L62l4pGaEGidcZ DLYT2Ud18eAJmxU3HnM8P3iZZgeoK7oqgb53/eg96vkONXNIOwARAQABtCVGZXJuYW5kbyBH b250IDxmZ29udEBzaTZuZXR3b3Jrcy5jb20+iQJBBBMBAgArAhsjBQkSzAMABgsJCAcDAgYV CAIJCgsEFgIDAQIeAQIXgAUCTmylpQIZAQAKCRCuJQ1VHU50kv7wD/9fuNtTfxSLk3B3Hs3p ixTy8YXVjdkVwWlnJjFd7BOWmg7sI+LDhpjGfT6+ddOiwkumnvUZpObodj4ysH0i8c7P4C5t F9yu7WjklSlrB5Rth2CGChg5bKt541z2WHkFFxys9qBLmCSYDeKQkzLqhCjIUJizY2kOJ2GI MnSFDzJjhSFEh//oW830Y8fel1xnf/NVF+lBVtRMtMOfoWUqDjvP3sJ1G4zgkDCnF0CfncLx +hq2Mv26Uq9OTzvLH9aSQQ/f067BOkKAJKsfHdborX4E96ISTz57/4xECRSMr5dVsKVm4Y// uVIsb+L5z+a32FaiBZIAKDgnJO7Z8j6CV5e5yfuBTtX52Yi9HjYYqnYJGSDxYd6igD4bWu+7 xmJPHjkdqZgGV6dQIgiUfqkU+s5Cv350vK48CMaT/ZLo2BdsMhWsmaHmb+waePUMyq6E4E9x 9Js+EJb9ZiCfxS9exgieZQpet1L36IvhiwByvkQM009ywfa30JeMOltUtfLi5V06WQWsTzPL 5C+4cpkguSuAJVDTctjCA0moIeVDOpJ8WH9voQ4IeWapQnX35OIoj1jGJqqYdx65gc1ygbyx b8vw+pJ9E5GLse5TQnYifOWpXzX9053dtbwp/2OVhU4KLlzfCPCEsoTyfu9nIZxdI2PMwiL5 M85BfjX4NmwBLmPGoLkCDQRObKNoARAAqqXCkr250BchRDmi+05F5UQFgylUh10XTAJxBeaQ UNtdxZiZRm6jgomSrqeYtricM9t9K0qb4X2ZXmAMW8o8AYW3RrQHTjcBwMnAKzUIEXXWaLfG cid/ygmvWzIHgMDQKP+MUq1AGQrnvt/MRLvZLyczAV1RTXS58qNaxtaSpc3K/yrDozh/a4pu WcUsVvIkzyx43sqcwamDSBb6U8JFoZizuLXiARLLASgyHrrCedNIZdWSx0z0iHEpZIelA2ih AGLiSMtmtikVEyrJICgO81DkKNCbBbPg+7fi23V6M24+3syHk3IdQibTtBMxinIPyLFF0byJ aGm0fmjefhnmVJyCIl/FDkCHprVhTme57G2/WdoGnUvnT7mcwDRb8XY5nNRkOJsqqLPemKjz kx8mXdQbunXtX9bKyVgd1gIl+LLsxbdzRCch773UBVoortPdK3kMyLtZ4uMeDX3comjx+6VL bztUdJ1Zc9/njwVG8fgmQ+0Kj5+bzQfUY+MmX0HTXIx3B4R1I1a8QoOwi1N+iZNdewV5Zfq+ 29NlQLnVPjCRCKbaz9k6RJ2oIti55YUI6zSsL3lmlOXsRbXN5bRswFczkNSCJxJMlDiyAUIC WOay7ymzvgzPa+BY/mYn94vRaurDQ4/ljOfj6oqgfjts+dJev4Jj89vp8MQI3KJpZPEAEQEA AYkCJQQYAQIADwUCTmyjaAIbDAUJEswDAAAKCRCuJQ1VHU50km4xEACho45PZrUjY4Zl2opR DFNo5a6roTOPpgwO9PcBb3I5F8yX2Dnew+9OhgWXbBhAFq4DCx+9Gjs43Bn60qbZTDbLGJ/m 8N4PwEiq0e5MKceYcbetEdEUWhm5L6psU9ZZ82GR3UGxPXYe+oifEoJjOXQ39avf9S8p3yKP Diil0E79rn7LbJjMcgMLyjFg9SDoJ6pHLtniJoDhEAaSSgeV7Y745+gyMIdtQmrFHfqrFdjq D6G0HE+Z68ywc5KN67YxhvhBmSycs1ZSKAXv1zLDlXdmjHDHkU3xMcB+RkuiTba8yRFYwb/n j62CC4NhFTuIKOc4ta3dJsyXTGh/hO9UjWUnmAGfd0fnzTBZF8Qlnw/8ftx5lt4/O+eqY1EN RITScnPzXE/wMOlTtdkddQ+QN6xt6jyR2XtAIi7aAFHypIqA3lLI9hF9x+lj4UQ2yA9LqpoX 6URpPOd13JhAyDe47cwsP1u9Y+OBvQTVLSvw7Liu2b4KjqL4lx++VdBi7dXsjJ6kjIRjI6Lb WVpxe8LumMCuVDepTafBZ49gr7Fgc4F9ZSCo6ChgQNLn6WDzIkqFX+42KuHz90AHWhuW+KZR 1aJylERWeTcMCGUSBptd48KniWmD6kPKpzwoMkJtEXTuO2lVuborxzwuqOTNuYg9lWDl7zKt wPI9brGzquUHy4qRrA== Message-ID: Date: Fri, 23 Aug 2019 19:27:27 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <68d11ca7-0644-07d4-4824-a179a70869ec@levkowetz.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [xml2rfc] IRTF boilerplate? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2019 16:35:18 -0000 On 23/8/19 18:46, Henrik Levkowetz wrote: > Hi Fernando, > > On 2019-08-23 17:26, Fernando Gont wrote: >> Folks, >> >> I'm authoring an IRTF draft. I've set: >> >> >> But it seems the output is the same as if I don't set this variable (and >> hence it takes de default value of "IETF"). >> >> Is this the intented result? Or should bol¡ilerplates for IRTF documents >> be different from IETF documents? > > In the v2 formatters, FWIW, I'm using https://xml2rfc.tools.ietf.org/ , which seems to be a v2 formatter. I've set: [...] Internet Research Task Force (IRTF) If I s/IRTF/IETF/, I get the same. > I think the only difference is in the stream name, > the top left of the front page (if no group name has been set), and the > consensus text. I assume by 'group' you mean 'workgroup'? (which would explain things here). > In the v3 formatters, the boilerplate should also change > to mention IRTF instead of IETF. Is a v3 formatter online? Thanks! (for your prompt answer, but also for your usual work!) Cheers, -- Fernando Gont e-mail: fernando@gont.com.ar || fgont@si6networks.com PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1 From nobody Fri Aug 23 09:53:55 2019 Return-Path: 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 BDB30120025 for ; Fri, 23 Aug 2019 09:53:53 -0700 (PDT) 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 Wpi4Of1nKRem for ; Fri, 23 Aug 2019 09:53:51 -0700 (PDT) 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 68FCD120020 for ; Fri, 23 Aug 2019 09:53:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1566579212; bh=+FEHH0En9M9oej5FFmhg6uYiBWcyz8FPzEufmdfAls4=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=KeqtGF7JKBENN63SkAhFGoqv8iaH+IkuwTShzUKHAXgFGKztP6jsUrQwtRZjosfcG /iwdhL9TXIFbg7zjwbopDRmUW629E0+R6RTLPg1bMQSah2zvWshMrxPf9QOwkjUb76 Qaw1uKdpdBzcpDi2EWc7OO+XrTnUvbtPyID5U6oc= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.124] ([84.171.157.224]) by mail.gmx.com (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MjjCL-1iUn952IIN-00lFGg; Fri, 23 Aug 2019 18:53:32 +0200 To: Fernando Gont , Henrik Levkowetz , xml2rfc@ietf.org References: <8af742c9-8273-0d9a-e776-9c8e763ffd2e@gont.com.ar> <68d11ca7-0644-07d4-4824-a179a70869ec@levkowetz.com> From: Julian Reschke Message-ID: <09028e94-8c27-2fad-f440-6c8ce4819d7a@gmx.de> Date: Fri, 23 Aug 2019 18:53:29 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:REug7XWfhDQdKoveMsrgTfdFrALJ3HU2sqSSM2UtuTJx0FILEys VcRpr9lkws53OeP+fEFbdISdb0C8s88DMRlbFbEQ48ZH5I3hxNH9dpNY3rwXlO0E5LR8La2 JudKu7de9BcpjHFKllSndUBWTLyZmefycIKiBe1C377cwF1TRsdE9n4324lK42MFhBo/BlY wIjIZPt3N2tAkq2h8E80Q== X-UI-Out-Filterresults: notjunk:1;V03:K0:ivS6xhmVhBs=:X1wILZQWYD5KeFs8TgoWsr ypeQmnpg6b0XIIcU2nd7Vszvao2K8Oc1L46pVHaxOOMabmYbOCKH7/3snsCI7SpCYMD/2dSip VjywkHjwV146DANrvvAYz8VvYuB+5QZUJO/O6NufTTLqr3TyaKkZQU4SB5+VMegHtEem4DvM5 m+50NuxZ9hFdThf2IOCbtdmrr5pxqjShzYMjOpVX0rL6Q15Xm1XUzZ4NYCiwKqezpXjjZDS+V BHuzDZFgY8TbNpzYn6PWHMxU5+vQb8cRTfSgcRTSd/aAwvMjcn+r3cUFSlv+r2OAc6FyHnQmp LgywPAfJ+ph1N5AMTS9tPiRQi00TZfbRLPI+knYsVYbyg19w0eug+RcCo1oOjgARhE5bIg+/z PmZ25QANzmWt3eIhLWW2nCG5dLrRAAJs4xhmcNwQQiXdAcMq42VVFDWaI1Az+u/UZ+ybaZGg+ sXsTs9NcK8AppzQe5M6R3aIqd+QvWZDEHEnR9C5fdnK4E1hau1DiQmc5VztTZyvhYBJdc/7N7 yDzFX5N9uPuJTu4byxOrJJiaeZklDTRy1pfNjxkODlvbN+zA7TW6AHDe9e10NVEa5n4z/zcCd zaeoQ16qliU427ntPqhOEKdEpUrhW+H5P0Slaz4DpVIAkefxc7KjoABjpLh0dls8cGR9ob0Hl P2khGxOjsTmY2g3oYLKbnF3RFeNM/IZrqnMC5H0lfK3eRfKbZbtkEJ333t65ZvaMU/CkBaoTi ilDE9DyraG+/Ws6jJEzmcfwJZ6Mi/pBY0JcmrbT7iooapThponLuYDR+cWu7O6qxSKqlAqbiV xtd23S/LXnlho2nuF5gS/oAR2OKMZohd7j4qkYi8QoZSf6GPXbkduhROhhKIrImzoYl6S+DLc 19+Z5SS8oliycwg2qnj2kkrTX1rtIJVEbn3LEJhjz4AqKFfWrO2rtIg4x+EuGjbZdr+t4r5dS 25Yt1x9A5ylYEoYB0dW/gXYO5s8Y0LU+bhW143pK34bcaRh3YkofEFz6vruPnwaj9oOQIjMiN NxIkKlENf+OK0ChOwqj4cL0YRuOrJc61V3z/0rPi80ZyikWxfrjDLHWdBBcugFU8VtJRvan7q 5DQXyF+h2+JnRQSgG6G0YAvstZnXPXW5DmToi3bj5+uLnrGrnN68rRHCQget2ijEQad+Lx6Kq //oy4= Archived-At: Subject: Re: [xml2rfc] IRTF boilerplate? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2019 16:53:54 -0000 On 23.08.2019 18:27, Fernando Gont wrote: > On 23/8/19 18:46, Henrik Levkowetz wrote: >> Hi Fernando, >> >> On 2019-08-23 17:26, Fernando Gont wrote: >>> Folks, >>> >>> I'm authoring an IRTF draft. I've set: >>> >>> >>> But it seems the output is the same as if I don't set this variable (a= nd >>> hence it takes de default value of "IETF"). >>> >>> Is this the intented result? Or should bol=C2=A1ilerplates for IRTF do= cuments >>> be different from IETF documents? >> >> In the v2 formatters, > > FWIW, I'm using https://xml2rfc.tools.ietf.org/ , which seems to be a v2 > formatter. > > I've set: > > [...] > > Internet Research Task Force (IRTF) > > > If I s/IRTF/IETF/, I get the same. > ... SubmissionType is an attribute on the element, not a processing instruction. See . Best regards, Julian From nobody Sat Aug 24 23:07:27 2019 Return-Path: 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 68F851200EF for ; Sat, 24 Aug 2019 23:07:25 -0700 (PDT) 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 Fvuhg12Fy-Pf for ; Sat, 24 Aug 2019 23:07:24 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C73B120019 for ; Sat, 24 Aug 2019 23:07:24 -0700 (PDT) Received: from localhost ([::1]:37623 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1i1lgQ-00015O-7X; Sat, 24 Aug 2019 23:07:22 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com, julian.reschke@gmx.de X-Trac-Project: xml2rfc Date: Sun, 25 Aug 2019 06:07:22 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/418 Message-ID: <069.96cf890ca45cceab7afdcd494a0f664c@tools.ietf.org> X-Trac-Ticket-ID: 418 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, julian.reschke@gmx.de, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: [xml2rfc] #418 (Version 2 cli): weird index generation X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Aug 2019 06:07:26 -0000 #418: weird index generation - duplicate entries - missing linking (hard to describe, please see yourself) -- -----------------------------------+---------------------------------- Reporter: julian.reschke@gmx.de | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.24.* Keywords: | -----------------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Sun Aug 25 00:08:28 2019 Return-Path: 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 8ED63120112 for ; Sun, 25 Aug 2019 00:08:27 -0700 (PDT) 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 kjSob6a42914 for ; Sun, 25 Aug 2019 00:08:26 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F173A120024 for ; Sun, 25 Aug 2019 00:08:25 -0700 (PDT) Received: from localhost ([::1]:38605 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1i1mdU-0001Mx-1f; Sun, 25 Aug 2019 00:08:24 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com, miek@miek.nl X-Trac-Project: xml2rfc Date: Sun, 25 Aug 2019 07:08:22 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/418#comment:1 Message-ID: <084.84dd703d013121315ebc062efde0f634@tools.ietf.org> References: <069.96cf890ca45cceab7afdcd494a0f664c@tools.ietf.org> X-Trac-Ticket-ID: 418 In-Reply-To: <069.96cf890ca45cceab7afdcd494a0f664c@tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, miek@miek.nl, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [xml2rfc] #418 (Version 2 cli): weird index generation X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Aug 2019 07:08:27 -0000 #418: weird index generation Comment (by miek@miek.nl): Now that we're paginating in the text format, shouldn't we also re-add the pages back to the indices? (sorry unrelated to this issue - just ran xml2rfc 2.24.0, --v3 --text) on this draft. Index looks strange indeed. -- ------------------------------------+---------------------------------- Reporter: julian.reschke@gmx.de | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.24.* Resolution: | Keywords: ------------------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Sun Aug 25 13:12:17 2019 Return-Path: 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 913E81200B1 for ; Sun, 25 Aug 2019 13:12:15 -0700 (PDT) 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 MHgHAzSojEa7 for ; Sun, 25 Aug 2019 13:12:14 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18C4C12010C for ; Sun, 25 Aug 2019 13:12:14 -0700 (PDT) Received: from localhost ([::1]:41156 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1i1ys0-0004nC-Ai; Sun, 25 Aug 2019 13:12:12 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com, julian.reschke@gmx.de X-Trac-Project: xml2rfc Date: Sun, 25 Aug 2019 20:12:12 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/419 Message-ID: <069.d5d30ff1a5db56e9a2891f7905ff7012@tools.ietf.org> X-Trac-Ticket-ID: 419 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, julian.reschke@gmx.de, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: [xml2rfc] #419 (Version 2 cli): Error: Invalid attribute displayFormat for element xref X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Aug 2019 20:12:16 -0000 #419: Error: Invalid attribute displayFormat for element xref ...for something that seems to be valid to me. -- -----------------------------------+---------------------------------- Reporter: julian.reschke@gmx.de | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.24.* Keywords: | -----------------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Sun Aug 25 20:52:05 2019 Return-Path: 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 12BF51200A4 for ; Sun, 25 Aug 2019 20:52:04 -0700 (PDT) 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 gTIIeearpjNC for ; Sun, 25 Aug 2019 20:52:02 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 552E812080D for ; Sun, 25 Aug 2019 20:52:02 -0700 (PDT) Received: from localhost ([::1]:54827 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1i262z-0004aL-KB; Sun, 25 Aug 2019 20:52:01 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com, julian.reschke@gmx.de X-Trac-Project: xml2rfc Date: Mon, 26 Aug 2019 03:52:01 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/419#comment:1 Message-ID: <084.9ef00e8d8e4814cc153297d9917392de@tools.ietf.org> References: <069.d5d30ff1a5db56e9a2891f7905ff7012@tools.ietf.org> X-Trac-Ticket-ID: 419 In-Reply-To: <069.d5d30ff1a5db56e9a2891f7905ff7012@tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, julian.reschke@gmx.de, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [xml2rfc] #419 (Version 2 cli): Error: Invalid attribute displayFormat for element xref X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2019 03:52:04 -0000 #419: Error: Invalid attribute displayFormat for element xref Description changed by julian.reschke@gmx.de: Old description: > ...for something that seems to be valid to me. New description: ...for something that seems to be valid to me: {{{ and optional TCP port (). }}} -- -- ------------------------------------+---------------------------------- Reporter: julian.reschke@gmx.de | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.24.* Resolution: | Keywords: ------------------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Mon Aug 26 01:21:44 2019 Return-Path: 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 331AA120045 for ; Mon, 26 Aug 2019 01:21:43 -0700 (PDT) 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 golXPwtnb8mC for ; Mon, 26 Aug 2019 01:21:41 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 903DD120025 for ; Mon, 26 Aug 2019 01:21:41 -0700 (PDT) Received: from localhost ([::1]:34017 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1i2AFw-0007zK-Ez; Mon, 26 Aug 2019 01:21:40 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com, julian.reschke@gmx.de X-Trac-Project: xml2rfc Date: Mon, 26 Aug 2019 08:21:40 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/419#comment:2 Message-ID: <084.51abe47e756dcd0cd26a18939b9fe9db@tools.ietf.org> References: <069.d5d30ff1a5db56e9a2891f7905ff7012@tools.ietf.org> X-Trac-Ticket-ID: 419 In-Reply-To: <069.d5d30ff1a5db56e9a2891f7905ff7012@tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, julian.reschke@gmx.de, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [xml2rfc] #419 (Version 2 cli): Error: Invalid attribute displayFormat for element xref X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2019 08:21:43 -0000 #419: Error: Invalid attribute displayFormat for element xref Comment (by julian.reschke@gmx.de): It appears that is accepted, though. According to , should however work. (FWIW, I'd not only deprecate but remove it) -- ------------------------------------+---------------------------------- Reporter: julian.reschke@gmx.de | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.24.* Resolution: | Keywords: ------------------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Mon Aug 26 05:44:50 2019 Return-Path: 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 2A7B512082C; Mon, 26 Aug 2019 05:44:28 -0700 (PDT) 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 5AVu0viRG_wx; Mon, 26 Aug 2019 05:44:26 -0700 (PDT) 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 1876112021C; Mon, 26 Aug 2019 05:44:26 -0700 (PDT) Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from ) id 1i2EMD-0002SA-UW; Mon, 26 Aug 2019 05:44:25 -0700 To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org Message-Id: From: Henrik Levkowetz Date: Mon, 26 Aug 2019 05:44:25 -0700 X-SA-Exim-Connect-IP: 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: Subject: [xml2rfc] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2019 12:44:36 -0000 Hi, This is an automatic notification about a new xml2rfc release, v2.25.0, generated when running the mkrelease script. Release notes: xml2rfc (2.25.0) ietf; urgency=medium This rounds up the remaining known issues raised by the RFC Editor staff. Commit log excerpt: * Rolled back an earlier requirements change, and added a restriction on pycountry due to a buggy release. * Fixed a number of issues with the xml generated for ToC and Index. This makes the ToC output from prepped files the same as from unprepped files, which was not the case earlier. * Fixed an log() argument error. * Modified test input files to silence known issues with legacy rfc xml test files, in order to more easily be able to see newly appearing errors. * Fixed a string formatting error. Fixes issue #417. * Changed processing progress messages to more consistently obey --quiet, and to be visually distinct from errors and warnings. * Modified the PI stripping so as to be able to silence warnings during preptool processing. * Added indentation handling for variations of
      on request from the rfc-editor staff. * Moved the check for appropriate content from the text renderer to the preptool, and tweaked it to permit  , e.g., 'MUST NOT'. * Added a base_url setting to avoid an error message during pdf generation. * Added an option --id-reference-base-url to set base url for rendering of with I-D section references, with a sensible default; and set a default value for --rfc-reference-base-url for with section= ease of use. * Tweaked the conditions for a preptool warning about missing docName to only apply in non-rfc mode, and added generation of any missing element from docName if present. * Widened the search for seriesInfo elements when handling the --rfc-reference-base-url option, in order to handle all possible placements, and fixed a bug in the creation of target URL when using this option. * Added a warning for elements without proper v3 alternatives during v2v3 conversion. * Fixed a bug introduced in [3201] when stabilizing attribute order, which could cause errors when running v2v3 conversion with XInclude insertion. * Changed the code for --info dump to work for both py27 and py3x. * The --legacy-list-symbols option was checked for validity before the version attribute of the input file was seen. Moved this check (and some similar cases) later, in order to permit it to be used with v3 input without giving the --v3 option. Fixes issue #414. -- Henrik Levkowetz 24 Aug 2019 22:02:32 +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.25.0' Regards, Henrik (via the mkrelease script) From nobody Mon Aug 26 05:49:39 2019 Return-Path: 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 9935F12004C for ; Mon, 26 Aug 2019 05:49:37 -0700 (PDT) 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 8ZNW5sdnSpXG for ; Mon, 26 Aug 2019 05:49:36 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04331120047 for ; Mon, 26 Aug 2019 05:49:36 -0700 (PDT) Received: from localhost ([::1]:39599 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1i2ERC-0001aN-Sa; Mon, 26 Aug 2019 05:49:34 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com, miek@miek.nl X-Trac-Project: xml2rfc Date: Mon, 26 Aug 2019 12:49:34 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/418#comment:2 Message-ID: <084.65a63d5e7b236c9110a0120fb16d07ad@tools.ietf.org> References: <069.96cf890ca45cceab7afdcd494a0f664c@tools.ietf.org> X-Trac-Ticket-ID: 418 In-Reply-To: <069.96cf890ca45cceab7afdcd494a0f664c@tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, miek@miek.nl, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [xml2rfc] #418 (Version 2 cli): weird index generation X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2019 12:49:38 -0000 #418: weird index generation Comment (by henrik@levkowetz.com): There are known issues with Index generation and rendering, indeed. After consultation with the RFC Editor staff earlier this year, based on how seldom Index sections have been used, fixing this has been given a lower priority than other work necessary to address issues raised by the RFC Editor staff before the transition to publishing RFCs with XML as the authoritative version. -- ------------------------------------+---------------------------------- Reporter: julian.reschke@gmx.de | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.24.* Resolution: | Keywords: ------------------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Mon Aug 26 07:27:39 2019 Return-Path: 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 558101201E0; Mon, 26 Aug 2019 07:27:25 -0700 (PDT) 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, 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] 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 gYzhgB987eeo; Mon, 26 Aug 2019 07:27:23 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 3BD0F120018; Mon, 26 Aug 2019 07:27:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1566829635; bh=4p5BCGgIr32gs3hh+7A7K0uUq97h4ew0ZSG/b6BfUfk=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=MEYFeyGuJzyPDId4oTStgqNocDMSNC/q/9XAnEFz/KiP9HavN0f/jJNQx18BtYrhg 1gJZNn/ODs3OeXX58pqo5HszsqRmrLclyWnxDvMpjmtKnFcvitRI7WwwgMEFYLDbeD BiA4sgQn5rPF5VMruHV/fhnkJROtht+faqovG7ZY= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.124] ([217.251.143.234]) by mail.gmx.com (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1M7sDq-1i67UT0KNm-004zHF; Mon, 26 Aug 2019 16:21:51 +0200 To: Henrik Levkowetz , xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org References: From: Julian Reschke Message-ID: <22880345-a324-8dfd-a08c-e8ec89aeb9b5@gmx.de> Date: Mon, 26 Aug 2019 16:21:46 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:cSd0+dyqlArNsVvlQ+AnDZFkVlbT7esM6H8ttSoXg6zV9IKusdy bXDMKxHaVJrdwOWsuGY2XbSYZf9Gkor5MdmJrA1oq17MtQWwVSQh6eWLRtm59f0uWdQ3L5i 1YTUGq+1q7UK8ZCdwI0lR6GVGSlhyx8kZC1DHQ/QaVGWJVaUPv8eX7YezV24dPjt3UpjRA7 /AAxPJEIlaGLUeWgyf3Vw== X-UI-Out-Filterresults: notjunk:1;V03:K0:C3VP0ieARdc=:VtSPI3ShnC/wcKra1wOD2P YQWdXYACDc1MMgZbEj2XL13gGGpjdtIypAvW0ualG2r3y7tl1K2/gARhove5yF9KCohSFmhwk K9YfCBNsZsTqSGja6HDJtWsrpRCxpuNgOABlVaDWjJ7Sf/SSgPzj99Hi05EzWfA/4BWjBAg73 qhCLFk+WEmfac/pP2v/oIYbZE1+k/oz/gkEG/ch7rVoP9yrgzHXTriFR75Q6P9+6ZAjEoAZDE EF7RaSGa49NXdUucgw66i6W0r5SLlNQ20LOk/jNaxwn/K1n0dyFcj3D17YdH+WX5FfKCZ2hBy 92oEsD8cc71ZehJiz2r4x/ma+VPOfPywMiNmq1HqbR+fANjehP9iKhuXOTI+Ve+KtnHFnBmOt v55EpYz5730hxOfoZYdNYzC5WgzpGmdRwZ0mCGXWNY5/ZVCqHShm0z0rUwb+o76OEh8hNta97 U2tc1w4W1TMF8sCEOH6MtcINfYIQdtPu8OfeLaa6MOtaQ8yaPeLwWul658bNx8N+ZZgDd5lA/ R66XzqT/aK4eXqeiz+Eu9KZjKwVs6AobRsnn91UU4+4RwkKM4GR8QaLpFRQieDOiJkb3D6hZE NXXmPBZuRaR3UwTZ7nwecOB0Rt6oHbgCfFiJnPLmC6bfUbGxV/U5wByYIuW9xx3eGL4CnfE5w 4/EX8jzWSOlu5IAtnA4R86dy1nYQUv1Km/CvKB9EhkBKWof9KpL7fSY1IRfjmG7MHUwvqqvqR BCm1lYsajt+e5PXM5GMx44/sbHUIV6ODbNLm2+kFt8WZ4uNRapN40c/+O1omxPgmVbimjGpal PLe1hYy0tTrF2vIJ5KoShB/0lifPM0LVN3mWasnMw/4MEYiFhp/lr2UpQZBLzRwGKmG/QcMbk n2g4abwPHU5liVrDaBjd39V3EdSr0sIv30upldJav66k8vYZhFPqicoL5XoH2oStovPGUvnTy ckm9C+MXDCMGEQpyDFeMNcjQNMUrCqTgBPGGGH0aNlvm1wF5LosDA6bH3ryuNFAfIUKjlS/lq VQAWhW5kLneByfu8eMltd21ogKxjmK6FxBNGMk/9uBxcRl6B6XGf3zgChwK/lC3wUTmj+Iw04 hqCEY4O0XFkRrvHuK8H8PGS/M45DB5L1wkTCRr06V5Z9BtuK7BcExNHK+Hi3WLVjk47X/UYnb RlISQ= Archived-At: Subject: [xml2rfc] bcp14, was: [xml2rfc-dev] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2019 14:27:26 -0000 On 26.08.2019 14:44, Henrik Levkowetz wrote: > ... > * Moved the check for appropriate content from the text rende= rer > to the preptool, and tweaked it to permit  , e.g., 'MUST = NOT'. > ... IMHO a bad idea, because now rendering preferences leak into the content. It means that tools that do something meaningful with will have to process variations of whitespace characters (just NBSP or more??). If the desire is to consistently keep together keywords in output, it might be a better idea to let the renderer do that automatically. Whatever the outcome is, this should be precisely described in RFC 7991bis= . Best regards, Julian From nobody Mon Aug 26 07:45:36 2019 Return-Path: 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 2B8101200C5 for ; Mon, 26 Aug 2019 07:45:28 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=miek-nl.20150623.gappssmtp.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 mvqvYVjU4ohB for ; Mon, 26 Aug 2019 07:45:25 -0700 (PDT) Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (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 6564712001B for ; Mon, 26 Aug 2019 07:45:25 -0700 (PDT) Received: by mail-wm1-x329.google.com with SMTP id o4so15745919wmh.2 for ; Mon, 26 Aug 2019 07:45:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=miek-nl.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to; bh=F3E+cc9+HVvJHtlAOv647JgZhnm8Kutcbfm3cI0qvck=; b=luVbFBK8Wx6omi80sSaNjTk9fpaa5yfrhXuA6JC/2cYyYhwRj4fujDvD1t1M3Er/7b xGGB9Vkf5cGEWUGhtl3x7wyNXCmJMgOIgEFJ9m1ZD8eBjWYKJ9mjL74xzMzu2abO7TeM obS9486AEPuJ5tY6navTm24c7/Okl2dzw76EMJvDdxUGMv/cBBqR85KCGj5gF6wvLZn9 CTWNFqVqWTqbOcgrTDfLPPzc4Ut1AkrNQQsFhLpqZTURHd22fGkqgWx+Tg97xMRbz4Nc 6RQMEO/apYxmBvfEN9tKT3wxDZyV/gZm8HTHQ4e8hNiZun/EFvVeKidXARJFghpetpvV Wlpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to; bh=F3E+cc9+HVvJHtlAOv647JgZhnm8Kutcbfm3cI0qvck=; b=Pg7J0Ye5hyxbZ82KPKKo1HVWluAUrTcoKupAK051WC2RJu2y48+RXQ/u9VmuPmpSdC k2+F6eUMGq2fNLbw0Gfbz6wtKH5Xn5mqvw2z796mElwgSwDYDCJxg1QfwkxI5Hzzdiy0 G3AxghnzhNZEdR8FYGZFuaOwcoFXrurMqQl50AGvDk6SniJTlXew7naeXd3YPlSrZR3V 4hIzuFdb8OjeygYD2ygAWHHdSgIm4Ymds+SrNA9N7JiBW+9B5NY+pxNd0J+XAOk7plAA u5M3o7nZKtJCkstcTj9jBsYmRnbVtFr0biUv+aachOiaYllj710uywqA5/P6dXtUj2S5 nYdw== X-Gm-Message-State: APjAAAVIXJZer0y+lREKWMPISLTB6hfK954dx3TCYjhcxK72iFnbgKWz Avj6CK7KsMEN2OU9xRZ+gcKZ6g== X-Google-Smtp-Source: APXvYqzRxCe94gcOuD1y3LceUVy5OwIYWT/gKfy9nkibfxDhwDeqho5OciP/cIKwHTEQk3fMv9rqwg== X-Received: by 2002:a7b:ca5a:: with SMTP id m26mr20920269wml.134.1566830723575; Mon, 26 Aug 2019 07:45:23 -0700 (PDT) Received: from miek.nl (router.mikrotime.com. [81.187.237.61]) by smtp.gmail.com with ESMTPSA id 74sm21999792wma.15.2019.08.26.07.45.21 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 26 Aug 2019 07:45:21 -0700 (PDT) Date: Mon, 26 Aug 2019 15:45:20 +0100 From: Miek Gieben To: Julian Reschke Cc: Henrik Levkowetz , xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org Message-ID: <20190826144520.GA19037@miek.nl> Mail-Followup-To: Julian Reschke , Henrik Levkowetz , xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org References: <22880345-a324-8dfd-a08c-e8ec89aeb9b5@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <22880345-a324-8dfd-a08c-e8ec89aeb9b5@gmx.de> Archived-At: Subject: Re: [xml2rfc] [Rfc-markdown] bcp14, was: [xml2rfc-dev] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2019 14:45:28 -0000 [ Quoting in "[Rfc-markdown] bcp14, was: [xml2rfc..." ] >On 26.08.2019 14:44, Henrik Levkowetz wrote: >>... >> * Moved the check for appropriate content from the text renderer >> to the preptool, and tweaked it to permit  , e.g., 'MUST NOT'. >>... > >IMHO a bad idea, because now rendering preferences leak into the >content. It means that tools that do something meaningful with >will have to process variations of whitespace characters (just NBSP or >more??). > >If the desire is to consistently keep together keywords in output, it >might be a better idea to let the renderer do that automatically. > >Whatever the outcome is, this should be precisely described in RFC 7991bis. I tend to agree with Julian. This mean I'm better of always outputing "MUST NOT" instead of just using a normal space. From nobody Mon Aug 26 10:14:28 2019 Return-Path: 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 2B4AC120AEF; Mon, 26 Aug 2019 10:14:19 -0700 (PDT) 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 9G2SobvD-brm; Mon, 26 Aug 2019 10:14:16 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69851120AFD; Mon, 26 Aug 2019 10:14:16 -0700 (PDT) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:59767 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1i2IZL-00037L-CP; Mon, 26 Aug 2019 10:14:15 -0700 To: Julian Reschke , xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org References: <22880345-a324-8dfd-a08c-e8ec89aeb9b5@gmx.de> <20190826144520.GA19037@miek.nl> From: Henrik Levkowetz Message-ID: <40d507f2-ed78-e09f-ae96-c64333a91547@levkowetz.com> Date: Mon, 26 Aug 2019 19:14:07 +0200 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: <20190826144520.GA19037@miek.nl> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="E2LeFpkgvxm4rJxC3xhT39pbxhB2ewDRI" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: rfc-markdown@ietf.org, xml2rfc@ietf.org, xml2rfc-dev@ietf.org, julian.reschke@gmx.de 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: Subject: Re: [xml2rfc] [Rfc-markdown] bcp14, was: [xml2rfc-dev] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2019 17:14:21 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --E2LeFpkgvxm4rJxC3xhT39pbxhB2ewDRI Content-Type: multipart/mixed; boundary="H4Tr1SpWVgv9g4e3V54HSoiKsdU1V17bS"; protected-headers="v1" From: Henrik Levkowetz To: Julian Reschke , xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org Message-ID: <40d507f2-ed78-e09f-ae96-c64333a91547@levkowetz.com> Subject: Re: [Rfc-markdown] bcp14, was: [xml2rfc-dev] New xml2rfc release: v2.25.0 References: <22880345-a324-8dfd-a08c-e8ec89aeb9b5@gmx.de> <20190826144520.GA19037@miek.nl> In-Reply-To: <20190826144520.GA19037@miek.nl> --H4Tr1SpWVgv9g4e3V54HSoiKsdU1V17bS Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2019-08-26 16:45, Miek Gieben wrote: > [ Quoting in "[Rfc-markdown] bcp14, was: [xml2r= fc..." ] >>On 26.08.2019 14:44, Henrik Levkowetz wrote: >>>... >>> * Moved the check for appropriate content from the text ren= derer >>> to the preptool, and tweaked it to permit  , e.g., 'MUST&nbs= p;NOT'. >>>... >> >>IMHO a bad idea, because now rendering preferences leak into the >>content. It means that tools that do something meaningful with >>will have to process variations of whitespace characters (just NBSP or >>more??). >> >>If the desire is to consistently keep together keywords in output, it >>might be a better idea to let the renderer do that automatically. >> >>Whatever the outcome is, this should be precisely described in RFC 7991= bis. >=20 > I tend to agree with Julian. This mean I'm better of always outputing > "MUST NOT" instead of just using a normal space. It seems to me that the alternative to recognising "MUST NOT" as a valid keyword, and not emit warnings for it, is to disallow U+00A0 (which= is equivalent to   occurring in our XML) in this position. To me, that seems worse than the original problem.=20 It seems to me that future tools that process our XML should be prepared to deal with unicode whitespace generally, not only ASCII space. Henrik --H4Tr1SpWVgv9g4e3V54HSoiKsdU1V17bS-- --E2LeFpkgvxm4rJxC3xhT39pbxhB2ewDRI Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl1kE18ACgkQTptXS4+7 FxpnqA/+LcZDK9emgQRIy7WcGpyEtnHilnccYbiDn/DkqyW3kdsN2IwPTTVW3Ijz e9D7dD4yomRTM43geTKi1TXpbxpATosn3KNvS5dijmbl4Yn24DU5zHH3kUck5wWo ak3iGBJZrEAZ3ircx4IDAK6+ntFVXmZLoIYDLBlb5fIMd5cs2yhA1wLOITYgB8G4 VhvyL/3dd8oCfch82LlQQjywuUSqx2Yb8pAq1895jnphYk2ly4hVazz2pnOlFJ2Q u0TkInz23vkATH9H0RR45GunVSsrr+TKFc92IBM6xSZi2K2xq40UPVDpot8pSrm4 csGcb6Ev5Ohj/YKiebYJTTs45nFRXoCtY+NApwTLQgpB1bE90DbY1XZS6fzWJWl2 1/tketkhSv1IG3PVr2dd4H86hNG19jNlLykfy4Dod8hU4diNNkGHMOYJmNqg0UO9 pql+umpGWvFsQQn2Iff8D1dEYk67j7smnaNOL7WjuDVrdqIG6b8O7mC7HMGeD3he ymF3+QuAPdPQ8yRTkE2EU1qibqGMBmwJTQAyM7+u6NTGyGW6FkSXlzkBhgKeh0Ar VBhaSZ1l3SqLcgpC0JGj+ew8XMfc0h3Z4nCs8m5HDA5S7BN3q7v/hJcPx2soXmRQ judnGOQqx0wHrITfVVRwxUJtQcgc5uogl1vZt4NbocVyr7YP8sk= =6Elk -----END PGP SIGNATURE----- --E2LeFpkgvxm4rJxC3xhT39pbxhB2ewDRI-- From nobody Mon Aug 26 10:27:12 2019 Return-Path: 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 F384A12008B; Mon, 26 Aug 2019 10:26:56 -0700 (PDT) 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 BVKkxV6r7tFF; Mon, 26 Aug 2019 10:26:55 -0700 (PDT) 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 C735D12084E; Mon, 26 Aug 2019 10:26:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1566840398; bh=HqbRghhrflW0frxQJPiCSog4YA8SgZl3ArlmbqIZj+Y=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=h/A4g2CrSGdfNWl/I5fUdr/bhEm4EsPD7g+Avw6YcvZmSUEhi+9ztgtyblM4V0Pz6 GHMsY+loSEmrO6hQikTSjd1F0ExmYYBcEpKJ/LWWD03L7NM7M6zqmboJj4asqNX70H ns4qhZFU7GRIynZZlGG+bFtrU2Ww9fu7lBLFgalM= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.124] ([217.251.143.234]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0Lhfu5-1iXWzX1IpN-00mr9H; Mon, 26 Aug 2019 19:26:38 +0200 To: Henrik Levkowetz , xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org References: <22880345-a324-8dfd-a08c-e8ec89aeb9b5@gmx.de> <20190826144520.GA19037@miek.nl> <40d507f2-ed78-e09f-ae96-c64333a91547@levkowetz.com> From: Julian Reschke Message-ID: <07f24586-9540-5170-e11c-9fca3c858b73@gmx.de> Date: Mon, 26 Aug 2019 19:26:36 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <40d507f2-ed78-e09f-ae96-c64333a91547@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:jgvxceVkTS1OHgQokr14H1CBJXmQiHZBaf940SxjA/L33vzPLb1 wd6FF4SusN27aPkYHfWsdtr5mRCZn4lU9yqLoxMhw08Gra7hH0eUfiZJLLLsT752+kQ9SGz nfufC+K84NfgRuSl050iRTtj1G6x7RoTd6oTI6VZvxa4/m5NRSjiDrXIHRrnmwNkzW1CuhQ PfJuBSq+oA97sgCKsthxw== X-UI-Out-Filterresults: notjunk:1;V03:K0:vN2rObqCaGQ=:YaKM0+Gzl+JHrzb5AopFRn n+Lpn8zEoNFxdXQT1vql/ZrktqimU1dV6UOO7pxhheeCIg0wO4lwqAUTVx/a/V2p2FG7DFWFF 6+VgxJ6pSSFN9zg9DtMn6qIh4cnvvCI3r5IJPFFyy+5Kw5V13+ZESNEPHEUVEyWR1LMCJNnVA 2r6lYv/tKm5LqT7agur8noVHxTRMCpbxi+EWhsyHsaItPT5kbolLLPkz+vQdhYXFc0piF2f4E 3rzYaOdzyKEM8O84aLSJhdr8eyyq6KrXHen2MxO8puYhSB5MsYVxmji8P9xKzZ5rGr23clDNo ALPR/n6NPhMo3mgDnTkQdrGq5SHd3mZX97bPH3aSdmkKJhdxCPjlssrStC9l0AzfnhZubY64p yEE5DtMLXNTM8AwL8qFRnssWbEeLgo6840I4E2b0tG6tx9Tx+8OeSWXhmeQrru/N4iUvMWxpW uKNa/k0V7FP8YKkdWsWoi10rT51+CiWKs31pusm01AhppDEBv1BBVusPH1Hjrk4+p2YsTiL0P dRYSysbv39J10qIfnsgIhHptj8hasOpi6mRJBX6OVnL5Piv7uDC3sqgUAg5+JD5m2eQWbUNSE bgztCXrKjvPVbgNpYdPZSTV8S+5kh77GR4mUjDB/nXA92usCCnU/ijrbrRk76sqiTl9h1rQ8M 3Pf2CZ+OsCgAr7O+/GQ7ae2fdllqPgYVPLdvorDGjl5xqWJflEvfRhOpthR64A70q01r0Z4nf OZtEnhuN/iha9Vmj4rgiYKDJnD3DgK7T8LhWw2TnuOIDoDYkE4ZEx22uZBZm6XuIQ7sA9mK7J BaO/EIskrKL3PtTsPdvlWSBG4p/gFRwqWZGbuYZf4QY2tyoRy8vX4v3I/gErZP/5z/Mv1xq7D Fr+9Ere37jxwWhojE2ZwWVCTWHc8aq29+TsoPH6xYSCeUTL8+nVhWQRvHXpanyxP35WZCzuaD 7KoO0LpCggQtd1LOgi3PBpystRrRJo8geJsgGZ9s9MXj7BV1gcZwUOQCzOVsmzq6XOxXYVqOl mzvk160g0rjNto5DV2QcdhjdJJO/cCVBRBR+lCdZjQMHk/KZNAyuK2D/NFmIS8k2dvyymXpa5 Y2B9XNYsjAnXH4qwVcafD9lw06D32p65Ax4CMBjTtyU2pOhkfrqZIc6vTXN9SwRJ+HQusceBO fIZ7hZPqPeHXQkq93sY+Oe/SHxQj6uFvp9md7i8XjIvueivA== Archived-At: Subject: Re: [xml2rfc] [Rfc-markdown] bcp14, was: [xml2rfc-dev] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2019 17:26:57 -0000 On 26.08.2019 19:14, Henrik Levkowetz wrote: > . > It seems to me that the alternative to recognising "MUST NOT" a= s a > valid keyword, and not emit warnings for it, is to disallow U+00A0 (whic= h > is equivalent to   occurring in our XML) in this position. To me, Yes. Or warn about it. > that seems worse than the original problem. > > It seems to me that future tools that process our XML should be prepared > to deal with unicode whitespace generally, not only ASCII space. Yes, but not necessarily everywhere. was not added just for rendering, but also so that tools could extract information about normative requirements. I just don't see how detecting the keywords will work reliably if it requires converting an essentially open-ended set of Unicode characters (given that the set of whitespace characters can be extended). If the sole reason for this change is to avoid breaking up MUST_NOT (and friends), why not hard-wire that into the renderers (for HTML, I believe it could be done with CSS...)? That will at least create consistency, and avoid yet another task to deal with during AUTH48. Best regards, Julian From nobody Mon Aug 26 13:37:14 2019 Return-Path: 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 953F1120FD8; Mon, 26 Aug 2019 13:36:54 -0700 (PDT) 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 Z-vmMwUrw4vG; Mon, 26 Aug 2019 13:36:51 -0700 (PDT) Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) (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 8F4EB120FCF; Mon, 26 Aug 2019 13:36:51 -0700 (PDT) Received: by mail-ot1-x32e.google.com with SMTP id z17so16464563otk.13; Mon, 26 Aug 2019 13:36:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=szcV9z3/Q92HwK5h9ZqkPfFDRW48710t4ieqQsCu7fI=; b=UttvhmZ5L5hFGpKeo4rxzgMgreRWn2NDJKtLLfz6yb9kibuoN/hj6kX1ysrkqCvItR 575ico1GAdyQR3sQpodWAFvKo37wA8fDlNrdZj6Th9GepiDJRDoF6Onq70ZFrOL6uhPq QqJoaX3v1CIjaLwAXQng37GI8vcC3OUgsnUQnFrKVUjqWMVNcFc0eAu0m8VdtmQaxway CQZk7Y4AvlPiM+hM+cGZfv9F/hGpp3RvFev8M5Vf/QMjo92G1mEatDtRHz5eJnwEkAJY qR5WrywUCAVbZSK4NvEnbFjerd4LW/oGgYz+UJl6bXFa+dB+gvIdKLhb6Bk6TgMoBKhP 4JZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=szcV9z3/Q92HwK5h9ZqkPfFDRW48710t4ieqQsCu7fI=; b=f7a5v/jsVkZ42QLjI1H0mmAHtOSUK1wK5AagQw/QD8pnZ86sZgWfa5SbiLpDsr40sy W73hvdZzdtTtxGEwQnLe0HI0gqrSke0gflyZkJ1Up8vnNkK093M/Ix8hrCccT37wCN6B eGcpOFfn1rlaSOW6HBdMBcnHu6J2qZT1+5U18TzgIhTZZfOId4S+shxM2EPFvXi0qHFe KIDpTWwr8lDyd3RaqHQpBuyhU7gPJuNcKYLpagUJ+L+9DwGn4DhDx3Z6FG5SBCwbeYYE sg292njwkupN+rsw3bpuZ7tgILxZWKpwZukAspukhFNlasF0ic2aBEEoauQA4edy/5pm iSVQ== X-Gm-Message-State: APjAAAWDa44H03it5zLOgrCnQ3QmKts1uhtsn8HWr4bbZDIFOfroAY5V MFbSpTwLiZKOxnaCyIXBP14= X-Google-Smtp-Source: APXvYqxOIHCi/hrZ+HrkpC9vu0YRcGlyBGlo92gmuG1myGz/0de2OeY6FStafNs04oTT+yHjLvXk4g== X-Received: by 2002:a9d:5601:: with SMTP id e1mr6770484oti.370.1566851810979; Mon, 26 Aug 2019 13:36:50 -0700 (PDT) Received: from ?IPv6:2600:8802:5903:df16::1053? ([2600:8802:5903:df16::1053]) by smtp.gmail.com with ESMTPSA id q85sm3964321oic.52.2019.08.26.13.36.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Aug 2019 13:36:50 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3578.1\)) From: Fred Baker In-Reply-To: <40d507f2-ed78-e09f-ae96-c64333a91547@levkowetz.com> Date: Mon, 26 Aug 2019 13:36:45 -0700 Cc: Julian Reschke , xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <22880345-a324-8dfd-a08c-e8ec89aeb9b5@gmx.de> <20190826144520.GA19037@miek.nl> <40d507f2-ed78-e09f-ae96-c64333a91547@levkowetz.com> To: Henrik Levkowetz X-Mailer: Apple Mail (2.3578.1) Archived-At: Subject: Re: [xml2rfc] [Rfc-markdown] bcp14, was: [xml2rfc-dev] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2019 20:36:59 -0000 > On Aug 26, 2019, at 10:14 AM, Henrik Levkowetz = wrote: >=20 > It seems to me that future tools that process our XML should be = prepared > to deal with unicode whitespace generally, not only ASCII space. That makes sense to me. The normative language is as seen by the eye and = processed by the brain, not as processed by some random computer = program. One implication is that it can be broken by a line feed or any = other construct that the brain renders as white space.= From nobody Mon Aug 26 16:06:42 2019 Return-Path: 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 31DC9120F02; Mon, 26 Aug 2019 16:06:27 -0700 (PDT) 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 ixC_BT29JFbg; Mon, 26 Aug 2019 16:06:25 -0700 (PDT) Received: from gro.dd.org (host2.dlawren-3-gw.cust.sover.net [207.136.201.30]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C86BC120EE0; Mon, 26 Aug 2019 16:06:25 -0700 (PDT) Received: by gro.dd.org (Postfix, from userid 102) id 230AC10D626; Mon, 26 Aug 2019 19:06:25 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <23908.26097.125524.792528@gro.dd.org> Date: Mon, 26 Aug 2019 19:06:25 -0400 From: Dave Lawrence To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org In-Reply-To: <07f24586-9540-5170-e11c-9fca3c858b73@gmx.de> References: <22880345-a324-8dfd-a08c-e8ec89aeb9b5@gmx.de> <20190826144520.GA19037@miek.nl> <40d507f2-ed78-e09f-ae96-c64333a91547@levkowetz.com> <07f24586-9540-5170-e11c-9fca3c858b73@gmx.de> Archived-At: Subject: Re: [xml2rfc] [Rfc-markdown] bcp14, was: [xml2rfc-dev] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2019 23:06:27 -0000 Julian Reschke writes: > If the sole reason for this change is to avoid breaking up MUST_NOT (and > friends), why not hard-wire that into the renderers (for HTML, I believe > it could be done with CSS...)? And I readily admit I might have missed a memo, but if that is the sole reason then how did we arrive at the conclusion that they needed to be inseparable? From nobody Mon Aug 26 16:47:09 2019 Return-Path: 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 77A45120EE0; Mon, 26 Aug 2019 16:46:56 -0700 (PDT) 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 2G7q2l5rPOv9; Mon, 26 Aug 2019 16:46:55 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5197B120811; Mon, 26 Aug 2019 16:46:55 -0700 (PDT) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:61412 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1i2OhK-000183-En; Mon, 26 Aug 2019 16:46:54 -0700 To: Dave Lawrence , xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org References: <22880345-a324-8dfd-a08c-e8ec89aeb9b5@gmx.de> <20190826144520.GA19037@miek.nl> <40d507f2-ed78-e09f-ae96-c64333a91547@levkowetz.com> <07f24586-9540-5170-e11c-9fca3c858b73@gmx.de> <23908.26097.125524.792528@gro.dd.org> From: Henrik Levkowetz Message-ID: <1eff2a94-3cf1-4fcd-a0f9-b2b12230d894@levkowetz.com> Date: Tue, 27 Aug 2019 01:46:46 +0200 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: <23908.26097.125524.792528@gro.dd.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="qsCq5VRFIsGLk3qelLPoT77KoBh9CNNRJ" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: rfc-markdown@ietf.org, xml2rfc@ietf.org, xml2rfc-dev@ietf.org, tale@dd.org 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: Subject: Re: [xml2rfc] [xml2rfc-dev] [Rfc-markdown] bcp14, was: New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2019 23:46:57 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --qsCq5VRFIsGLk3qelLPoT77KoBh9CNNRJ Content-Type: multipart/mixed; boundary="f2MCC8n7vf5fH4lUqHJ6O1p9fwedOWlp9"; protected-headers="v1" From: Henrik Levkowetz To: Dave Lawrence , xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org Message-ID: <1eff2a94-3cf1-4fcd-a0f9-b2b12230d894@levkowetz.com> Subject: Re: [xml2rfc-dev] [Rfc-markdown] bcp14, was: New xml2rfc release: v2.25.0 References: <22880345-a324-8dfd-a08c-e8ec89aeb9b5@gmx.de> <20190826144520.GA19037@miek.nl> <40d507f2-ed78-e09f-ae96-c64333a91547@levkowetz.com> <07f24586-9540-5170-e11c-9fca3c858b73@gmx.de> <23908.26097.125524.792528@gro.dd.org> In-Reply-To: <23908.26097.125524.792528@gro.dd.org> --f2MCC8n7vf5fH4lUqHJ6O1p9fwedOWlp9 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Dave, On 2019-08-27 01:06, Dave Lawrence wrote: > Julian Reschke writes: >> If the sole reason for this change is to avoid breaking up MUST_NOT (a= nd >> friends), why not hard-wire that into the renderers (for HTML, I belie= ve >> it could be done with CSS...)? >=20 > And I readily admit I might have missed a memo, but if that is the > sole reason then how did we arrive at the conclusion that they needed > to be inseparable? They don't. There's no such rule that I know of, and I don't think there= should be one. But if an RPC editor decides to make it so in some cases, why should xml2= rfc get in the way and issue an inappropriate warning about unrecognised keyw= ords? No reason to do so that I can see. Which is why I made xml2rfc recognize= both "MUST NOT" and "MUST NOT" (and "MUST\tNOT", and "MUST\nNOT", an= d some others) as a BCP 14 key word. Henrik --f2MCC8n7vf5fH4lUqHJ6O1p9fwedOWlp9-- --qsCq5VRFIsGLk3qelLPoT77KoBh9CNNRJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl1kb2YACgkQTptXS4+7 FxpJJRAAt04GiKOuavqChiWGv9ZAM8kwH6EG1Xxpaj8HBgP6JQPQkbi7H2y77Ksz JhkdybQQR/IZRlerKqSX/7YU5k+PsPbuam4vP2IP3qxXNb7Zf3QJ0bdTVMlS7IWe yW+Z3N0Mb+76TQPjI1Lniqnail4h49DlvTtHfTSyjfH1YrpbJBZu1KqPpsskk34L rZ+Fzs7kzWCl+Jcw1qqH9UwHdDA1JzFKBmcrgiQCwYp5nITsKSUHAqYRHbXoZd2D X0sI6WcKQ+vVHftSu6g4+/OcD06nPN/a6YanmfkEnsJl+Ks0//oJpH6RTONPB21b 1zNtBMWwh25705wDTTDhbtFMFRjbUCZYgUOxshNrE0ajPOQ8Xatk09+tBiCruAO5 1BW+hfav/aalmt6HvTs7sO78TmLJNK0HoG7SJnLQHnVq3EJZleh+fFuMoaGSl+bU eCjgRF+I6IznOakKZbfpUHw4Rw7EyygpIRdFMvT8BJhvB4JuQ+czkeRXU7Z5VtM3 XmVY5DFhhldgYFMcyr7QhEJ4zJf0gT7nsJcFJdEfMNb54ulI6cZVh1BfzmRuyiiC f1DMo1Pf7NfN7GIpv2y5uUgX6lX5wAzxlXdoDkwcUHJWYquMyaUv+PgC1fVxtkw/ kRjsvdmWO/vDdepXBIgLz4d4x2ghnIp/hgjEHnW6Yh8HvlNTmKY= =1JG8 -----END PGP SIGNATURE----- --qsCq5VRFIsGLk3qelLPoT77KoBh9CNNRJ-- From nobody Mon Aug 26 22:44:44 2019 Return-Path: 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 AEFAA120F18; Mon, 26 Aug 2019 22:44:29 -0700 (PDT) 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 UnVJFxYs-IE0; Mon, 26 Aug 2019 22:44:28 -0700 (PDT) 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 E1D97120823; Mon, 26 Aug 2019 22:44:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1566884663; bh=09q3fA5Yjm9WguAqeTvO/4Rnxej0Xu1BL4XDVkSRjo0=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=czIPscf+VDwdrwvMR0axQ9nTl0o9Ldwnsv55/we5AmSo04mhEsFn1ByDlY0o/g1Lk u5UBJY1s4KbvrwS7uow3Ol/dd7I8dxQkWqZIOvHJpqm2+UHBvI07OSZbhZeS+XHaNz gv3c1hQtzmUsiTfYwrbZwxiOzMrhy3b02tVv8q4Y= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.124] ([84.171.157.68]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LfBX6-1iZPNH10eG-00oolN; Tue, 27 Aug 2019 07:44:23 +0200 To: Dave Lawrence , xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org References: <22880345-a324-8dfd-a08c-e8ec89aeb9b5@gmx.de> <20190826144520.GA19037@miek.nl> <40d507f2-ed78-e09f-ae96-c64333a91547@levkowetz.com> <07f24586-9540-5170-e11c-9fca3c858b73@gmx.de> <23908.26097.125524.792528@gro.dd.org> From: Julian Reschke Message-ID: <543eddce-957f-2add-beb1-205efcd7fb4d@gmx.de> Date: Tue, 27 Aug 2019 07:44:16 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <23908.26097.125524.792528@gro.dd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:rdx1AXrIJMuG5DaDGlY3BSe2UB87U3zVq+20qt+s8XFgDaytVSa iuNRZ3T1mv8D3Q6BHhScHu2A+VRpgWm6s3DKbHfOh+H1wXLHt/KHiK8TXY6za/48OSDywqu xv7lmCUX9u3opyUyfe08nzFowGINbwPdVkvbcUZl+WJFjzIS7l3fA2rzclZfBuCfE+a+Pyu PZux1FeU2oQmaVHJf3uGg== X-UI-Out-Filterresults: notjunk:1;V03:K0:HQ/jOe5Hffo=:nBLfQwLUpjFjQ975V37zzK yyLdeHiwMNQyQuekfaC6geXtc4LaoC16wgbMwSbFb6oTIKalIEGNcZ/1OOzQXVt2lqcEth+Zc WXzj39duwMHdc7B7cM+7hlQuTCtvSOzEZ8i60Kuz+e1rgu2borzKPzX9eeh+CwQIjjXPJn3zw 8ypwlp/hYjAsCnkwcEwaikxPPP9L72DR4wDDPMUpNigLyf7hu7pkZOyRfrkkPs7Bo8Dqox5eU 0mpi3VFWTkhzsRCNy4MlcHeZO8D9X+BAdX9gqE7fw+u6WIykpvG/pdhrOL5ZcDFJD0z9eKWAM dcXCNYCGlC/AVm0LnP0W8+Nu81zDZCSPiqsZxh46gPHhOoLlUaXC2Oc1GlgsqiGhFGKZuuN6s 2DxdXbe3lPDhPk8rqjKutihxXXbH/l4ICPlwZpjfa6jyHKOaLPDi7rEAdKjXaEbtGHq6t1mxU Wm8X31jGlmbB1MsZbpVRqltiNP5KKVRC3UliPzE7HwIOPb+bqy+Huu0X59iLpIVMkHqwP+LmL 3vjV/OpuftVGdMA+7nJ9qmw2LBPPctFr57vhORcsI3RGbrZY8kLh9WPG068+xx4WGPSDZ9qxe qdJZGJXwkZvcE4V+u4GXXmoI42ODMp6geLJpGAz02K874V68XLJwNBDvIKgI1YGzA8xDOfa7R dUUVQ3HyTD71QrJ8ffCPlV77LWNenmnw8aDp9CXqLDtcj0Y8aJVnUNlOxh4kBcnVYYtEzGte8 PfdNoSgoMAGh2N751aFsgt1+Fd1k5doK5qdBjC7fBcju5TEsOqRM0KqkAUPM8nDGma95el1Rx eoV2GQBmjm6UNlp/1i2U0pjHCG0DYgRlxtFErF+Ou7qL/icYppoLzfA3/R704ndXDGQo/glWJ 8xUGh5VqKhwECKQN101sxGrYTOdiJHn2KumiWnm9jd1b+Z9pJPo8wgqUjDANh5FfnSUVGOEMN JmzferayWl+fR3rtr5iWNuXZwVRslcr8bC180w1gF0mijZ4ZbFmY/anVwTBNYS9AGTxeWHrZH pdzDhXIrorGcRk4haTFp1wFH6kkHcay0lpBXgw80xb9WbQl/LjNUUZItcwlw/GaEYN98JYdTH GDsXX4Abq2eFzYJw/TAKFNfRQFet2dhfIf5tVwC8KufE+GryRIyyE+HxVzSvXqD44bJ6qMIH8 r9Gxg= Archived-At: Subject: Re: [xml2rfc] [Rfc-markdown] bcp14, was: [xml2rfc-dev] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Aug 2019 05:44:30 -0000 On 27.08.2019 01:06, Dave Lawrence wrote: > Julian Reschke writes: >> If the sole reason for this change is to avoid breaking up MUST_NOT (an= d >> friends), why not hard-wire that into the renderers (for HTML, I believ= e >> it could be done with CSS...)? > > And I readily admit I might have missed a memo, but if that is the > sole reason then how did we arrive at the conclusion that they needed > to be inseparable? That's a good question as well. Best regards, Julian From nobody Mon Aug 26 22:49:01 2019 Return-Path: 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 C4DBC120F18; Mon, 26 Aug 2019 22:48:52 -0700 (PDT) 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 vR7uT9rloKQT; Mon, 26 Aug 2019 22:48:51 -0700 (PDT) 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 15297120823; Mon, 26 Aug 2019 22:48:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1566884916; bh=OLUaWJK/LqxAytsYHw3IHn+zcsVGFvwOWJm4MNMCYz8=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=jCpTNSwDstTmDmepVAFWcygfFkGMRZxIIasleCu7T9xOKi+g9aOPJx7pehU/NpOJU hcZMIw/DZZhpZ/1vx+dHByKOirGR/JFx/eOKMOdEDYPX9OX0HPYuy4k0CRVgyCuCup Uun4/IGSFNGsJZEkGdsgtvtByum+mbfWcEBVUS6o= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.124] ([84.171.157.68]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MhU5R-1ignIt1wqR-00ecbe; Tue, 27 Aug 2019 07:48:36 +0200 To: Henrik Levkowetz , Dave Lawrence , xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org References: <22880345-a324-8dfd-a08c-e8ec89aeb9b5@gmx.de> <20190826144520.GA19037@miek.nl> <40d507f2-ed78-e09f-ae96-c64333a91547@levkowetz.com> <07f24586-9540-5170-e11c-9fca3c858b73@gmx.de> <23908.26097.125524.792528@gro.dd.org> <1eff2a94-3cf1-4fcd-a0f9-b2b12230d894@levkowetz.com> From: Julian Reschke Message-ID: <86c614a6-908a-cb14-b13c-d7bf1c277532@gmx.de> Date: Tue, 27 Aug 2019 07:48:33 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <1eff2a94-3cf1-4fcd-a0f9-b2b12230d894@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:gPfqQwut2/N3EIU9Lppzf5n0y+xNF7Rn/XWvgKx6hKW6XsraFXK bDU2FjV2oflr/OpSFFojZSaHiSpbiAvTAnGQ/rcm1v7hzoIWl+lzw/3AHehJKyX6wd+pbT7 8T+Rulw+vYWw+Ioo/xEWt1h1bVzf5NtvK6sMRqCINqvJHjFU+UbL8uGVjGwpeWUCUQWFs0G pyDZVYrMreYuJIZhppMJA== X-UI-Out-Filterresults: notjunk:1;V03:K0:sP2J9TUD9vs=:DtwBiWCqwPVnjp/opLTDWe dbls24pwot69oA7xtc8ryQmHh3fZM7JJJyYLqBwc2lOrXUal9wwJMIWwf0BvzfpnMKX30Hllb 1zSJrGVohQ68Clye/7/+e/3xwY89oPGVVLirIxH0ni529tQWwkGcCJCUsxscvrXnFJbiZts63 Bq6p16kP4yWTPsLyBjYyrwFhGrxDygqq4DIKCUJ5TfABFGtEAN3I4EHmtp+5piXbkrgbUyXgA hwfgOwFSqqTgsludK26iJu8ACDUxdPnIjUMxgYGsaHgV/Y5jJL4mDvy39SzGEDsGOMlGooYFW 939C++lEoKJ4zt6m1xchLt3G1iI8lDxAVAE/jCwIO1Y3ubqEWxHMK9TGfPe3hANNlp+gWLOT9 c+WI4xdg4ediy3Uu7Q1xIVKgT1BLBGRsC50wwIdamqPGrrwUTHMQQsiPr/sze5q3Bh5GGl6sU XRE75JudDI7ZFVOY8aJXEFSBnzSSxRNsQCyNf+HeoJVE1EDH1puvnyS4uTewv3/4sNDaP8PP5 4IZjC9+xZdwLOTST7m0sNvmMsNqIzNKfERJTiKp7mp5IT45n/zj6BNDS0G3b/Sj64o0NKAlc4 h08Xxosdtzd2CpXH1z0G4wjt16deJGcgH5cqMToarO7proi3SuWrb4cgEBT+QsdsaUtwt+Dgx 9Yt8Zt+Fp4mUrS9P6WvG2RiKFvjBF524NHkreuAVhKb7UED5Sb8LkRjaOAnXf7mgJUcBx9z9F a6QZ5r6TgZOFcwRPXg3QMf8az7Luuf4/HbH88ZqJVz11PtINvCiVbRJ/NGwH5Sz87m2PiJvsb hCMu9mb/VHGHhDAuqEuk+MeKP2V5ZmxFL1CJXcXBZOpaROp5wFxne8iRu6+P63Y+M9vDuruup Nhc3rGS5WUxPcgME6Rb/iIPEdioc//GobpHtwnd3bqQxem4ExyuMWUv1xjywgqoL/lYJZVnfW gZDvdwT3XiH2ClC42AG8iKvwFjxgi88OOUNaOtndsgWgwoJjyIF5ItmEFbuZdJmQcrBkSpXs4 XNGHuMqdy02m+V10t3ZA7EJrhHwPfYeKP3/boZU28hotZqEEYD/NL8u1gUQ3yPjuRG9qr5yQh UG+CognB3D1zPfDpE0WlaQOegU6DqkPRC0ozNdTD3+/sSEPeXN3lZ5YjxXGr+cWW8pLQzhBha 3I5C1e49DfCQpW27kk1fIQPAOLBTgFv/ebkXLLmyLq7souvg== Archived-At: Subject: Re: [xml2rfc] [Rfc-markdown] [xml2rfc-dev] bcp14, was: New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Aug 2019 05:48:53 -0000 On 27.08.2019 01:46, Henrik Levkowetz wrote: > Hi Dave, > > On 2019-08-27 01:06, Dave Lawrence wrote: >> Julian Reschke writes: >>> If the sole reason for this change is to avoid breaking up MUST_NOT (a= nd >>> friends), why not hard-wire that into the renderers (for HTML, I belie= ve >>> it could be done with CSS...)? >> >> And I readily admit I might have missed a memo, but if that is the >> sole reason then how did we arrive at the conclusion that they needed >> to be inseparable? > > They don't. There's no such rule that I know of, and I don't think ther= e > should be one. > > But if an RPC editor decides to make it so in some cases, why should xml= 2rfc > get in the way and issue an inappropriate warning about unrecognised key= words? It would be good to better understand the requirement. In particular I'd like to understand why this needs to happen on a case-by-case basis. It sounds as if historic requirements (line breaking in plain text) leak back into the canonical source file. > No reason to do so that I can see. Which is why I made xml2rfc recogniz= e > both "MUST NOT" and "MUST NOT" (and "MUST\tNOT", and "MUST\nNOT", a= nd > some others) as a BCP 14 key word. What about other non-ASCII whitespace characters? Best regards, Julian From nobody Mon Aug 26 23:05:33 2019 Return-Path: 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 6F97D120F9D; Mon, 26 Aug 2019 23:05:25 -0700 (PDT) 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 bNxce18Pv0TS; Mon, 26 Aug 2019 23:05:23 -0700 (PDT) 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 21CED120F39; Mon, 26 Aug 2019 23:05:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1566885902; bh=H5De8PxMT+b1fOLkLeRa481TVxW5lswBHXWTsE5lfSA=; h=X-UI-Sender-Class:Subject:From:To:References:Date:In-Reply-To; b=GJ7SPNl5vaYY+TYstIbcS9mMVyHB6sxK0+rJCNgvvoMmRlYXHzvkWnVChvMTwcJw5 ton/xVBD3UPrVfgFilJN+cAtXX00aex8k1UGcwyC5wa6PjnFnjckDXDkiIM3CnfJcZ DZ4VynyxnrgYYzoyo6w8najCKWB00jTRBCB6yEhM= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.124] ([84.171.157.68]) by mail.gmx.com (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1M7b6l-1i8HUh1qxB-0084sl; Tue, 27 Aug 2019 08:05:02 +0200 From: Julian Reschke To: Henrik Levkowetz , Dave Lawrence , xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org References: <22880345-a324-8dfd-a08c-e8ec89aeb9b5@gmx.de> <20190826144520.GA19037@miek.nl> <40d507f2-ed78-e09f-ae96-c64333a91547@levkowetz.com> <07f24586-9540-5170-e11c-9fca3c858b73@gmx.de> <23908.26097.125524.792528@gro.dd.org> <1eff2a94-3cf1-4fcd-a0f9-b2b12230d894@levkowetz.com> <86c614a6-908a-cb14-b13c-d7bf1c277532@gmx.de> Message-ID: <029013b5-2195-c56b-915b-99f90845ee02@gmx.de> Date: Tue, 27 Aug 2019 08:05:00 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <86c614a6-908a-cb14-b13c-d7bf1c277532@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:bg8Qw6S3mMpCBRCeBqGHeNZfvw/8GUfr3U3zQAe0FQW9QY3JBnJ fOZKJycl3eMH+HNgMsAA0a6CMeTIApdXnLpkkWHVqMA3oG1bEGXBMm2ruGLI6Yzn0cGDarv jJM0Wk2gBR62wwPVr2vfFyx6f3tO2Q1V7hkCjOJ1GtKHwa2r87EO9fRnOyb6jUcSS8AbcvY MOg2Qgi/2gjVK97DABAAA== X-UI-Out-Filterresults: notjunk:1;V03:K0:GNlqp+Dq+qk=:iKh2W/bRmoIt8IBbosgX0E O9vFLM969n9/btp9x4kqwjLloP5JHeELC0WRp4REEaR/dmPZsIpz2pHAG1dcWDqID0ryjz/Gt abDDcwYMHqOkMaCVOmuA6QtOZyOcoNW9oA98TvcQ18BKhw8uQZqnp8j4Uo5BAGRtYBcQi27+q a6CPys7b0e9bNkpVpUx9qpNKLtihlIGLIk4O45ZwHMsh8iUY/s5jnLxaufisZF0BOOjx1+Tb7 WxtS8YWL2wH+IYK0IwnPYdAwwZiVDNag1ivkN2J1FDb2tK56jFb64gODcK24Cf3xGMNkx/VkH bXGBuQkIFv52uspeqqAaPEYQm7mPTdmPCpAn2bOgSUGYHLfXhIJV25hS6UYe72B3e1QIZUE3m RXAmuS5fkx4T+aO15PmsM3zBM9K3iQ39Y+JjRmuojvJ/dTsNGDnbEUsXUU1o5jggzxDfsDftL j3OpIpmfKEF7UTLeHD1db5VHP/6+2OUL2Ofh8dz2Es0rZkYmw/NeIP5x/O8/t+4cStqXq5ORc upKPQ7+fXnNvNvnzFz7UyZ0nUxXkYmp5YCQ/wVOYUJurOS8KzG4jg53YQPBuHG/KNOYQGKOkf wcUjgdZ+eHB+Un7qC4ExFvCC2KgEbcCbGaTHrACD4uqmbeJe02t/qFgnrUTkm/oZd1ABR6J4r 6SfzdfO2TlWv6MWRYtoe2GLHkooXNnZXCOqagMG+b/UTxLiaCn7Q3/XgizEJLWTMkIpwE0JzZ ze5+qPEsydYUvsUpmD9piZftqcxZeEA+at9wAmMvLViDhPfTclBeotkWOnF27IV7VlETrgR0i fc4xIVyOVfHzrNdjQvfszApvoQJrmFWMhTG4rOWRqgJkTNCMtM+zfSNiyv2usI/6Icb4h94gJ 2brj4wWXKwk+0KlP0Hyd5xTACu/WMZpfJ++RqmLLCJ78CTJqPZg7MZdzGZmnth1NGVLiIg9I1 RjPvdql1eYVbDWSkIPnuqCJDeIpBuQKF2hu10zwt7VOL2l9In7GcogcBq8LnO7hUW+nO2/7Lq WLa487bcNjGUI3ZpMplESYGovwk93vLfd+FqAkaQWqWEHVpW1TcHm3r4jNLn21mk7ss9vw10e xT3aMdn+RmA6xwri/NLCo0fSqJt7j/2qr4fOfGNBldZVHSoOyZ1rayJXfyKLtsY7Pa+n0QQuZ PFoS0= Archived-At: Subject: Re: [xml2rfc] [Rfc-markdown] [xml2rfc-dev] bcp14, was: New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Aug 2019 06:05:26 -0000 On 27.08.2019 07:48, Julian Reschke wrote: > ... FWIW, opened . Best regards, Julian From nobody Thu Aug 29 12:22:57 2019 Return-Path: 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 805D1120BB4; Thu, 29 Aug 2019 12:22:55 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 n4R9dB0oPaEv; Thu, 29 Aug 2019 12:22:53 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90D47120BC0; Thu, 29 Aug 2019 12:22:53 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 0301F6211D; Thu, 29 Aug 2019 15:22:52 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id hzyk0oM3khxu; Thu, 29 Aug 2019 15:22:48 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 090F66211C; Thu, 29 Aug 2019 15:22:46 -0400 (EDT) To: Henrik Levkowetz , xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org References: From: Robert Moskowitz Message-ID: Date: Thu, 29 Aug 2019 15:22:38 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [xml2rfc] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Aug 2019 19:22:56 -0000 On 8/26/19 8:44 AM, Henrik Levkowetz wrote: > Hi, > > This is an automatic notification about a new xml2rfc release, > v2.25.0, generated when running the mkrelease script. Notes on my experience with the upgrade: I get the standard warning: DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. I have both Python2 and 3 installed on my Fedora 30 system. What is causing this message?  An old version of pip or xml2rfc? Is there a way to install xml2rfc v3 to start checking it out without loosing v2? thanks From nobody Thu Aug 29 12:35:58 2019 Return-Path: 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 D5448120C43; Thu, 29 Aug 2019 12:35:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.68 X-Spam-Level: X-Spam-Status: No, score=-1.68 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" 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 9t2uPq42Zz2F; Thu, 29 Aug 2019 12:35:49 -0700 (PDT) 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 790E3120C2C; Thu, 29 Aug 2019 12:35:49 -0700 (PDT) Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x7TJZegL097667 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 29 Aug 2019 14:35:42 -0500 (CDT) (envelope-from rjsparks@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1567107343; bh=7L9rCEm39f7YsDAUgjMHp+HG6R9jEz4J7L5B46flsgQ=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=HnN/ZQ/qyJQsHaa10rnExesa1cKZs7Sk0TEVn2P1jJOMHJguEA5Q015wosOolDl/L E7ScmEV4shOWVDKz1OieUcSPF3ygF+8rG8349sHSq06WIwtLn5IllbLpgGA6ClFp6b tIebZyC9VEzY8WJ/LlzUcwxkDRhrzWSQDVrxhiuo= X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local To: Robert Moskowitz , Henrik Levkowetz , xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org References: From: Robert Sparks Message-ID: <49ac6de5-b3ed-fee5-10d6-49c0b0540df6@nostrum.com> Date: Thu, 29 Aug 2019 14:35:40 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [xml2rfc] [Rfc-markdown] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Aug 2019 19:35:51 -0000 Hi Bob - The message is coming out of pip, and I suspect your default python is currently 2.7. If you run pip --version, it should tell you which version of python it's running on (and consequently which version it is installing packages for). There is only one xml2rfc - it can process both v2 and v3 documents. It also runs under either python 2 or python 3. RjS On 8/29/19 2:22 PM, Robert Moskowitz wrote: > > > On 8/26/19 8:44 AM, Henrik Levkowetz wrote: >> Hi, >> >> This is an automatic notification about a new xml2rfc release, >> v2.25.0, generated when running the mkrelease script. > > Notes on my experience with the upgrade: > > I get the standard warning: > > DEPRECATION: Python 2.7 will reach the end of its life on January 1st, > 2020. Please upgrade your Python as Python 2.7 won't be maintained > after that date. A future version of pip will drop support for Python > 2.7. > > I have both Python2 and 3 installed on my Fedora 30 system. > > What is causing this message?  An old version of pip or xml2rfc? > > Is there a way to install xml2rfc v3 to start checking it out without > loosing v2? > > thanks > > _______________________________________________ > Rfc-markdown mailing list > Rfc-markdown@ietf.org > https://www.ietf.org/mailman/listinfo/rfc-markdown From nobody Thu Aug 29 12:57:45 2019 Return-Path: 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 E4F15120B48; Thu, 29 Aug 2019 12:57:28 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 TmyQyRqHtDtj; Thu, 29 Aug 2019 12:57:27 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E5AC120BFD; Thu, 29 Aug 2019 12:57:27 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id F24896211C; Thu, 29 Aug 2019 15:57:25 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id MlL4b2oY3LrO; Thu, 29 Aug 2019 15:57:18 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 743D462110; Thu, 29 Aug 2019 15:57:13 -0400 (EDT) To: Robert Sparks , Henrik Levkowetz , xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org References: <49ac6de5-b3ed-fee5-10d6-49c0b0540df6@nostrum.com> From: Robert Moskowitz Message-ID: <1fc420c6-e836-4e6e-f073-2c50942226cc@htt-consult.com> Date: Thu, 29 Aug 2019 15:57:03 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <49ac6de5-b3ed-fee5-10d6-49c0b0540df6@nostrum.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [xml2rfc] [Rfc-markdown] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Aug 2019 19:57:29 -0000 On 8/29/19 3:35 PM, Robert Sparks wrote: > Hi Bob - > > The message is coming out of pip, and I suspect your default python is > currently 2.7. > > If you run pip --version, it should tell you which version of python > it's running on (and consequently which version it is installing > packages for). Looks like I have a pip, pip2, and pip3 installed.  So a question for the Fedora list. > There is only one xml2rfc - it can process both v2 and v3 documents. > It also runs under either python 2 or python 3. So no surprises?   The big v3 reveal being discussed on the IETF list will have no effect on drafts in development? thanks > > RjS > > > On 8/29/19 2:22 PM, Robert Moskowitz wrote: >> >> >> On 8/26/19 8:44 AM, Henrik Levkowetz wrote: >>> Hi, >>> >>> This is an automatic notification about a new xml2rfc release, >>> v2.25.0, generated when running the mkrelease script. >> >> Notes on my experience with the upgrade: >> >> I get the standard warning: >> >> DEPRECATION: Python 2.7 will reach the end of its life on January >> 1st, 2020. Please upgrade your Python as Python 2.7 won't be >> maintained after that date. A future version of pip will drop support >> for Python 2.7. >> >> I have both Python2 and 3 installed on my Fedora 30 system. >> >> What is causing this message?  An old version of pip or xml2rfc? >> >> Is there a way to install xml2rfc v3 to start checking it out without >> loosing v2? >> >> thanks >> >> _______________________________________________ >> Rfc-markdown mailing list >> Rfc-markdown@ietf.org >> https://www.ietf.org/mailman/listinfo/rfc-markdown > From nobody Thu Aug 29 12:59:11 2019 Return-Path: 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 10D11120BFF; Thu, 29 Aug 2019 12:59:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.68 X-Spam-Level: X-Spam-Status: No, score=-1.68 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" 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 etw78iX6K_vQ; Thu, 29 Aug 2019 12:59:08 -0700 (PDT) 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 B218F120B48; Thu, 29 Aug 2019 12:59:08 -0700 (PDT) Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x7TJx3LT001983 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 29 Aug 2019 14:59:05 -0500 (CDT) (envelope-from rjsparks@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1567108747; bh=+RTAW3IyikM7yhowY0fDC/74cseDWUpFIIcqrxFCtro=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=Y0ln6s/ru2J1uRuTEY7mtggPa8TIG13WpbFD0s065fjE3I7wODq6EY3uhcLyBkxKV RCyqFpB8hE++5C7SCitfGvWMAoW9/rFPljUM0G5h/62V4uRY37QNpKPIUSloZcMnOa csojSnTvpAyvDGmkmqfc2S7ypACujabhI/fXgfzM= X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local To: Robert Moskowitz , Henrik Levkowetz , xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org References: <49ac6de5-b3ed-fee5-10d6-49c0b0540df6@nostrum.com> <1fc420c6-e836-4e6e-f073-2c50942226cc@htt-consult.com> From: Robert Sparks Message-ID: <301e0246-759c-b735-0427-8a40156164af@nostrum.com> Date: Thu, 29 Aug 2019 14:59:03 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <1fc420c6-e836-4e6e-f073-2c50942226cc@htt-consult.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [xml2rfc] [Rfc-markdown] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Aug 2019 19:59:10 -0000 On 8/29/19 2:57 PM, Robert Moskowitz wrote: > > > On 8/29/19 3:35 PM, Robert Sparks wrote: >> Hi Bob - >> >> The message is coming out of pip, and I suspect your default python >> is currently 2.7. >> >> If you run pip --version, it should tell you which version of python >> it's running on (and consequently which version it is installing >> packages for). > > Looks like I have a pip, pip2, and pip3 installed.  So a question for > the Fedora list. > > >> There is only one xml2rfc - it can process both v2 and v3 documents. >> It also runs under either python 2 or python 3. > > So no surprises?   The big v3 reveal being discussed on the IETF list > will have no effect on drafts in development? xml2rfc won't try to process your draft as v3 until you change the source to say it is v3 source, or you use the --v3 argument. > > > thanks > >> >> RjS >> >> >> On 8/29/19 2:22 PM, Robert Moskowitz wrote: >>> >>> >>> On 8/26/19 8:44 AM, Henrik Levkowetz wrote: >>>> Hi, >>>> >>>> This is an automatic notification about a new xml2rfc release, >>>> v2.25.0, generated when running the mkrelease script. >>> >>> Notes on my experience with the upgrade: >>> >>> I get the standard warning: >>> >>> DEPRECATION: Python 2.7 will reach the end of its life on January >>> 1st, 2020. Please upgrade your Python as Python 2.7 won't be >>> maintained after that date. A future version of pip will drop >>> support for Python 2.7. >>> >>> I have both Python2 and 3 installed on my Fedora 30 system. >>> >>> What is causing this message?  An old version of pip or xml2rfc? >>> >>> Is there a way to install xml2rfc v3 to start checking it out >>> without loosing v2? >>> >>> thanks >>> >>> _______________________________________________ >>> Rfc-markdown mailing list >>> Rfc-markdown@ietf.org >>> https://www.ietf.org/mailman/listinfo/rfc-markdown >> > From nobody Thu Aug 29 13:24:42 2019 Return-Path: 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 D939E1208DD; Thu, 29 Aug 2019 13:24:29 -0700 (PDT) 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 vm4PtdEcf0bv; Thu, 29 Aug 2019 13:24:28 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A87A12001B; Thu, 29 Aug 2019 13:24:28 -0700 (PDT) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:60560 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1i3Qy3-00007g-EI; Thu, 29 Aug 2019 13:24:28 -0700 To: Robert Moskowitz , xml2rfc-dev@ietf.org, xml2rfc@ietf.org References: Cc: rfc-markdown@ietf.org From: Henrik Levkowetz Message-ID: Date: Thu, 29 Aug 2019 22:24:19 +0200 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: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="UubANVQJxgQHShtJDdGRSO3mA8vawaO1X" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: rfc-markdown@ietf.org, xml2rfc@ietf.org, xml2rfc-dev@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: Subject: Re: [xml2rfc] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Aug 2019 20:24:30 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --UubANVQJxgQHShtJDdGRSO3mA8vawaO1X Content-Type: multipart/mixed; boundary="UTdde9L09V53ff77kpQhqw7DdQOHsew7N"; protected-headers="v1" From: Henrik Levkowetz To: Robert Moskowitz , xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org Message-ID: Subject: Re: [xml2rfc] New xml2rfc release: v2.25.0 References: In-Reply-To: --UTdde9L09V53ff77kpQhqw7DdQOHsew7N Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Bob, On 2019-08-29 21:22, Robert Moskowitz wrote: >=20 >=20 > On 8/26/19 8:44 AM, Henrik Levkowetz wrote: >> Hi, >> >> This is an automatic notification about a new xml2rfc release, >> v2.25.0, generated when running the mkrelease script. >=20 > Notes on my experience with the upgrade: >=20 > I get the standard warning: >=20 > DEPRECATION: Python 2.7 will reach the end of its life on January 1st, = > 2020. Please upgrade your Python as Python 2.7 won't be maintained afte= r=20 > that date. A future version of pip will drop support for Python 2.7. >=20 > I have both Python2 and 3 installed on my Fedora 30 system. This warning indicates either that the default python is still 2.7, or that the pip command you are running is symlinked to pip-2.7. > What is causing this message? An old version of pip or xml2rfc? Pip. The pip that comes with Python 2.7 gives the warning above. Irrespective of which pip and python you use (2.7, 3.5, 3.6, 3.7), the installed version of xml2rfc now supports vocabulary v3. > Is there a way to install xml2rfc v3 to start checking it out without=20 > loosing v2? xml2rfc v2 and v3 are supported by the same install. In order to produce= v3 output, use 'xml2rfc --v3 ...'. In order to convert your v2 xml files= to v3 xml, use 'xml2rfc --v2v3 ...'. Note that when speaking about 'v3' xml2rfc, there is a certain need to indicate which aspect of xml2rfc v3 support you are referring to: There is both the matter of the v3 xml vocabulary, where many v2 construc= ts are deprecated; and there are the v3 formatters, which are completely rewritten to handle the v3 xml. Now, having made that clear, I'm afraid that the following may cause some= blurring again, but it's been done in the interest of making forward prog= ress easier: If you invoke one of the v3 formatters, by saying for instance 'xml2rfc --v3 --text ...', but your input file uses deprecated v2 element= s, those will be quietly converted internally, using the v2-to-v3 converter,= and then handed to the v3 formatter. This of course adds a bit of magic to the process, and you will have better control of your output if you wo= rk with clean v3 input files. Converting your v2 files to v3 with --v2v3 sh= ould give you a good starting point for that. I hope that helps. Best regards, Henrik --UTdde9L09V53ff77kpQhqw7DdQOHsew7N-- --UubANVQJxgQHShtJDdGRSO3mA8vawaO1X Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl1oNHMACgkQTptXS4+7 FxrFfg/+K7K0V8jSci6DU1xNAbu5UnLuh6xtq1rI5S8BpR0+PsEJe8FAVIl23COu a1fmOcJEGHvVMSJybzjq+MIXZcHo8PS2SetzZXs8fnxJCxsOAJ381Lcz0Oj56zC8 6AeAqdoIMzG6lYGJvtG6UNefOr5jCdP/FoLVxTa6TzGLLKQYc3+Fz6sW8LDoliB/ n13sM3QeTjLzZHh198FYn1NDo2zF9fifDB0TVA5W3zqOvvPPWZsOjvI3FWsWAFau GriwlCWehf821FYzAWXeGNDHCvtdCqX7Fj2y9FGY7Zf1kXG5O+49jIN44cwFZn+K BsBCfmiXgXDU9qjoLQpW5jlbRselMBDsrpqjSQuTO7eMp9PtgnYuWn4/YkW7vgDm 2dwi6T863sl3ibOVcsQreCkce9KWy3rxcC0/6Zjmazcy6k/F7PfvVsUWsagLqGI/ or1P5ClHBw7RIhhGWPbIeSP50bAgfBOyxNNCJXJ08ajl+AjMPCQLj4WrUTYXzsPd JvX9JoGHvQqPeTN/m3q2W85GKJlur0tBD/IoK0d6K1a3NBhbkcSqJ5va8baplHj6 ZS8pKHAijcdfQYPVoc2ZfZ1LAidGUd6+/NzjB9nd9StttmxZgMwnf/ZYbIZ7JTDP T76WSLykRUnn3qYiWAuVCfuF3hzgIH5jCrHUhhZfluPGGupYuo4= =+rNL -----END PGP SIGNATURE----- --UubANVQJxgQHShtJDdGRSO3mA8vawaO1X-- From nobody Thu Aug 29 13:26:27 2019 Return-Path: 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 F0D72120C14; Thu, 29 Aug 2019 13:26:13 -0700 (PDT) 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 PvNb6a_BgOxR; Thu, 29 Aug 2019 13:26:12 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EF2912001B; Thu, 29 Aug 2019 13:26:12 -0700 (PDT) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:60571 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1i3Qzj-000411-KB; Thu, 29 Aug 2019 13:26:12 -0700 To: Robert Moskowitz , xml2rfc-dev@ietf.org, xml2rfc@ietf.org References: Cc: rfc-markdown@ietf.org From: Henrik Levkowetz Message-ID: <53c88f77-a4e6-7ef5-9bd4-5de18a23f3e8@levkowetz.com> Date: Thu, 29 Aug 2019 22:26:03 +0200 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: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="oAgJ6ShEAo49rHnF5gACaK9iuMMpHxs3C" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: rfc-markdown@ietf.org, xml2rfc@ietf.org, xml2rfc-dev@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: Subject: Re: [xml2rfc] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Aug 2019 20:26:14 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --oAgJ6ShEAo49rHnF5gACaK9iuMMpHxs3C Content-Type: multipart/mixed; boundary="BOIiGiQnlHrAIuakO7iBitodg71HMRVje"; protected-headers="v1" From: Henrik Levkowetz To: Robert Moskowitz , xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org Message-ID: <53c88f77-a4e6-7ef5-9bd4-5de18a23f3e8@levkowetz.com> Subject: Re: [xml2rfc] New xml2rfc release: v2.25.0 References: In-Reply-To: --BOIiGiQnlHrAIuakO7iBitodg71HMRVje Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I see Robert's responses landed while I was typing my response ,:-) On 2019-08-29 22:24, Henrik Levkowetz wrote: > Hi Bob, >=20 > On 2019-08-29 21:22, Robert Moskowitz wrote: >>=20 >>=20 >> On 8/26/19 8:44 AM, Henrik Levkowetz wrote: >>> Hi, >>> >>> This is an automatic notification about a new xml2rfc release, >>> v2.25.0, generated when running the mkrelease script. >>=20 >> Notes on my experience with the upgrade: >>=20 >> I get the standard warning: >>=20 >> DEPRECATION: Python 2.7 will reach the end of its life on January 1st,= =20 >> 2020. Please upgrade your Python as Python 2.7 won't be maintained aft= er=20 >> that date. A future version of pip will drop support for Python 2.7. >>=20 >> I have both Python2 and 3 installed on my Fedora 30 system. >=20 > This warning indicates either that the default python is still 2.7, or > that the pip command you are running is symlinked to pip-2.7. >=20 >> What is causing this message? An old version of pip or xml2rfc? >=20 > Pip. The pip that comes with Python 2.7 gives the warning above. >=20 > Irrespective of which pip and python you use (2.7, 3.5, 3.6, 3.7), > the installed version of xml2rfc now supports vocabulary v3. >=20 >> Is there a way to install xml2rfc v3 to start checking it out without = >> loosing v2? >=20 > xml2rfc v2 and v3 are supported by the same install. In order to produ= ce > v3 output, use 'xml2rfc --v3 ...'. In order to convert your v2 xml fil= es > to v3 xml, use 'xml2rfc --v2v3 ...'. >=20 > Note that when speaking about 'v3' xml2rfc, there is a certain need to > indicate which aspect of xml2rfc v3 support you are referring to: >=20 > There is both the matter of the v3 xml vocabulary, where many v2 constr= ucts > are deprecated; and there are the v3 formatters, which are completely > rewritten to handle the v3 xml. >=20 > Now, having made that clear, I'm afraid that the following may cause so= me > blurring again, but it's been done in the interest of making forward pr= ogress > easier: If you invoke one of the v3 formatters, by saying for instance= > 'xml2rfc --v3 --text ...', but your input file uses deprecated v2 eleme= nts, > those will be quietly converted internally, using the v2-to-v3 converte= r, > and then handed to the v3 formatter. This of course adds a bit of magi= c > to the process, and you will have better control of your output if you = work > with clean v3 input files. Converting your v2 files to v3 with --v2v3 = should > give you a good starting point for that. >=20 > I hope that helps. >=20 >=20 > Best regards, >=20 > Henrik >=20 >=20 >=20 > _______________________________________________ > xml2rfc mailing list > xml2rfc@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc >=20 --BOIiGiQnlHrAIuakO7iBitodg71HMRVje-- --oAgJ6ShEAo49rHnF5gACaK9iuMMpHxs3C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl1oNNsACgkQTptXS4+7 FxrSWQ//bKMC94ovgEAzIY6bqMkI9ZT0vO6bfQNVw6KSCwRcUaciie6GmCvy5lwT sb1/sO2HtNr+fKZ6dADAeRp4hQHCR3jimN2WmkYvapJuzQrvnOPENSzl7KScfBg3 pvdVN3ymqmp6MQwZ0UZGVgRWW4xvV01YAzQiP4VmcTYnUcvIgT1z5PXH7KFEivU7 Aj4Ae+sxMZ4K7/YLSyaIxOvZLFVno+xTT9qbu3ZIEBybn6WQZlMleTB8qB5OhNlo 0+u1jQOtEidsLEKZxkrMVwLFgInTr/VORvqxr4QD9VkrFDthaLs4S0+Cl9Snf++P FYZxzAtMcM5NBX1VsTfXxj32EU+psvmS6ylCcA7WIzGyg5eUdghNZ4ULQ7tNHWKS 8r9nktMdneVsPdR0gorH0SAR5IXojdOGXihpgMp5kBBLeLIIHAXZsWjVHxiGptBB 2HDokERjriRAMkb4Hb/6yjzyW3MPcGnWgTv0CvfHqRvcspmFyqsruUtu1qSF8dF6 zTLU4gdEKy74YZK5Y8mbPbyDcQ8efnGLVHbfGmHHpu87hLd5YmiiUxujdQKQO9TX mbDDpiGkv0ZCYBdmYcCxvmF+bPlVT27mdktKBtsqK5gzkDs+MJ7sspPuayvubfKo gKMYeR4GmBUyI647YxTUVgeJVfLBkXWmJ/JJEiU1c4uUvGew5iA= =qSDs -----END PGP SIGNATURE----- --oAgJ6ShEAo49rHnF5gACaK9iuMMpHxs3C-- From nobody Thu Aug 29 13:49:39 2019 Return-Path: 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 2B014120077; Thu, 29 Aug 2019 13:49:24 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 U_xO_Tr4iUGK; Thu, 29 Aug 2019 13:49:22 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B24EA120073; Thu, 29 Aug 2019 13:49:22 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id B976F6211C; Thu, 29 Aug 2019 16:49:20 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id dlENU0EwTcX7; Thu, 29 Aug 2019 16:49:13 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 083E062110; Thu, 29 Aug 2019 16:49:12 -0400 (EDT) To: Henrik Levkowetz , xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org References: From: Robert Moskowitz Message-ID: <8fdc91d2-a683-eb4d-04f1-ade8e424436f@htt-consult.com> Date: Thu, 29 Aug 2019 16:49:03 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [xml2rfc] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Aug 2019 20:49:24 -0000 On 8/29/19 4:24 PM, Henrik Levkowetz wrote: > Hi Bob, > > On 2019-08-29 21:22, Robert Moskowitz wrote: >> >> On 8/26/19 8:44 AM, Henrik Levkowetz wrote: >>> Hi, >>> >>> This is an automatic notification about a new xml2rfc release, >>> v2.25.0, generated when running the mkrelease script. >> Notes on my experience with the upgrade: >> >> I get the standard warning: >> >> DEPRECATION: Python 2.7 will reach the end of its life on January 1st, >> 2020. Please upgrade your Python as Python 2.7 won't be maintained after >> that date. A future version of pip will drop support for Python 2.7. >> >> I have both Python2 and 3 installed on my Fedora 30 system. > This warning indicates either that the default python is still 2.7, or > that the pip command you are running is symlinked to pip-2.7. > >> What is causing this message? An old version of pip or xml2rfc? > Pip. The pip that comes with Python 2.7 gives the warning above. > > Irrespective of which pip and python you use (2.7, 3.5, 3.6, 3.7), > the installed version of xml2rfc now supports vocabulary v3. I just asked on the Fedora list.  I am suppose to be running pip3, not just pip.  There is also a  pip2, but don't use it as it is the same as pip. The default version is still 2.7: $ python --version Python 2.7.16 But Python3 is installed.  I am going to have to dig more.  Just for my own 'sanity'.  Ha! > >> Is there a way to install xml2rfc v3 to start checking it out without >> loosing v2? > xml2rfc v2 and v3 are supported by the same install. In order to produce > v3 output, use 'xml2rfc --v3 ...'. I tried this with both drafts that are 'ready' and both gave me the warning: draft-moskowitz-hip-hierarchical-hit-00.xml(14): Warning: Setting consensus="true" for IETF STD document (this is not the schema default, but is the only value permitted for this type of document) I need to find where 'consensus' is explained. > In order to convert your v2 xml files > to v3 xml, use 'xml2rfc --v2v3 ...'. From what you say below, this is something I should do.  I also foresee a possible challenge in that I do a lot of copy and paste from old drafts to new, and I could end up dragging something into converted draft that is not for v3 from an unconverted old file. Actually I have a number of drafts in various stages.  Ugh. > > Note that when speaking about 'v3' xml2rfc, there is a certain need to > indicate which aspect of xml2rfc v3 support you are referring to: > > There is both the matter of the v3 xml vocabulary, where many v2 constructs > are deprecated; and there are the v3 formatters, which are completely > rewritten to handle the v3 xml. > > Now, having made that clear, I'm afraid that the following may cause some > blurring again, but it's been done in the interest of making forward progress > easier: If you invoke one of the v3 formatters, by saying for instance > 'xml2rfc --v3 --text ...', but your input file uses deprecated v2 elements, > those will be quietly converted internally, using the v2-to-v3 converter, > and then handed to the v3 formatter. This of course adds a bit of magic > to the process, and you will have better control of your output if you work > with clean v3 input files. Converting your v2 files to v3 with --v2v3 should > give you a good starting point for that. > > I hope that helps. > > > Best regards, > > Henrik > From nobody Thu Aug 29 21:22:14 2019 Return-Path: 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 02CBC120C70; Thu, 29 Aug 2019 21:22:01 -0700 (PDT) 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 nXHl50WKfNQP; Thu, 29 Aug 2019 21:21:59 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (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 E9952120918; Thu, 29 Aug 2019 21:21:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1567138893; bh=qmL4bKZhiHqC8EGW9lJvZgukai5AuLA7hkoIFc1IDEc=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=IInp13ctyyblP+Ya1g19vogFh6n8ECrZ/cJyWf7vZf6GMWWrlPZuW4xvW1k+gejbf 4TI1SRaGtB8CBGVXOuixSeuKtyqTx26IKduS5dfLUaM6WBsGgGCDXnH/u6l0LLCnaH oqlTd6C33OfEJbQrki/g1+3g+aRCNQDo2A8wUDss= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.124] ([84.171.150.109]) by mail.gmx.com (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1M3DNt-1i2jb61UZZ-003dQo; Fri, 30 Aug 2019 06:21:33 +0200 To: Robert Moskowitz , Henrik Levkowetz , xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org References: <8fdc91d2-a683-eb4d-04f1-ade8e424436f@htt-consult.com> From: Julian Reschke Message-ID: <3646d280-9e8c-9b90-093d-9dd36967fc7a@gmx.de> Date: Fri, 30 Aug 2019 06:21:27 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <8fdc91d2-a683-eb4d-04f1-ade8e424436f@htt-consult.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:ktqbJTiHgf2B5OCBh7Ekny/SDhVSRX7Kq98NNcAdL4coJSmYjrP 8OR9dAC4z2QoHjwjScFwdqSV4Ku0r3DTvrm7nU2lv3BbUvLNyI9TBR+bB7ic9NhhHrFefMK 0TTIvZg4YQ1MqrCLYH40ndQq2+Mva8iaxif6CALB4ugUaLZ/sDe1iM2B+KKXX3EDxbnWYm0 6jCwrtjP96t+oV0Ux/eVg== X-UI-Out-Filterresults: notjunk:1;V03:K0:M2qX8zWlcrA=:61J/DXa/WGwl+nlFpvfBm4 HYlAYoa1CCBkHmAduU6GnAEORtA/MQmPviniSwvZqVqnuL2YzV+jftHGFMe5WI09RWWfXqiUv LDT+wuQ+QI/oAtPopbj0d5GBQHhD0cNHM9fc/cHbL3mW/gRQR8BOnqlRNW6aoYMVHNYME3KyE cI0wnQhp2fv8Cd6OsbfXbWeSNbMJ1kMh2iELbv6kxFlcar3SHGVddqxmygPH9FzQo1ZW5XGe5 qPBQfsIW6uhJfsFTXavuyo+6pOXYLwCLiu/rEiqMZAvGgv3amoVH4wBJlBuKYArZ7gCk4iBTn odFAHkEE0IsYfRxvxgu0ns5nD/2AXFpFOSkcsnhEzGJAyqnXmrgbxtPoHMmuUpmQ/yxZ15OnB bzV8UmVvZwP4iH4zo7uLWsEF0lm9J/8FpAivLIZvkluWTPMI4qreh3LS7MOca4zQQee8JP2YO UtvfVXbSEC9ulBnHWhin277yMfDdX9WC8G5Mgsm0l6d9ahD4nZ/Bgvho4rBKUW51NYdTaisNj WzanvyEUVVKVH9tC3EWd0cp9lb0BIRPL/mORx6P5JeO+ZQE5AVGFEXUJLBlKkmZKpMXuH0B2B me4ZySj9Ds6BjAt79B8YFMsDEU0aV3SeN2U8Q9zkbYKKILyc625z0c6UwWBABtNjrYkKv2G9x y+ZZP2ahCrJfJl0FYn59BvKeZ+VJB8StOjmjYey94yTQikTDqsZnJbGGVwqfyb598f2tp0AQ1 OAw/sAcHOk0sGsA9AqCC8/qkKHboFXX4npeu+EMNLDY9NF4TvyozJazPAMLZgDNIR2hXMVZcq F1omvIq2Ha2g0Lyw+JbTZdhrwySqGKIhR/evjnCu1VZEqk/JTRt97hKqrLnA3IanhlCxSiwd4 GMHNhlu/TbFX7yJWT+4BwFX6NrpQg3xgHg1/Ra2y9tg3bDJFQIXnmPsoi3zo/yfWuZ9owd3eF 5KzTgXp43wbqUNseFqSe3gVLDEy9MLZn1dZOBYrL7RBCeXhnwKKEJOEXvbnTOr8LGe90oqcn4 +xNUBAd/ePnpwdv+mttFufCSxhh9HYmcXfjfx4poyquJ5dMB6u/T4+3tQL/4iu1egjWZOB+CF Rm/a8megyYEsTDODckoH/8VQuBrBrWhDGfolhaKNEpkUdFoOPPm8Taz225afg1KRVUTnWxEO/ ixjbw7xWU3L1O4LPYZbNNN0PhT20mRzG2f3SoohVqNd05Hsw== Archived-At: Subject: Re: [xml2rfc] [Rfc-markdown] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2019 04:22:01 -0000 On 29.08.2019 22:49, Robert Moskowitz wrote: > ... > I tried this with both drafts that are 'ready' and both gave me th= e > warning: > > draft-moskowitz-hip-hierarchical-hit-00.xml(14): Warning: Setting > consensus=3D"true" for IETF STD document (this is not the schema default= , > but is the only value permitted for this type of document) > > I need to find where 'consensus' is explained. > ... FWIW, I'm not sure the Warning is correct since this is still an Internet Draft. Best regards, Julian From nobody Thu Aug 29 21:43:52 2019 Return-Path: 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 029FB120C99; Thu, 29 Aug 2019 21:43:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.197 X-Spam-Level: X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 rwzgUYHJJRSY; Thu, 29 Aug 2019 21:43:34 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA340120C97; Thu, 29 Aug 2019 21:43:33 -0700 (PDT) Received: from [192.168.217.110] (p548DCCB9.dip0.t-ipconnect.de [84.141.204.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 46KRgl55GyzyVX; Fri, 30 Aug 2019 06:43:31 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Carsten Bormann In-Reply-To: <3646d280-9e8c-9b90-093d-9dd36967fc7a@gmx.de> Date: Fri, 30 Aug 2019 06:43:31 +0200 Cc: Robert Moskowitz , Henrik Levkowetz , XML Developer List , xml2rfc@ietf.org, rfc-markdown@ietf.org X-Mao-Original-Outgoing-Id: 588833009.695919-8292c184bd2493bc976f269c245e600e Content-Transfer-Encoding: quoted-printable Message-Id: <59EADF98-C4C3-4F82-9534-AB706199CB4F@tzi.org> References: <8fdc91d2-a683-eb4d-04f1-ade8e424436f@htt-consult.com> <3646d280-9e8c-9b90-093d-9dd36967fc7a@gmx.de> To: Julian Reschke X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [xml2rfc] [xml2rfc-dev] [Rfc-markdown] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2019 04:43:36 -0000 On Aug 30, 2019, at 06:21, Julian Reschke wrote: >=20 >> I need to find where 'consensus' is explained. >> ... >=20 > = I=E2=80=99m not sure whether you are serious when you say the attribute = is =E2=80=9Cexplained=E2=80=9D there. Yes, there is text about this attribute. No, it is not explained. The reference to 7841 just points to more text about =E2=80=9Cconsensus=E2= =80=9D there, but not about the meaning of this attribute. Gr=C3=BC=C3=9Fe, Carsten From nobody Thu Aug 29 21:46:14 2019 Return-Path: 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 5464D120C9B; Thu, 29 Aug 2019 21:46:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.197 X-Spam-Level: X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 WVr-vsT6kIDy; Thu, 29 Aug 2019 21:46:03 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA3EB120C9A; Thu, 29 Aug 2019 21:46:02 -0700 (PDT) Received: from [192.168.217.110] (p548DCCB9.dip0.t-ipconnect.de [84.141.204.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 46KRkd3kjJzyVb; Fri, 30 Aug 2019 06:46:01 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Carsten Bormann In-Reply-To: <8fdc91d2-a683-eb4d-04f1-ade8e424436f@htt-consult.com> Date: Fri, 30 Aug 2019 06:46:01 +0200 Cc: Henrik Levkowetz , xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org X-Mao-Original-Outgoing-Id: 588833159.522516-bedb8df44ee44b0403857f2bb4e6c74a Content-Transfer-Encoding: quoted-printable Message-Id: References: <8fdc91d2-a683-eb4d-04f1-ade8e424436f@htt-consult.com> To: Robert Moskowitz X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [xml2rfc] [xml2rfc-dev] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2019 04:46:05 -0000 On Aug 29, 2019, at 22:49, Robert Moskowitz wrote: >=20 > I also foresee a possible challenge in that I do a lot of copy and = paste from old drafts to new, and I could end up dragging something into = converted draft that is not for v3 from an unconverted old file. For the next decade or so, the v2v3 avenue is going to be the one that = many drafts will use. Going for v3 only source gives you more control (maybe; some of this = control is wrested away from you in the preptool), but has little = practical value to most RFC authors in an organization where documents = take 3 to 7 years to gestate. Gr=C3=BC=C3=9Fe, Carsten From nobody Thu Aug 29 21:54:38 2019 Return-Path: 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 AC308120C9C; Thu, 29 Aug 2019 21:54:22 -0700 (PDT) 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 UF7mMiEAZ3QX; Thu, 29 Aug 2019 21:54:20 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 F35561200E3; Thu, 29 Aug 2019 21:54:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1567140820; bh=lyBRydSkgnxPq/pVXz/7lqebeOVJkDfohXSgbH+GVfA=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=h2tuwbL3pn908Q3d0W5fYAVMxz4YnPMk/IhQoG3CWQvQ6cXVco3f6ZED+TCbp1n4Z q1dE9K+xD/i6XGnCeYFpdDayV9F2qVijo1/rQLpBTn1BYexw7welltnszKl9zNRZqe ppYTi5rWY7+qZqtcqINqhZit8oAVcqUsDd1FVof8= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.124] ([84.171.150.109]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0M1FAK-1iIsoO2q08-00tDSF; Fri, 30 Aug 2019 06:53:40 +0200 To: Carsten Bormann Cc: Robert Moskowitz , Henrik Levkowetz , XML Developer List , xml2rfc@ietf.org, rfc-markdown@ietf.org References: <8fdc91d2-a683-eb4d-04f1-ade8e424436f@htt-consult.com> <3646d280-9e8c-9b90-093d-9dd36967fc7a@gmx.de> <59EADF98-C4C3-4F82-9534-AB706199CB4F@tzi.org> From: Julian Reschke Message-ID: <8be273dd-6692-99d2-9162-20a7a3515605@gmx.de> Date: Fri, 30 Aug 2019 06:53:38 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <59EADF98-C4C3-4F82-9534-AB706199CB4F@tzi.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:aLbbaErfE9a6y4Fjgbj1VCH3fpy+XyFuy9W2FDZMXm88HCX9EyD fhOqvY5c6+5oTRETMJ1icSebKx83uEUuokSoJ6zIR41jISorrWBf1DjaD2DNM0PZdqQxFn+ LHBoVT8rWXRcXftkrkU9CTKh+I8vqoPA+RZW3KqDNO82S1aOXKOeXnGn4v6Ig6lvJNk6wdn WY7/SuHrhS6SgYR1KnShg== X-UI-Out-Filterresults: notjunk:1;V03:K0:24tp7r8pv7o=:xlTXfBjEZWOL7W4WZz7G/W pO91TUEU99Snlk+W7ULkOPnBrtcYEvnRJ/Ox3yHI2DXXlfylzkgcyqrAXQ/cxpvbE+FNlli9K vEqTb+No8jHGXW6ufUWlEDGjdKXqGJqqepGGyb3qomwnXR7i13Xz6ylRCEWiLMiNw+8AtjViM ZCdDX3pNaVRiCyRPtpDg73LZkCV3XDDo+FYuHxEKlpmm2PwrHozLrL0gQTmczt8htDYfv5+YV wfn72OGEhlbDvp9ScNPkHyaF2p7I7qTqx8Xwc5uLtp+31pbexSKVkjFlX9d2S1BFJr5/u42We 1c8EhzyMe430ZGz/JOb/RBx9kyppT7iTsftPkMyVs4E+vHVH886Rw9Jb7gNRJYMFdg/5DfeB1 Ff9pVJzH9G4swlZo6w6zdaYeL+H9UTLnEEPBk1krDzHpMJKdvFtXAYhBv0Unuc4kQHaoGID61 13wZPWdNBjunI9liBCc2rcq6symChI9UraH8spLxMnZJ4omN3qOWVxKnGfUAmMIRcYBbQhhj1 aiSEbnZM4KIj+QhvB7POiN51PcD0FPJSTmcbm0dEdUTtflqhlWf5i7NiLuBfuJ1w00AwWBCc3 uXSVMSEZhE2I8ykyRp59J58qTjcH9o2aoPCnW3oME29rjAXVul1rwO1LpbZ9Qn8NktJOHoa9W Rhlejm43+IxhbBCygMkcfamKm32cv93l35b75DPkNNw2Prf+MXhkdRD25W3zO/wLjfp/kzAPO HOEM++IXEXwUzA3i75wq9ef715Vag4OZmEzjS1BOQXgSyFE3rHZVX4A59LXTl65i92RfQNDQ9 8Bgrw9b4sEatzCb6TRhI+oiR8sn1xh7/WWgAO/l0xiszmf8oazFz5vk5RMADo7G1I7XRVAbsA etqefYLd9/+M0vLG9T/D9lVkJUV16XQQccHtinF/oG9rRbTgs5VrxdSOE8vaZrNhdfaj0Hlit rZwoQWIMsRKM4chnhnR4WNUaqrwqmhQIjuoVUX5m8dMbEG0j5JtyJGuPea7lcUcOW6Rt9UnJW jgvBAnA1cODa8Z6DD8h9Su9xE+IJfKXYKeQvjgZ7zQKShAe1qhon1IiZuhbaQ+H9avqPlHXa2 BA6WVkvlf8Xd7WrwUspxys75MLSGNOLqyY9cY603rTV6xHPqstXMYTYbJpRG8CcFxzj8VeHKM 7EFQ62nTq14BahUbZoQr7NF6j+qrWWGoQqExrfdwfY5wE14g== Archived-At: Subject: Re: [xml2rfc] [xml2rfc-dev] [Rfc-markdown] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2019 04:54:23 -0000 On 30.08.2019 06:43, Carsten Bormann wrote: > On Aug 30, 2019, at 06:21, Julian Reschke wrote: >> >>> I need to find where 'consensus' is explained. >>> ... >> >> > > I=E2=80=99m not sure whether you are serious when you say the attribute = is =E2=80=9Cexplained=E2=80=9D there. > Yes, there is text about this attribute. > No, it is not explained. > The reference to 7841 just points to more text about =E2=80=9Cconsensus= =E2=80=9D there, but not about the meaning of this attribute. There's more text at ; and the main definition should reference that: > A.3. The "consensus" Attribute > > For some of the publication streams (see Appendix A.2), the "Status of T= his Memo" section depends on whether there was a consensus to publish (aga= in, see Section 3.4 of [RFC7841]). > > The consensus attribute can be used to supply this information. The acce= ptable values are "true" (the default) and "false"; "yes" and "no" from v2= are deprecated. > > The effect of this value for the various streams is: > > "independent": none. > "IAB": mention that there was an IAB consensus. > "IETF": mention that there was an IETF consensus. > "IRTF": mention that there was a research group consensus (where the= name of the research group is extracted from the element). Best regards, Julian From nobody Thu Aug 29 21:57:49 2019 Return-Path: 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 6D984120CA4; Thu, 29 Aug 2019 21:57:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.197 X-Spam-Level: X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 JNm3euNa2YKC; Thu, 29 Aug 2019 21:57:39 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C86A0120C83; Thu, 29 Aug 2019 21:57:38 -0700 (PDT) Received: from [192.168.217.110] (p548DCCB9.dip0.t-ipconnect.de [84.141.204.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 46KS012jLjzyt5; Fri, 30 Aug 2019 06:57:37 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Carsten Bormann In-Reply-To: <8be273dd-6692-99d2-9162-20a7a3515605@gmx.de> Date: Fri, 30 Aug 2019 06:57:37 +0200 Cc: rfc-markdown@ietf.org, xml2rfc@ietf.org, Robert Moskowitz , XML Developer List , Henrik Levkowetz X-Mao-Original-Outgoing-Id: 588833855.532173-3bf84cf4f2fb3f91d3a56887a5c17733 Content-Transfer-Encoding: quoted-printable Message-Id: <187D822F-476C-4157-A1C8-8C71600B232C@tzi.org> References: <8fdc91d2-a683-eb4d-04f1-ade8e424436f@htt-consult.com> <3646d280-9e8c-9b90-093d-9dd36967fc7a@gmx.de> <59EADF98-C4C3-4F82-9534-AB706199CB4F@tzi.org> <8be273dd-6692-99d2-9162-20a7a3515605@gmx.de> To: Julian Reschke X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [xml2rfc] [Rfc-markdown] [xml2rfc-dev] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2019 04:57:41 -0000 On Aug 30, 2019, at 06:53, Julian Reschke wrote: >=20 >> A.3. The "consensus" Attribute That=E2=80=99s more useful, indeed. Thanks. Gr=C3=BC=C3=9Fe, Carsten From nobody Fri Aug 30 02:51:50 2019 Return-Path: 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 968F2120807; Fri, 30 Aug 2019 02:51:35 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 reUhshiDVZ1e; Fri, 30 Aug 2019 02:51:33 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C437012004F; Fri, 30 Aug 2019 02:51:32 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 70FF66211D; Fri, 30 Aug 2019 05:51:29 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id byiGXKqqJJqm; Fri, 30 Aug 2019 05:51:22 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 95848620D4; Fri, 30 Aug 2019 05:51:21 -0400 (EDT) To: Julian Reschke , Carsten Bormann Cc: Henrik Levkowetz , XML Developer List , xml2rfc@ietf.org, rfc-markdown@ietf.org References: <8fdc91d2-a683-eb4d-04f1-ade8e424436f@htt-consult.com> <3646d280-9e8c-9b90-093d-9dd36967fc7a@gmx.de> <59EADF98-C4C3-4F82-9534-AB706199CB4F@tzi.org> <8be273dd-6692-99d2-9162-20a7a3515605@gmx.de> From: Robert Moskowitz Message-ID: <493d4dc2-ae06-e7da-3ca2-810ab889c7e1@htt-consult.com> Date: Fri, 30 Aug 2019 05:51:09 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <8be273dd-6692-99d2-9162-20a7a3515605@gmx.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [xml2rfc] [xml2rfc-dev] [Rfc-markdown] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2019 09:51:36 -0000 On 8/30/19 12:53 AM, Julian Reschke wrote: > On 30.08.2019 06:43, Carsten Bormann wrote: >> On Aug 30, 2019, at 06:21, Julian Reschke wrote: >>> >>>> I need to find where 'consensus' is explained. >>>> ... >>> >>> >>> >> >> I’m not sure whether you are serious when you say the attribute is >> “explained” there. >> Yes, there is text about this attribute. >> No, it is not explained. >> The reference to 7841 just points to more text about “consensus” >> there, but not about the meaning of this attribute. > > There's more text at > ; > and the main definition should reference that: > >> A.3. The "consensus" Attribute >> >> For some of the publication streams (see Appendix A.2), the "Status >> of This Memo" section depends on whether there was a consensus to >> publish (again, see Section 3.4 of [RFC7841]). >> >> The consensus attribute can be used to supply this information. The >> acceptable values are "true" (the default) and "false"; "yes" and >> "no" from v2 are deprecated. >> >> The effect of this value for the various streams is: >> >>     "independent": none. >>     "IAB": mention that there was an IAB consensus. >>     "IETF": mention that there was an IETF consensus. >>     "IRTF": mention that there was a research group consensus (where >> the name of the research group is extracted from the >> element). > > Best regards, Julian Oh, Dear Lord, this is such a wonderful addition that captures the state of work.  It just calls out for an April 1 RFC!!!!! Is if fine grain enough.  What about design team consensus, or work group consensus, to Webster's definition of consensus to Oxford definition of consensus (boy was that a fun meeting of US and UK people back in '95!: "We have consensus here." "What are you saying, we do not consent to this proposal!"). Then if there is a consensus attribute, where is the running_code attribute.  How many interoperable versions? Oh the potential!!!! Carsten and Julian, are you up for an RFC on this one?    :) I would love to see your German take on the US vs UK discussions on tabling... Bob From nobody Fri Aug 30 03:03:20 2019 Return-Path: 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 1AB671200FF; Fri, 30 Aug 2019 03:03:13 -0700 (PDT) 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 X4d6rlnD7HbL; Fri, 30 Aug 2019 03:03:10 -0700 (PDT) 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 4EC7012004F; Fri, 30 Aug 2019 03:03:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1567159370; bh=vHr+LSM65+4r4RYoAxhvuASN6HP2Rpq5NYh8FUp5x/w=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=LuiDSPq2C9YARTxrsAbBkbzDusA89QXcmod6HHDn1bbsIZtIFJ4WFGE63J65CXZSn urO/L86uqaYEbQXNPiO0p0YJ4X9K1up5bBpKbx6SQ+7oWhwOXqYuf2UTPg+Coj/yqk YYLFD/VBBxZ4HI/RMVm7QDN4qqHnoshkitE/NgJk= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.1.34] ([217.91.35.233]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M08eS-1iJwAe3PhM-00uJrl; Fri, 30 Aug 2019 12:02:50 +0200 To: Robert Moskowitz , Carsten Bormann Cc: rfc-markdown@ietf.org, xml2rfc@ietf.org, XML Developer List References: <8fdc91d2-a683-eb4d-04f1-ade8e424436f@htt-consult.com> <3646d280-9e8c-9b90-093d-9dd36967fc7a@gmx.de> <59EADF98-C4C3-4F82-9534-AB706199CB4F@tzi.org> <8be273dd-6692-99d2-9162-20a7a3515605@gmx.de> <493d4dc2-ae06-e7da-3ca2-810ab889c7e1@htt-consult.com> From: Julian Reschke Message-ID: <3719c563-05a1-ec26-0375-bea2d45848c4@gmx.de> Date: Fri, 30 Aug 2019 12:02:45 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <493d4dc2-ae06-e7da-3ca2-810ab889c7e1@htt-consult.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:x5g1+L2EbKZexBLF+McCmH3FUlOgLBYLE7D9owu62w04iKVux3f 3P6I/Gz8hdpO4pkQ8/Bld+L6ZhPxly96X20LwG8mXnmWAYVslzUR3dOW87sLlsNGheBNFRD 7Ec60zEpkBX0PSTapVeVAdpkQrMsoEJBUekR8qYIo8M82D0ZwXV4kuByYuBrKWRf1OpMcwC zRz6Jcvpcadgdoj50pvJA== X-UI-Out-Filterresults: notjunk:1;V03:K0:RrPXgULiDRU=:AQe7ZqoF3y+BmMqq3ksfxp slfsHqF+xPx5oE2zMbmnuw8I75kOZtoDpJlowrn0riQSFCIl5LXzHWWiFFvw9gbywNkRf9Fh6 JOtqdxNzAgf5joXQzBay01FdNkqfeYwnzuH7Fwf/8sogK4JWD0RPuB3lntdribXvOdHCxF8uP OP0vqeJVaWeLXwduc2kutjXdyI/PbfEEhXPtj/6juMoe0N3MHyhV/XMK5KrR0ZhzIbmWRhi8z ZPHva9dGHNiWegPniAhzL+EJjhGzYesHFo2ZwGXyoTIXu01t4A9zmzhv2/1mkyda4Fv2SJlGN QNu4BJQ4QDNRxZreRsNud6h+42WzRVf1RE05K8i25dFiFNka3c25LYxZjiJpu74MSWmCVYGVO JkqCgxth441S930rr+cTUPBZ0f/y/zNpKfGzaTetw/F6CWKukt9IUsr4ytWSfqp6BgbtL+K9f SEty7K3ifhNHFOP6fk/oB9xdmQoSU+wPRDtBKLmddUz9ab0Fq6QmqoqhKhpvb8wYaNep2QTiw poXYQsYsvgsfJyWjVWzXaMAsm/41X0b/P3+T5IlIxQFPvFI5I3gfHspP3+5cGgGxPF2Tpo3AX Kae4EZMVdUFTnClhe//HF8LnMGAScLCpp5kjfadiclw1DhVV0bxAH1YfOCovlnEUopnvP4u9V qDk78HR3QOcFoGUsgpeGVH+krdEkQuTaKYqCp86dCqfdF3IiJO4n+AoI3xLF8zY0X6EvBEX7M CzZXHmmU+LN3oYRWcDNq6ovzMLOdapYc5DMnWycWsmRKQ7b1VKHMr1oAAhlgOeog8BDzq+wgJ Z54Gh42IEhL9e+0PJrMif/Q3ZSlOTeDsS086GYseagTUj2Uc6JWcq+AAiWu+qoLjDuek42vrs h4AKV45yHOliwFwswLwwr6fTxsvxw7eIcG9GvjHzuyaKmBXzp8hj2ryToOf2FZ5xOcTOq8cwF SMXk6bSjp70wkKucfUhTZBcVPrc0jm6tPzYCayVtRXlnu15EpOJqmV0I1uljoDvSfiI3o06v2 HIX0+SKkLWXzYQsCWpjW1oWMGCTWNo4+a1HsCBM8sAiCVka1zKk97iLGn+bPHrEj42QURnZK8 CVaa/I/r12AUlOwadGRY7NRdQcyAYfko6WAqoPs5Jx4RWNfF7RK82W11QcHOEKVrg3eBdIOr9 2VeXrHgA4MW5nrLgfVtbFdb8s3kr0WfT9rpwTg1gsmHB4b8w== Archived-At: Subject: Re: [xml2rfc] [xml2rfc-dev] [Rfc-markdown] New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2019 10:03:13 -0000 On 30.08.2019 11:51, Robert Moskowitz wrote: > > > On 8/30/19 12:53 AM, Julian Reschke wrote: >> On 30.08.2019 06:43, Carsten Bormann wrote: >>> On Aug 30, 2019, at 06:21, Julian Reschke wrot= e: >>>> >>>>> I need to find where 'consensus' is explained. >>>>> ... >>>> >>>> >>>> >>> >>> I=E2=80=99m not sure whether you are serious when you say the attribut= e is >>> =E2=80=9Cexplained=E2=80=9D there. >>> Yes, there is text about this attribute. >>> No, it is not explained. >>> The reference to 7841 just points to more text about =E2=80=9Cconsensu= s=E2=80=9D >>> there, but not about the meaning of this attribute. >> >> There's more text at >> ; >> and the main definition should reference that: >> >>> A.3. The "consensus" Attribute >>> >>> For some of the publication streams (see Appendix A.2), the "Status >>> of This Memo" section depends on whether there was a consensus to >>> publish (again, see Section 3.4 of [RFC7841]). >>> >>> The consensus attribute can be used to supply this information. The >>> acceptable values are "true" (the default) and "false"; "yes" and >>> "no" from v2 are deprecated. >>> >>> The effect of this value for the various streams is: >>> >>> =C2=A0=C2=A0=C2=A0 "independent": none. >>> =C2=A0=C2=A0=C2=A0 "IAB": mention that there was an IAB consensus. >>> =C2=A0=C2=A0=C2=A0 "IETF": mention that there was an IETF consensus. >>> =C2=A0=C2=A0=C2=A0 "IRTF": mention that there was a research group con= sensus (where >>> the name of the research group is extracted from the >>> element). >> >> Best regards, Julian > > Oh, Dear Lord, this is such a wonderful addition that captures the state > of work.=C2=A0 It just calls out for an April 1 RFC!!!!! > ... FWIW, this is not new at all. It has been around for at least nine years. What's new is just the (IMHO confusing) warning message. Best regards, Julian From nobody Fri Aug 30 04:03:11 2019 Return-Path: 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 B768212009C for ; Fri, 30 Aug 2019 04:03:09 -0700 (PDT) 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 UqwsK7YtgjSI for ; Fri, 30 Aug 2019 04:03:08 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18022120086 for ; Fri, 30 Aug 2019 04:03:08 -0700 (PDT) Received: from localhost ([::1]:51027 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1i3egN-000124-5t; Fri, 30 Aug 2019 04:03:07 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com, julian.reschke@gmx.de X-Trac-Project: xml2rfc Date: Fri, 30 Aug 2019 11:03:07 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/420 Message-ID: <069.26414e7099ed8e843523ad395ba82b07@tools.ietf.org> X-Trac-Ticket-ID: 420 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, julian.reschke@gmx.de, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: [xml2rfc] #420 (Version 2 cli): misleading warning about missing consensus attribute for drafts X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2019 11:03:10 -0000 #420: misleading warning about missing consensus attribute for drafts {{{ Warning: Setting consensus="true" for IETF STD document (this is not the schema default, but is the only value permitted for this type of document) }}} This is causing confusion, as the value is irrelevant when producing an internet draft. -- -----------------------------------+---------------------------------- Reporter: julian.reschke@gmx.de | Owner: henrik@levkowetz.com Type: enhancement | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.25.* Keywords: | -----------------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Fri Aug 30 04:03:23 2019 Return-Path: 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 2C8F3120814 for ; Fri, 30 Aug 2019 04:03:21 -0700 (PDT) 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 Fop6EHfKcUiP for ; Fri, 30 Aug 2019 04:03:19 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A763120C9F for ; Fri, 30 Aug 2019 04:03:19 -0700 (PDT) Received: from localhost ([::1]:51042 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1i3egZ-0001xu-5A; Fri, 30 Aug 2019 04:03:19 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com, julian.reschke@gmx.de X-Trac-Project: xml2rfc Date: Fri, 30 Aug 2019 11:03:19 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/420#comment:1 Message-ID: <084.bc6e14384b6816002293e343acf34ba1@tools.ietf.org> References: <069.26414e7099ed8e843523ad395ba82b07@tools.ietf.org> X-Trac-Ticket-ID: 420 In-Reply-To: <069.26414e7099ed8e843523ad395ba82b07@tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, julian.reschke@gmx.de, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [xml2rfc] #420 (Version 2 cli): misleading warning about missing consensus attribute for drafts X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2019 11:03:21 -0000 #420: misleading warning about missing consensus attribute for drafts Changes (by julian.reschke@gmx.de): * priority: medium => trivial -- ------------------------------------+---------------------------------- Reporter: julian.reschke@gmx.de | Owner: henrik@levkowetz.com Type: enhancement | Status: new Priority: trivial | Milestone: Component: Version 2 cli | Version: 2.25.* Resolution: | Keywords: ------------------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Fri Aug 30 06:19:36 2019 Return-Path: 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 83F5D12003F; Fri, 30 Aug 2019 06:19:27 -0700 (PDT) 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 5pnXhi1jStIG; Fri, 30 Aug 2019 06:19:25 -0700 (PDT) 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 24BC212001E; Fri, 30 Aug 2019 06:19:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1567171145; bh=5aDzU+VloUJaZw0+49AUpusaNuXEHkz+9Yky2q+Ljfw=; h=X-UI-Sender-Class:Subject:From:To:References:Date:In-Reply-To; b=IgJGfu8cCL1iydyVtFyZB9VJkeZ9Opoh//ICGOx2FaoYSnxca3ASz3aRTf+3iE23+ oF6Hw9kN4BPqDdSHaTGS3RJJYfbrJo/x2Ym1nUtZmziFmvsqEt0aJC2C0XcA3dLiKj MNsxO0ago6php5AHCkH6HrAa+XFrqnnsB7dlqZ8s= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.1.34] ([217.91.35.233]) by mail.gmx.com (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MEm6L-1hxM5i1yDj-00GIQJ; Fri, 30 Aug 2019 15:19:05 +0200 From: Julian Reschke To: Henrik Levkowetz , xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org References: <22880345-a324-8dfd-a08c-e8ec89aeb9b5@gmx.de> <20190826144520.GA19037@miek.nl> <40d507f2-ed78-e09f-ae96-c64333a91547@levkowetz.com> <07f24586-9540-5170-e11c-9fca3c858b73@gmx.de> Message-ID: Date: Fri, 30 Aug 2019 15:19:03 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <07f24586-9540-5170-e11c-9fca3c858b73@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:Wi20KcNCrk/IGK5xKvvEpG7JJP7+f0gRZUo4QbKTm5ACYpJahFA PqxNeM83IyfOkFH3D6T2aZX6UokbJ96pauxMSyZ7H+KOwDX4ukBvv/Q+PjtuhGIHvkz6oIS XWFJEXBLZo+hww8jr9srnrHVEoqKXt7Rq8yKesPdcO46wfZwOQmrV/NW0wm2WL0hbvf9hQC ilCzkQGxh7kdz13CB98Ow== X-UI-Out-Filterresults: notjunk:1;V03:K0:IscyJEepwOI=:6nhlPwdha5/pMBAuDI8aMw bGCK9HdNKnIqbQMv/SfLdvodGM3sumb+3n6MwTVLMEsRnKkuUeZ2Y7OJjM9dYEbHzOLdWZqCs XEDukJQDL5ryJVFVPIL604h3N/K1czsQWMsd5eZMzr36xHtjkkz4/dYk2XK3BggeRh990/F4t sOX7IoyA94SrnBE9dypjDjFIGgU0Y7oZKMFIATjHTqfrQaPFm4zzUuswpSfX6r/gVBRUktZe8 s1Xh5noM3bpdUu+0KkuT3kfg0rRbSn35yRfyWISmTdAj4M8TN0XmjZyEJYXW2BobWLsuzc6H+ Jkkg7NzsFd5vOFCgSxPoDc4fVWUWTJ3wngMj5w2qVHDBSSLFdDvmWf7VXAYWnd3o0Yoa9pfub aab/ZM0OJhI3MskNND6ypWGkSJoCwC10eibIt46evACQ+D+mbInbEys6d2rJyZ6/BaJ4zKGgU rtF9u4KVfg/OWMMUO+jspQQSuu2PgnRQpIxf0PhoK/Gey4Ik0X6SZ9F+XJibNVMs75W1XxMIv fRFHTNyLa9ufX2Az0KcA5S4GBmiMEeDtKYVpdrDXaJvjgFHLAPC6LUgtnY/fM35pBwxlbboeo h6JPV8VpOeePDnfMmks1EO/8GWFKAr2ETM/E4U2VjwHQXYiWjJozMMcuGRtwQ/KRyhTyAyQZ+ 1nZl0j0fANrr5Ou5CqKFCXOnIsqMp9CpXXpqssFW7AAmTe0c986IFi9/M5aW8CQhoSIuKGmJV AY1jdWFDRMOjXq35cSSqOhacUgxEDxCbOu/3SJLo0hhWYElhPHoJV63ODvLf/RtStm1HB8E1s IS00G8eIeW1WRjzZFUu3TWo8IxvmKiWhFOgXHuzxsoCqJtSmiWK2TczsLW57co0sp+SRs8dae 11xujQ0tFhNLIjCix+NzLVH8FQDpuSsiFOo4/EFp2pA0oZJkWMJER94bdmbst5L6c5b31K0rd R2LmzMW/k3HXEnoX45Ubvfa2/wg6WVNa7/3ymrXY8cguyWaTxsgCi8u9ubQ2RcWVCYx08zakb F3uyAzVIIYHpIp1W6QH+Gv0LhsDlAi3qx5OakNmKn73Bl/MQTm3z2WWmigzXtGde9Ef83tmco TiQH8lqd5fmFR2P+T+2qtXSmL2vE7mLnG0Xyx4jAN9omKTo1GWpwDJQ2VIMTIRhr4T3845nfw Z/ty8XMTkx9e8IBCWZEa2jD0hsEqahVeFkO94zCAqhthKLHw== Archived-At: Subject: Re: [xml2rfc] [xml2rfc-dev] [Rfc-markdown] bcp14, was: New xml2rfc release: v2.25.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2019 13:19:28 -0000 On 26.08.2019 19:26, Julian Reschke wrote: > ... > If the sole reason for this change is to avoid breaking up MUST_NOT (and > friends), why not hard-wire that into the renderers (for HTML, I believe > it could be done with CSS...)? That will at least create consistency, > and avoid yet another task to deal with during AUTH48. > ... FWIW; this could be done with "white-space: nowrap" (see ). Best regards, Julian From nobody Fri Aug 30 06:28:00 2019 Return-Path: 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 3B43D1200CD for ; Fri, 30 Aug 2019 06:27:59 -0700 (PDT) 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 mfvXcSniJ0eQ for ; Fri, 30 Aug 2019 06:27:57 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A04351200B6 for ; Fri, 30 Aug 2019 06:27:57 -0700 (PDT) Received: from localhost ([::1]:53409 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1i3gwB-0004G7-6P; Fri, 30 Aug 2019 06:27:35 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com, julian.reschke@gmx.de X-Trac-Project: xml2rfc Date: Fri, 30 Aug 2019 13:27:22 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/420#comment:2 Message-ID: <084.6ac5c8a800b66ebe17ca7729acce07ae@tools.ietf.org> References: <069.26414e7099ed8e843523ad395ba82b07@tools.ietf.org> X-Trac-Ticket-ID: 420 In-Reply-To: <069.26414e7099ed8e843523ad395ba82b07@tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, julian.reschke@gmx.de, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [xml2rfc] #420 (Version 2 cli): misleading warning about missing consensus attribute for drafts X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2019 13:28:00 -0000 #420: misleading warning about missing consensus attribute for drafts Changes (by henrik@levkowetz.com): * status: new => closed * resolution: => invalid Comment: This is a direct consequence of the preptool phase and its RFC 7998 requirement to set attributes to their default values. Setting consensus to its default value would result in an invalid combination of category and consensus. I can remove the warning, but I don't see that doing so would make things better. -- ------------------------------------+---------------------------------- Reporter: julian.reschke@gmx.de | Owner: henrik@levkowetz.com Type: enhancement | Status: closed Priority: trivial | Milestone: Component: Version 2 cli | Version: 2.25.* Resolution: invalid | Keywords: ------------------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Fri Aug 30 06:38:50 2019 Return-Path: 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 874111200C4 for ; Fri, 30 Aug 2019 06:38:48 -0700 (PDT) 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 4Frsn8NvibfK for ; Fri, 30 Aug 2019 06:38:46 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B09951200B6 for ; Fri, 30 Aug 2019 06:38:46 -0700 (PDT) Received: from localhost ([::1]:53579 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1i3h6z-0003S1-LQ; Fri, 30 Aug 2019 06:38:45 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com, julian.reschke@gmx.de X-Trac-Project: xml2rfc Date: Fri, 30 Aug 2019 13:38:45 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/420#comment:3 Message-ID: <084.edf3d94b0e2217e98df579202c69d36a@tools.ietf.org> References: <069.26414e7099ed8e843523ad395ba82b07@tools.ietf.org> X-Trac-Ticket-ID: 420 In-Reply-To: <069.26414e7099ed8e843523ad395ba82b07@tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, julian.reschke@gmx.de, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [xml2rfc] #420 (Version 2 cli): misleading warning about missing consensus attribute for drafts X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2019 13:38:49 -0000 #420: misleading warning about missing consensus attribute for drafts Comment (by julian.reschke@gmx.de): > Setting consensus to its default value would result in an invalid combination of category and consensus. Why would it be invalid, in particular for the source of an Internet- Draft? (citation please) -- ------------------------------------+---------------------------------- Reporter: julian.reschke@gmx.de | Owner: henrik@levkowetz.com Type: enhancement | Status: closed Priority: trivial | Milestone: Component: Version 2 cli | Version: 2.25.* Resolution: invalid | Keywords: ------------------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Fri Aug 30 06:46:39 2019 Return-Path: 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 03BD01200F5 for ; Fri, 30 Aug 2019 06:46:38 -0700 (PDT) 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 Zaa2fYdu6-G6 for ; Fri, 30 Aug 2019 06:46:36 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EE0C1200B3 for ; Fri, 30 Aug 2019 06:46:36 -0700 (PDT) Received: from localhost ([::1]:53737 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1i3hEN-0001Of-Gs; Fri, 30 Aug 2019 06:46:29 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com, julian.reschke@gmx.de X-Trac-Project: xml2rfc Date: Fri, 30 Aug 2019 13:46:19 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/420#comment:4 Message-ID: <084.9288a2c4f39e235855ecb3ed62896210@tools.ietf.org> References: <069.26414e7099ed8e843523ad395ba82b07@tools.ietf.org> X-Trac-Ticket-ID: 420 In-Reply-To: <069.26414e7099ed8e843523ad395ba82b07@tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, julian.reschke@gmx.de, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [xml2rfc] #420 (Version 2 cli): misleading warning about missing consensus attribute for drafts X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2019 13:46:38 -0000 #420: misleading warning about missing consensus attribute for drafts Comment (by julian.reschke@gmx.de): FWIW, the consensus attribute did not have a default in rfc2629.dtd. Maybe the best fix would be to remove the default in v3 as well. -- ------------------------------------+---------------------------------- Reporter: julian.reschke@gmx.de | Owner: henrik@levkowetz.com Type: enhancement | Status: closed Priority: trivial | Milestone: Component: Version 2 cli | Version: 2.25.* Resolution: invalid | Keywords: ------------------------------------+---------------------------------- Ticket URL: xml2rfc From nobody Sat Aug 31 11:28:41 2019 Return-Path: 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 7196C1200FA for ; Sat, 31 Aug 2019 11:28:40 -0700 (PDT) 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 rG4aIyFwX435 for ; Sat, 31 Aug 2019 11:28:38 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDBCE1200F9 for ; Sat, 31 Aug 2019 11:28:38 -0700 (PDT) Received: from localhost ([::1]:59749 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1i4874-0005aY-9x; Sat, 31 Aug 2019 11:28:38 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.5 Precedence: bulk Cc: xml2rfc@ietf.org Auto-Submitted: auto-generated X-Mailer: Trac 0.12.5, by Edgewall Software To: henrik@levkowetz.com, ietf@augustcellars.com X-Trac-Project: xml2rfc Date: Sat, 31 Aug 2019 18:28:38 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/421 Message-ID: <070.3d8e972f20dc85fe0674858561f6081b@tools.ietf.org> X-Trac-Ticket-ID: 421 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, ietf@augustcellars.com, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: [xml2rfc] #421 (Version 2 cli): Duplicate displayreference names are allowed X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Aug 2019 18:28:41 -0000 #421: Duplicate displayreference names are allowed I put the following into a file and it did not complain. This should not be an allowed as it means that the reference is not unique. -- ------------------------------------+---------------------------------- Reporter: ietf@augustcellars.com | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.24.* Keywords: | ------------------------------------+---------------------------------- Ticket URL: xml2rfc