. Fixes issue #479. * Fixed a bug where text after was lost by the text formatter. Fixes issue #480 * Added an option to list recognised country names for use with , and changed the note() emitted for unrecognized countries to a warning. Added some new alternative country strings. * Updated test masters * Fixed a problem with entries with only information. Fixes issue #424. * Added a minimum width setting for tables, in order to avoid table captions rendering in very narrow space when the table itself is narrow. Fixes issue #482. * Avoid double space after initial when is rendered inline. Fixes issue #478. * Added code to recognise another case of inconsistent table row cell counts and report the issue. * Added 'P.R. China' as a recognized country name. * From Python 3.2 and later, cgi.encode() is deprecated. Changed to use html.encode() instead. -- Henrik Levkowetz 14 Jan 2020 18:08:08 +0000 The preferred way to install xml2rfc is by doing 'pip install xml2rfc', and 'pip install --upgrade xml2rfc' to upgrade. If there are system- installed python modules which pip will not upgrade, you may have to use 'pip install --upgrade --no-deps xml2rfc' and install dependencies manually. The new version is also available through SVN checkout, with 'svn checkout http://svn.tools.ietf.org/svn/tools/xml2rfc/tags/cli/2.38.0' Regards, Henrik (via the mkrelease script) From nobody Mon Jan 20 07:33:55 2020 Return-Path: X-Original-To: xml2rfc-dev@ietfa.amsl.com Delivered-To: xml2rfc-dev@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B75C012082B; Mon, 20 Jan 2020 07:33:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3ZcsD23KrNJh; Mon, 20 Jan 2020 07:33:43 -0800 (PST) Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F2E4120837; Mon, 20 Jan 2020 07:33:43 -0800 (PST) Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from ) id 1itZ3Q-0003b8-Q5; Mon, 20 Jan 2020 07:33:40 -0800 To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org Message-Id: From: Henrik Levkowetz Date: Mon, 20 Jan 2020 07:33:28 -0800 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-dev] New xml2rfc release: v2.38.1 X-BeenThere: xml2rfc-dev@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jan 2020 15:33:54 -0000 Hi, This is an automatic notification about a new xml2rfc release, v2.38.1, generated when running the mkrelease script. Release notes: xml2rfc (2.38.1) ietf; urgency=medium * Added a preptool check for numbered sections occurring after or under unnumbered sections, and changed the code for Reference sections to not emit section numbers if the previous section was unnumbered. Fixes issue #433 * Refactored the code for reference anchor to display string mapping, locating it in a base class method. Updated it to honour the symRefs setting. Fixes issue #476. * Added installation of Python 3.8 to Dockerfile, and updated the minor version numbers for the other Python installation stanzas. * Fixed a problem rendering multiple authors with organization showOnFrontPage='false'. Further addresses issue #483. * Added a switch --no-external-js, and some other --no-* switches to invert boolean settings. Fixes issue #486. * Added an early return from cache() when repeated attempts to fetch an URL fails. -- Henrik Levkowetz 20 Jan 2020 15:29:17 +0000 The preferred way to install xml2rfc is by doing 'pip install xml2rfc', and 'pip install --upgrade xml2rfc' to upgrade. If there are system- installed python modules which pip will not upgrade, you may have to use 'pip install --upgrade --no-deps xml2rfc' and install dependencies manually. The new version is also available through SVN checkout, with 'svn checkout http://svn.tools.ietf.org/svn/tools/xml2rfc/tags/cli/2.38.1' Regards, Henrik (via the mkrelease script) From nobody Mon Jan 20 10:33:49 2020 Return-Path: X-Original-To: xml2rfc-dev@ietfa.amsl.com Delivered-To: xml2rfc-dev@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A11F120800; Mon, 20 Jan 2020 10:33:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LW-NjYBYsRTM; Mon, 20 Jan 2020 10:33:41 -0800 (PST) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B694120041; Mon, 20 Jan 2020 10:33:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1579545217; bh=rDQFKlD3F85v82bS3Dgz632ByoRIXBqvthhbf6KNXzo=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=dcwQs+H8a0nA4LtywHkkSoAVSnMoeLDYzvOLvx8KJhExZftJ38oE+PNW29syM46KM Yf7zQ1rXxsKGDk0hhG+47zuSNhlflx5PuzZFopuulSfAt7AZ0Qp455KT2Y/MYhj49N V9jujG9OQQ/P1JTRrLAckngliI0ogb6jFLkckJMA= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.124] ([91.61.63.42]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MfYPi-1jZGDR1uW0-00fzxz; Mon, 20 Jan 2020 19:33:37 +0100 To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org References: From: Julian Reschke Message-ID: <973bc456-19af-76e8-d8e5-ef506f587fe7@gmx.de> Date: Mon, 20 Jan 2020 19:33:32 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:8ObCG/dRoLRZ2LhAFcINeBgPGGI86tdC7Jn0dY2m4UcqCxJzw+y kDwUEFv/OM/BhNMFVmBiQt1NRdT/OhlfZiZRKvUi3LlHVq2pwWvuuYSbqA8+/tcI+r6ul1U r1xDZnECWjlYy5tRD7SsS7bNTfdlAD8ZqolZo8PkhqBUgRbFZhU2rcXGGCBZE7+ExflCI0s QsR1HaEfIepSVR1jpqRpQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:T/7Xw3CAPFw=:mEF+WXHCzrBsOGY+l2Dx89 oWbdl9qoumj8fmXki8MmHjyhyz1FfmSBm1bTBH77DXMWJOrsJqBr+kOS/KYEkUy5Hyd5/0PNh /ifNGB3jA1BDfBZhnj11/ms7J4z+C6GUDu8XiDCQwGJTA52fAKpO+LX6XxdX9ttE5Vp1ONCYf p3SRQNdT7RMg/GgUd5s71eApkrFg2E4W8SgKsnkf1Gbf54iNXk2KSFwXyucFb7P/cgoB9b0TS YP1PAqujzU+9295QFjXpk92fD8EY4+der0BLR3CeUV7zIuEoh6R5VHRp+khVKFu3ajvbVlhmt 0b/ub47LqlDjefrMUzNcoRSkj8leisAKUqHRdTb56/lOLdvkb++Fjfg30dDFkj2YCa5T+niLx QG4FJW3iRLTOOuj5CSc5B3ca8bIXoQO3mVnf0Auk/7MQgQHOeRAK+kbRGCbOfSYgefOvTRBKj npE3WXHnCa+GzRiI6WEK1/xr1mqGw/192CLOj4UnI/Oej6vBeAtO55n0Ow6BKLt8MPYQD6TMv aCjqek05KmIVEuAuZfJ926I0b4OVTzx/6TwPKtSpHuZyFcFAGmGGG9XTsMgsBcAZj4yhB5TGi cbjG6RO+xYf+JVjjLSrCTI8OzV8s0kqd2dEaNFciZ4tGI1nmxK/IJF3bOJ6oVzAaBjuqGfy06 d+AZ2r/d/fgVhYxEDpzPXE0GY1gVvSD/yjy3IMeqm54eJNERdq7T7q267TZOYKV/3KNza0o8t Hdy8SRjtYtK/D1a0ijqSJTDJvI62hj+Ps9xGbmNp1fsgB17jjsaYiUTMRZGfu2Rlq9hgygioD SaQseUtU7L6ZGPKkRCKzAkJDMmVC5fvlr/Ze0hASHVf7maS17FZb2XPNTQCi8IK2WYaIntqpu jmk9l5yW1Mlul1U/qQKKFIyxqbCqKhL9HVztO+1QVcM2xlv7cJWGlUAt4W1KYRFuo63XkUUFd sJhZh3kkNt3atx0s2xk58KpCo5EFZCMhyJH/rhxHka+OVyDjNf1rVcrafHXbdIsEKDcdsYA2/ sRbeo3B0eNJ+jn1UKQax6hBkU3InqySNGJnwa3BZih7D8fyVhd54mA39zXOrDjTTmPcjJPQVT hG59Ue75/qry4/CPxPPLgRjrssIokVqWHYtZI6iXzhUPkPvVeIID9fdhnxCScvBdmhLuQ1/xs g11WvxQhoncu4JAstwils4mwGVLx+SYJnCGid3rsouuSgO7IgO8lH9rwmtiRynzCMrcyHWmMV EofvJMaGCsAKiw9jvBen3xchc/XruEL912AEnWYbPGoGQQQjWR/mB+wR2wVo= Archived-At: Subject: Re: [xml2rfc-dev] New xml2rfc release: v2.38.1 X-BeenThere: xml2rfc-dev@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jan 2020 18:33:47 -0000 On 20.01.2020 16:33, Henrik Levkowetz wrote: > > Hi, > > This is an automatic notification about a new xml2rfc release, > v2.38.1, generated when running the mkrelease script. > > Release notes: > > xml2rfc (2.38.1) ietf; urgency=3Dmedium > > * Added a preptool check for numbered sections occurring after or und= er > unnumbered sections, and changed the code for Reference sections to > not emit section numbers if the previous section was unnumbered. > Fixes issue #433 > > * Refactored the code for reference anchor to display string mapping, > locating it in a base class method. Updated it to honour the symRe= fs > setting. Fixes issue #476. > ... The above may have broken s to children of . See . Best regards, Julian From nobody Tue Jan 28 17:03:13 2020 Return-Path: X-Original-To: xml2rfc-dev@ietfa.amsl.com Delivered-To: xml2rfc-dev@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62555120105 for ; Tue, 28 Jan 2020 17:03:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id looq3OecfgWJ for ; Tue, 28 Jan 2020 17:03:09 -0800 (PST) Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 1B67C1200B3 for ; Tue, 28 Jan 2020 17:03:09 -0800 (PST) Received: from xse163.mail2web.com ([66.113.196.163] helo=xse.mail2web.com) by mx105.antispamcloud.com with esmtp (Exim 4.92) (envelope-from ) id 1iwbkw-0001NA-7z for xml2rfc-dev@ietf.org; Wed, 29 Jan 2020 02:03:06 +0100 Received: from xsmtp21.mail2web.com (unknown [10.100.68.60]) by xse.mail2web.com (Postfix) with ESMTPS id 486lb50CBXz31QS for ; Tue, 28 Jan 2020 17:02:57 -0800 (PST) Received: from [10.5.2.15] (helo=xmail05.myhosting.com) by xsmtp21.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1iwbku-0003YU-T8 for xml2rfc-dev@ietf.org; Tue, 28 Jan 2020 17:02:56 -0800 Received: (qmail 24009 invoked from network); 29 Jan 2020 01:02:56 -0000 Received: from unknown (HELO [192.168.1.105]) (Authenticated-user:_huitema@huitema.net@[172.58.46.251]) (envelope-sender ) by xmail05.myhosting.com (qmail-ldap-1.03) with ESMTPA for ; 29 Jan 2020 01:02:56 -0000 To: xml2rfc-dev@ietf.org From: Christian Huitema Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mQENBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAG0J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PokBOQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1a5AQ0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAYkCPgQYAQIACQUCUhFfyAIb LgEpCRCTQwmyVcgNcsBdIAQZAQIABgUCUhFfyAAKCRC22tOSFDh1UOlBB/94RsCJepNvmi/c YiNmMnm0mKb6vjv43OsHkqrrCqJSfo95KHyl5Up4JEp8tiJMyYT2mp4IsirZHxz/5lqkw9Az tcGAF3GlFsj++xTyD07DXlNeddwTKlqPRi/b8sppjtWur6Pm+wnAHp0mQ7GidhxHccFCl65w uT7S/ocb1MjrTgnAMiz+x87d48n1UJ7yIdI41Wpg2XFZiA9xPBiDuuoPwFj14/nK0elV5Dvq 4/HVgfurb4+fd74PV/CC/dmd7hg0ZRlgnB5rFUcFO7ywb7/TvICIIaLWcI42OJDSZjZ/MAzz BeXm263lHh+kFxkh2LxEHnQGHCHGpTYyi4Z3dv03HtkH/1SI8joQMQq00Bv+RdEbJXfEExrT u4gtdZAihwvy97OPA2nCdTAHm/phkzryMeOaOztI4PS8u2Ce5lUB6P/HcGtK/038KdX5MYST Fn8KUDt4o29bkv0CUXwDzS3oTzPNtGdryBkRMc9b+yn9+AdwFEH4auhiTQXPMnl0+G3nhKr7 jvzVFJCRif3OAhEm4vmBNDE3uuaXFQnbK56GJrnqVN+KX5Z3M7X3fA8UcVCGOEHXRP/aubiw Ngawj0V9x+43kUapFp+nF69R53UI65YtJ95ec4PTO/Edvap8h1UbdEOc4+TiYwY1TBuIKltY 1cnrjgAWUh/Ucvr++/KbD9tD6C8= Message-ID: Date: Tue, 28 Jan 2020 17:02:56 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------08181761185D3009B19AA30A" Content-Language: en-US X-Originating-IP: 66.113.196.163 X-Spampanel-Domain: xsmtpout.mail2web.com X-Spampanel-Username: 66.113.196.163/32 Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.163/32@xsmtpout.mail2web.com X-Spampanel-Outgoing-Class: unsure X-Spampanel-Outgoing-Evidence: Combined (0.15) X-Recommended-Action: accept X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0YfsolMNZcEgL2mqy3zzv3mpSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDP+LJjfTjuxM0oenyb3UAfdXt FNSzkMWnDricnMrpFJrlL3vhRp7FCu7NBWgslY8ZQVFPFt+4EqMnp4CTDhVg0lKlzDUUdXZXKiJE 9FAeBYpBbCpe79Kozx0nomzoHNuE0iWH+V3xPUI11Obqsmg5K+42Vki7412dpbhrD2d47zbC3VvU djSCswikK/licfX+oIF6uBSWByrPG2Vxuo/vVPllrFEbCkMryfcYCsgMUJObfBQoU3roWy2GH1DY sAiH3gousbgNfxi2R3uFLvZP/HBXvrLBlKCVRjjdPbjQ4HnBNho1Lszw5OO01yYoll8q2UgzFF+j HNSbIoW1Q++Wvj3dKxLhoxcmaInYbR5vlqFg3eKzPG9E5MikC2dVXWcpK172i/E5sOgbaCtBiSIx 1XwCY8vmv+JqOVJamBHfOGVwjn7Xut/lXagsodd5qqODTFiwcpU4fyz75jxpU98RPGiH1Wgh6RAe nBR+licROGbJvgxCcfCHhQ0mdQLeGLyTwQdOytza9yUjSKcl/JutEPTCqdpM9ZidIMazwixIrdLo Oo70iqAlsD2ZyQe0MRcoJGFRUqYs8cxqQveBpKDFewRRiI4FYjmNWKK4C97xdQjTPpuFqUUQz+mM 8JAD4ECWLeiUu403BNqe8GzesHyoJBzd1TBXbJNvBC1nKO3+wSOd6QpA6hUNslWdwSbGY877OYf5 WsgpKiLOeQk3numYG1FfEoXm0/FPF8PR0w363lkzQqfbSvqMkajQfGKEj865yLIB1jT1Bo29o7Zg vtIBLnR6mMZiP8hyi9JD/oRrQtQcSyQwpbsYuxSOGTH6k0lfJmkP8s1HCfLKOW1F2ohPJ/AFMvX7 q8M4x6bP/gjzw0OgghQYwZVLClIproNi1WM01Bh4x4h9uYrmdPlyGg3lun80sIBTfGesZu6FzlJ8 P6r2OKHH5lr9xXvSM4nM3avg X-Report-Abuse-To: spam@quarantine11.antispamcloud.com Archived-At: Subject: [xml2rfc-dev] Weird formatting of list in presence of XML comments X-BeenThere: xml2rfc-dev@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jan 2020 01:03:11 -0000 This is a multi-part message in MIME format. --------------08181761185D3009B19AA30A Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I just submitted https://www.ietf.org/internet-drafts/draft-ietf-dnssd-prireq-04.txt, and I am surprised by the text rendering section 4.1. It looks like: 4.1. Private Client Requirements For all three scenarios described in Section 3.1, client privacy requires DNS-SD messages to: 1. Avoid disclosure of the client's identity, either directly or via inference, to nodes other than select servers. 1. 2. Avoid exposure of linkable identifiers that allow tracing client devices. 2. 3. Avoid disclosure of the client's interest in specific service instances or service types to nodes other than select servers. 3. Listing and resolving services via DNS-SD, clients typically disclose their interest in specific services types and specific instances of these types, respectively. Notice the extra "1.", "2.", "3."? Before submission, I tested the XML input against https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi, and there was no issue. The text rendering, as expected, was: 4.1. Private Client Requirements For all three scenarios described in Section 3.1, client privacy requires DNS-SD messages to: 1. Avoid disclosure of the client's identity, either directly or via inference, to nodes other than select servers. 2. Avoid exposure of linkable identifiers that allow tracing client devices. 3. Avoid disclosure of the client's interest in specific service instances or service types to nodes other than select servers. Listing and resolving services via DNS-SD, clients typically disclose their interest in specific services types and specific instances of these types, respectively. The input is an XML2RFC V2 file. The relevant section is: =C2=A0

=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 For all three scenarios described in , client privacy =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 requires DNS-SD messages to: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Avoid disclosure o= f the client's identity, either directly or via inference, =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 to nodes other tha= n select servers. =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Avoid exposure of = linkable identifiers that allow tracing client devices. =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Avoid disclosure o= f the client's interest in specific service instances or service types to =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 nodes other than s= elect servers. =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Listing and resolving services via DNS-SD,= clients typically disclose their interest in =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 specific services types and specific insta= nces of these types, respectively. =C2=A0=C2=A0=C2=A0 I suspect that the XML comments are tripping some bug. I will remove them in the next iteration of the draft, but I wonder whether that's a bug that should be fixed. -- Christian Huitema --------------08181761185D3009B19AA30A Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

I just submitted https://www.ietf.org/internet-drafts/draft-ietf-dnssd-prireq-04.txt, and I am surprised by the text rendering section 4.1. It looks like:

4.1.  Private Client Requirements

   For all three scenarios described in Section 3.1, client privacy
   requires DNS-SD messages to:

   1.  Avoid disclosure of the client's identity, either directly or via
       inference, to nodes other than select servers.

   1.

   2.  Avoid exposure of linkable identifiers that allow tracing client
       devices.

   2.

   3.  Avoid disclosure of the client's interest in specific service
       instances or service types to nodes other than select servers.

   3.

   Listing and resolving services via DNS-SD, clients typically disclose
   their interest in specific services types and specific instances of
   these types, respectively.

Notice the extra "1.", "2.", "3."? Before submission, I tested the XML input against https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi, and there was no issue. The text rendering, as expected, was:

4.1.  Private Client Requirements

   For all three scenarios described in Section 3.1, client privacy
   requires DNS-SD messages to:

   1.  Avoid disclosure of the client's identity, either directly or via
       inference, to nodes other than select servers.

   2.  Avoid exposure of linkable identifiers that allow tracing client
       devices.

   3.  Avoid disclosure of the client's interest in specific service
       instances or service types to nodes other than select servers.

   Listing and resolving services via DNS-SD, clients typically disclose
   their interest in specific services types and specific instances of
   these types, respectively.

The input is an XML2RFC V2 file. The relevant section is:

<section title="Private Client Requirements">
    <t>
      For all three scenarios described in <xref target="scenarios" />, client privacy
      requires DNS-SD messages to:
      <list style="numbers">
        <t>
          Avoid disclosure of the client's identity, either directly or via inference,
          to nodes other than select servers.
          
        </t>
        <t>
          Avoid exposure of linkable identifiers that allow tracing client devices.
          
        </t>
        <t>
          Avoid disclosure of the client's interest in specific service instances or service types to
          nodes other than select servers.
          
        </t>
      </list>
    </t>
    <t>
      Listing and resolving services via DNS-SD, clients typically disclose their interest in
      specific services types and specific instances of these types, respectively.
    </t>

I suspect that the XML comments are tripping some bug. I will remove them in the next iteration of the draft, but I wonder whether that's a bug that should be fixed.

-- Christian Huitema

--------------08181761185D3009B19AA30A-- From nobody Wed Jan 29 07:52:47 2020 Return-Path: X-Original-To: xml2rfc-dev@ietfa.amsl.com Delivered-To: xml2rfc-dev@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DBCA120169 for ; Wed, 29 Jan 2020 07:52:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.899 X-Spam-Level: X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JmqK-nk9XuRn for ; Wed, 29 Jan 2020 07:52:35 -0800 (PST) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0550120020 for ; Wed, 29 Jan 2020 07:52:35 -0800 (PST) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:57042 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 1iwpdU-0002ZA-Pj; Wed, 29 Jan 2020 07:52:34 -0800 To: Christian Huitema , xml2rfc-dev@ietf.org References: From: Henrik Levkowetz Message-ID: Date: Wed, 29 Jan 2020 16:52:05 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: xml2rfc-dev@ietf.org, huitema@huitema.net X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org) X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [xml2rfc-dev] Weird formatting of list in presence of XML comments X-BeenThere: xml2rfc-dev@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jan 2020 15:52:45 -0000 Hi Christian, On 2020-01-29 02:02, Christian Huitema wrote: > I just submitted > https://www.ietf.org/internet-drafts/draft-ietf-dnssd-prireq-04.txt, and > I am surprised by the text rendering section 4.1. It looks like: This is indeed a bug. It doesn't appear in a straightforward invocation of xml2rfc with your xml input file, though, so it will take a bit of debugging to pinpoint the circumstances that caused it. Regards, Henrik > > 4.1. Private Client Requirements > > For all three scenarios described in Section 3.1, client privacy > requires DNS-SD messages to: > > 1. Avoid disclosure of the client's identity, either directly or via > inference, to nodes other than select servers. > > 1. > > 2. Avoid exposure of linkable identifiers that allow tracing client > devices. > > 2. > > 3. Avoid disclosure of the client's interest in specific service > instances or service types to nodes other than select servers. > > 3. > > Listing and resolving services via DNS-SD, clients typically disclose > their interest in specific services types and specific instances of > these types, respectively. > > Notice the extra "1.", "2.", "3."? Before submission, I tested the XML > input against https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi, and > there was no issue. The text rendering, as expected, was: > > 4.1. Private Client Requirements > > For all three scenarios described in Section 3.1, client privacy > requires DNS-SD messages to: > > 1. Avoid disclosure of the client's identity, either directly or via > inference, to nodes other than select servers. > > 2. Avoid exposure of linkable identifiers that allow tracing client > devices. > > 3. Avoid disclosure of the client's interest in specific service > instances or service types to nodes other than select servers. > > Listing and resolving services via DNS-SD, clients typically disclose > their interest in specific services types and specific instances of > these types, respectively. > > The input is an XML2RFC V2 file. The relevant section is: > >

> > For all three scenarios described in , > client privacy > requires DNS-SD messages to: > > > Avoid disclosure of the client's identity, either directly or > via inference, > to nodes other than select servers. > > > > Avoid exposure of linkable identifiers that allow tracing > client devices. > > > > Avoid disclosure of the client's interest in specific service > instances or service types to > nodes other than select servers. > > > > > > Listing and resolving services via DNS-SD, clients typically > disclose their interest in > specific services types and specific instances of these types, > respectively. > > > I suspect that the XML comments are tripping some bug. I will remove > them in the next iteration of the draft, but I wonder whether that's a > bug that should be fixed. > > -- Christian Huitema > > > > > > > _______________________________________________ > xml2rfc-dev mailing list > xml2rfc-dev@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc-dev > From nobody Thu Jan 30 05:48:28 2020 Return-Path: X-Original-To: xml2rfc-dev@ietfa.amsl.com Delivered-To: xml2rfc-dev@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FFF8120113 for ; Thu, 30 Jan 2020 05:48:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.7 X-Spam-Level: X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (bad RSA signature)" header.d=gundogan.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 XDgod55lZJBK for ; Thu, 30 Jan 2020 05:48:24 -0800 (PST) Received: from mail.localdomain (trantor.gundogan.net [37.120.167.193]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C701B120103 for ; Thu, 30 Jan 2020 05:48:24 -0800 (PST) Received: from localhost (unknown [141.22.28.164]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by mail.localdomain (Postfix) with ESMTPSA id 4038C2CEFA for ; Thu, 30 Jan 2020 14:41:03 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gundogan.net; s=201712; t=1580391663; bh=GufcDlE0tP3hK/7QCbQ5DJf9R+LPiabZo/khh/oq8I0=; h=From:To:Subject:Date:From; b=n2IgjDlDb78iEfpP2Z8jT4/S4XJpKlX9oTZmA++QtwX4WsQvAQQwXFvpFNXRDi8M9 5AqFOZWbQ3qTGOWOOdy17n4oHtogpPoyOBmzcDisxdaNdwxm6CD9MCqtJHqzoDe0+B nWgtVE+X5wZ7uzqa9/bAhhJ5rYS+lNVqF0AXGhlN8W3ZfeSYaqo+qRx4HxOJqfvlyt XLHhoW3uD5DDMjzzYSKfjg6QjgoJmD4z3gllYDhTqBrn/G/A8/8N/y+cbYcWRA+1WF 3GbIiLhbX7+VApvjkgGFltneHJpBwOdcim5DQOsEbIjHinVVQeDdU6txt98EBGklTB 8LT0mvtGZjtUQ== User-agent: mu4e 1.2.0; emacs 26.3 From: Cenk =?utf-8?B?R8O8bmRvxJ9hbg==?= To: xml2rfc-dev@ietf.org Date: Thu, 30 Jan 2020 14:48:21 +0100 Message-ID: <871rrh2gyi.fsf@gundogan.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Archived-At: Subject: [xml2rfc-dev] Wrong surname and fullname in BibXML Ref X-BeenThere: xml2rfc-dev@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2020 13:48:26 -0000 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello all, when using particular bibxml refs [1,2,3,4], we encountered a strange behavior: fullname and surname for the first author are set to an e-mail address. In the datatracker, the meta data looks fine so far, though (e.g., [5]). This leads to strange looking references in compiled documents .. Might there be a problem in the BibXML generator script? Is there a way to amend the correct names? Cheers, Cenk [1] https://xml2rfc.tools.ietf.org/public/rfc/bibxml-ids/reference.I-D.mosk= o-icnrg-beginendfragment.xml [2] https://xml2rfc.tools.ietf.org/public/rfc/bibxml-ids/reference.I-D.mosk= o-icnrg-cachecontrol.xml [3] https://xml2rfc.tools.ietf.org/public/rfc/bibxml-ids/reference.I-D.mosk= o-icnrg-ccnxchunking.xml [4] https://xml2rfc.tools.ietf.org/public/rfc/bibxml-ids/reference.I-D.mosk= o-icnrg-ccnxfragmentation.xml [5] https://datatracker.ietf.org/doc/draft-mosko-icnrg-beginendfragment/ =2D- Cenk G=C3=BCndo=C4=9Fan Hamburg University of Applied Sciences Dept. of Computer Science / Internet Technologies Group Berliner Tor 7, 20099 Hamburg, Germany Fon: +49 40 42875 - 8426 Mail: cenk.guendogan@haw-hamburg.de Web: https://www.inet.haw-hamburg.de/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEO3dMsPVVAdvZ+Oc2o9vC90TUhNIFAl4y3qUACgkQo9vC90TU hNJeBBAA1PRqBEEktAACRRrndFZW5tlumpN+9eNZpFkkTxsRKE2ZP897vgSNECe6 WIHdUdxKUX4uW4qFM6V1slvKh1lkSklDU7kNTkm6mgtGE3b1QEbe6dVYpR7TiU8u wtEvJ+tHSb6xfo9J/gOafmVlMZZJup6hL9+FDDHvH3xHLKV8EQUuKo5uW865TTx1 JtFww0bmh1tPtRXQanV3djr5M4Laa1XY9Ql3bYULvt++MVuGKEsPy98yJhG/dhvA 5pZDuZ1+ssjQWwMkobHRX3NjDFghn8LQ/mnSwmdk1989joOG9Sp37ZPIJnFBn4pg Lp1Gd2m6OXQXpLgL/+Jgwc3PwwuMymw8wzZeyp3aTvWC+yBUlezDDidB6Xftf4qr TK1r4xnHxyMev4OX5LkHrUi0JrzPJBGT0M3FbfpVnVCu56FIVofLM4Z9Z9qQq3pX 0/QmUiiLav5XSNdKzO3US+GXPmr69+42S0/W+OZJmTG4twfPzooVwpbmcCpsBSfF 3L2cZGND8Bk0PjeRzDzNk49atTZB8DZ4QUP8MVigwv42zn/SworuaJJ7DOZOM+4R AnykRcKBXNCzlUzZg4KoDvhlgQdJFlWv9PtPN6dApAbU9XghoCM/G0FeEXjsiHqe HtP3GBvh46g6BIFBV0AIqn21FSF64ZLHXRbiquDlQvOgR/2vsT0= =oGFZ -----END PGP SIGNATURE----- --=-=-=-- From nobody Thu Jan 30 07:36:47 2020 Return-Path: X-Original-To: xml2rfc-dev@ietfa.amsl.com Delivered-To: xml2rfc-dev@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BEF8120168 for ; Thu, 30 Jan 2020 07:36:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.9 X-Spam-Level: X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=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 xM5FKuEDAGta for ; Thu, 30 Jan 2020 07:36:42 -0800 (PST) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69FD9120112 for ; Thu, 30 Jan 2020 07:36:42 -0800 (PST) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:57184 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 1ixBrg-0004wQ-5C; Thu, 30 Jan 2020 07:36:41 -0800 To: =?UTF-8?B?Q2VuayBHw7xuZG/En2Fu?= , xml2rfc-dev@ietf.org References: <871rrh2gyi.fsf@gundogan.net> From: Henrik Levkowetz Message-ID: <4079c56d-882e-c552-d6ab-b0e96119d58e@levkowetz.com> Date: Thu, 30 Jan 2020 16:36:12 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <871rrh2gyi.fsf@gundogan.net> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="SGW62eWq9kwv16QQx2JMfut41acbU4jK4" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: xml2rfc-dev@ietf.org, mail=2Bietf=40gundogan.net@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-dev] Wrong surname and fullname in BibXML Ref X-BeenThere: xml2rfc-dev@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2020 15:36:46 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --SGW62eWq9kwv16QQx2JMfut41acbU4jK4 Content-Type: multipart/mixed; boundary="bJvLQW5HQPuh3Do8GS81XEPgTHTfnhh0d"; protected-headers="v1" From: Henrik Levkowetz To: =?UTF-8?B?Q2VuayBHw7xuZG/En2Fu?= , xml2rfc-dev@ietf.org Message-ID: <4079c56d-882e-c552-d6ab-b0e96119d58e@levkowetz.com> Subject: Re: [xml2rfc-dev] Wrong surname and fullname in BibXML Ref References: <871rrh2gyi.fsf@gundogan.net> In-Reply-To: <871rrh2gyi.fsf@gundogan.net> --bJvLQW5HQPuh3Do8GS81XEPgTHTfnhh0d Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Cenk, On 2020-01-30 14:48, Cenk G=C3=BCndo=C4=9Fan wrote: > Hello all, >=20 > when using particular bibxml refs [1,2,3,4], we encountered a strange > behavior: fullname and surname for the first author are set to an e-mai= l > address. In the datatracker, the meta data looks fine so far, though > (e.g., [5]). This leads to strange looking references in compiled > documents .. Might there be a problem in the BibXML generator script? I= s > there a way to amend the correct names? This is indeed a problem with some old reference files for Marc Mosko. I would have expected the files to be updated when updated information is available in the datatracker, but this does not seem to be happening. I would suggest that you use the equivalent bibxml3 entries directly from= the datatracker. They have a better guarantee of being up-to-date: https://datatracker.ietf.org/doc/bibxml3/reference.I-D.mosko-icnrg-begin= endfragment.xml https://datatracker.ietf.org/doc/bibxml3/reference.I-D.mosko-icnrg-cache= control.xml https://datatracker.ietf.org/doc/bibxml3/reference.I-D.mosko-icnrg-ccnxc= hunking.xml https://datatracker.ietf.org/doc/bibxml3/reference.I-D.mosko-icnrg-ccnxf= ragmentation.xml Best regards, Henrik >=20 > Cheers, > Cenk >=20 > [1] https://xml2rfc.tools.ietf.org/public/rfc/bibxml-ids/reference.I-D.= mosko-icnrg-beginendfragment.xml > [2] https://xml2rfc.tools.ietf.org/public/rfc/bibxml-ids/reference.I-D.= mosko-icnrg-cachecontrol.xml > [3] https://xml2rfc.tools.ietf.org/public/rfc/bibxml-ids/reference.I-D.= mosko-icnrg-ccnxchunking.xml > [4] https://xml2rfc.tools.ietf.org/public/rfc/bibxml-ids/reference.I-D.= mosko-icnrg-ccnxfragmentation.xml > [5] https://datatracker.ietf.org/doc/draft-mosko-icnrg-beginendfragment= / >=20 > -- > Cenk G=C3=BCndo=C4=9Fan >=20 > Hamburg University of Applied Sciences > Dept. of Computer Science / Internet Technologies Group > Berliner Tor 7, 20099 Hamburg, Germany > Fon: +49 40 42875 - 8426 > Mail: cenk.guendogan@haw-hamburg.de > Web: https://www.inet.haw-hamburg.de/ >=20 >=20 >=20 > _______________________________________________ > xml2rfc-dev mailing list > xml2rfc-dev@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc-dev >=20 --bJvLQW5HQPuh3Do8GS81XEPgTHTfnhh0d-- --SGW62eWq9kwv16QQx2JMfut41acbU4jK4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl4y9+wACgkQTptXS4+7 Fxqa+BAAp3CCEumzUCSkSiwmpBtfVF08qoy6z3GSU5rfLR2lCUS1aa6Aav2yudzX eyB2SQ5INnbqbebeV4BH4XanE0n6Ha3u1k99ghOdVl1F3pXScXQ1VDxAv05VTRv8 q5KzsiSF5K5AClVZZyQVPGI0v+X/G8ofvazFkDAs7uA5bGkIyzF12ag1ve+JG+nN 8Vx1De5GmhBNrfGheJYvfO/iBuP3tQBw+5tU53jjr4etkjEQjYSGUmgAsDUhv7rT QJXWXOngoeljftLtwXDgT43JgzxDcno5/tm12vbNdUG2ddkBTehaAf/YrmszMOlm 1hrrPutIhF3KQlpQDh8k3CPLuUcp/Jo3v/Y36vBXFR//DdGaZfj4IYntfcbrzqwd x6vJKm0BzXBj2t1xILPLkpTcD0bvaLPhxuHXMbRaQExFrCFCO0hesc8ORMzR1bZf RMqbrxZNYUcL2sLYRjwo03pxV/a+0lXQ1gpWOh+4AcM+u5tUOS06spGYRoXh0rPc nq27LrggS3be+uIbQC9VwNKipJmDH+kR/2rs9d4nT2tAmtEG9+Z5BsMhG786KSPX 2iZml7t1Ya9BlD6BjyLYY7ekManpAPS6d+Q+uz9/EmCjBoZ7pTGj6SoSgiz9Jcd/ SKpqgABOa6TDw13eZJ33jOFURp/3puOcrWWfrAajfM2KShdIZK8= =w31t -----END PGP SIGNATURE----- --SGW62eWq9kwv16QQx2JMfut41acbU4jK4-- From nobody Thu Jan 30 07:53:45 2020 Return-Path: X-Original-To: xml2rfc-dev@ietfa.amsl.com Delivered-To: xml2rfc-dev@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3F5912018D for ; Thu, 30 Jan 2020 07:53:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 wsk96BXUVIc0 for ; Thu, 30 Jan 2020 07:53:41 -0800 (PST) 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 5EF8D120143 for ; Thu, 30 Jan 2020 07:53:41 -0800 (PST) Received: from [172.16.42.112] (p548DC4D8.dip0.t-ipconnect.de [84.141.196.216]) (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 487lJL5DGZz167s; Thu, 30 Jan 2020 16:53:38 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\)) From: Carsten Bormann In-Reply-To: <4079c56d-882e-c552-d6ab-b0e96119d58e@levkowetz.com> Date: Thu, 30 Jan 2020 16:53:37 +0100 Cc: =?utf-8?B?Q2VuayBHw7xuZG/En2Fu?= , xml2rfc-dev@ietf.org X-Mao-Original-Outgoing-Id: 602092417.075004-43ebab280134d87be822f8228611f38f Content-Transfer-Encoding: quoted-printable Message-Id: <8166DFDF-98D6-4DF4-8CF6-C34A522F9F7C@tzi.org> References: <871rrh2gyi.fsf@gundogan.net> <4079c56d-882e-c552-d6ab-b0e96119d58e@levkowetz.com> To: Henrik Levkowetz X-Mailer: Apple Mail (2.3608.40.2.2.4) Archived-At: Subject: Re: [xml2rfc-dev] Wrong surname and fullname in BibXML Ref X-BeenThere: xml2rfc-dev@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2020 15:53:44 -0000 On 2020-01-30, at 16:36, Henrik Levkowetz wrote: >=20 > I would suggest that you use the equivalent bibxml3 entries directly = from > the datatracker. They have a better guarantee of being up-to-date: Can we fix the official ones as well? I=E2=80=99m thinking about running a comparison, but I don=E2=80=99t = know whether datatracker would fall over from 114 k requests (the = official ones come in via rsync). Maybe I can start out without the 86 = k I-D.draft-* (i.e., version-specific) entries. Gr=C3=BC=C3=9Fe, Carsten From nobody Thu Jan 30 08:02:18 2020 Return-Path: X-Original-To: xml2rfc-dev@ietfa.amsl.com Delivered-To: xml2rfc-dev@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E32F312018D for ; Thu, 30 Jan 2020 08:02:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 wWWq7B4FD7T1 for ; Thu, 30 Jan 2020 08:02:14 -0800 (PST) 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 9563A1201CE for ; Thu, 30 Jan 2020 08:02:14 -0800 (PST) Received: from [172.16.42.112] (p548DC4D8.dip0.t-ipconnect.de [84.141.196.216]) (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 487lVF1Wdtz167m; Thu, 30 Jan 2020 17:02:13 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\)) From: Carsten Bormann In-Reply-To: <8166DFDF-98D6-4DF4-8CF6-C34A522F9F7C@tzi.org> Date: Thu, 30 Jan 2020 17:02:12 +0100 Cc: =?utf-8?B?Q2VuayBHw7xuZG/En2Fu?= , xml2rfc-dev@ietf.org X-Mao-Original-Outgoing-Id: 602092932.190271-9f0b64c5f6459408374eb6d3356f8ff8 Content-Transfer-Encoding: quoted-printable Message-Id: <9F75F1D4-6503-40D7-A106-3554741AC740@tzi.org> References: <871rrh2gyi.fsf@gundogan.net> <4079c56d-882e-c552-d6ab-b0e96119d58e@levkowetz.com> <8166DFDF-98D6-4DF4-8CF6-C34A522F9F7C@tzi.org> To: Henrik Levkowetz X-Mailer: Apple Mail (2.3608.40.2.2.4) Archived-At: Subject: Re: [xml2rfc-dev] Wrong surname and fullname in BibXML Ref X-BeenThere: xml2rfc-dev@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2020 16:02:17 -0000 On 2020-01-30, at 16:53, Carsten Bormann wrote: >=20 > Can we fix the official ones as well? That would be some 1739 places. Gr=C3=BC=C3=9Fe, Carsten find . -name reference\*.xml | xargs grep surname=3D | grep @= From nobody Thu Jan 30 10:10:47 2020 Return-Path: X-Original-To: xml2rfc-dev@ietfa.amsl.com Delivered-To: xml2rfc-dev@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B5CD1200B8 for ; Thu, 30 Jan 2020 10:10:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.7 X-Spam-Level: X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (bad RSA signature)" header.d=gundogan.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 5QdrmMOGIrsl for ; Thu, 30 Jan 2020 10:10:44 -0800 (PST) Received: from mail.localdomain (trantor.gundogan.net [37.120.167.193]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57100120090 for ; Thu, 30 Jan 2020 10:10:44 -0800 (PST) Received: from localhost (unknown [141.22.28.164]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by mail.localdomain (Postfix) with ESMTPSA id F26262CF4D for ; Thu, 30 Jan 2020 19:03:22 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gundogan.net; s=201712; t=1580407403; bh=muu2y5pcQ7IZzs2jO4DUNqDrNDBIVSdTogmFfgAtS4U=; h=References:From:To:Subject:In-reply-to:Date:From; b=CLceykUSc9DtFfGIVrYgLVsozlzkFhc7bgwWYX18dbLq4oTkh+rm+88/VWlCi+NC7 8IGwvFErNupzicxtde6ZN+tURr8Zltq7lqaZLI3uuBS41H/3QM6YtYN6F+jN+cxyTI BMybufaglvcKRcHQbz0Z+gUor7+bo7MJ+0gnwffttrjQ5PXsk11nQAGMcq7QTHKDts aZn1/H8DE8YW/Tuhw7DWOzYjlLYPA3922OUA+F7DIbOH2q73MlCnmrzq8WqjPXbo+F Je3MmyPOVrOh/at798/Jnajxjg1pzgiOTnuWRaYHbSR4+KVwXXuoLBaXlO6dVbCKCO nvcU9+znSuLpQ== References: <871rrh2gyi.fsf@gundogan.net> <4079c56d-882e-c552-d6ab-b0e96119d58e@levkowetz.com> <8166DFDF-98D6-4DF4-8CF6-C34A522F9F7C@tzi.org> User-agent: mu4e 1.2.0; emacs 26.3 From: Cenk =?utf-8?B?R8O8bmRvxJ9hbg==?= To: xml2rfc-dev@ietf.org In-reply-to: <8166DFDF-98D6-4DF4-8CF6-C34A522F9F7C@tzi.org> Date: Thu, 30 Jan 2020 19:10:41 +0100 Message-ID: <87zhe424ta.fsf@gundogan.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Archived-At: Subject: Re: [xml2rfc-dev] Wrong surname and fullname in BibXML Ref X-BeenThere: xml2rfc-dev@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2020 18:10:45 -0000 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello Henrik, Carsten, On Thu, Jan 30 2020 at 16:53 +0100, Carsten Bormann wrote: > On 2020-01-30, at 16:36, Henrik Levkowetz wrote: >> >> I would suggest that you use the equivalent bibxml3 entries directly from >> the datatracker. They have a better guarantee of being up-to-date: > > Can we fix the official ones as well? @Carsten: so around 0.5\% are broken? Darn my luck (: @Henrik: Thanks for the alternative link. I wasn't aware of that location. I actually would prefer the other location for its rsync capability. I just did another rsync update and I saw that some drafts have been fixed (probably manually?). Thank you (: One question, though: While drafts of the form bibxml3/reference.I-D.draft-mosko-icnrg-beginendfragment-.xml have a correct author field now, the document bibxml3/reference.I-D.mosko-icnrg-beginendfragment.xml has still the broken format. I like to use the latter reference to always have the latest ID version in the bibliography. Is there a way to also update these ones? Cheers, Cenk > > I=E2=80=99m thinking about running a comparison, but I don=E2=80=99t know= whether datatracker would fall over from 114 k requests (the official ones= come in via rsync). Maybe I can start out without the 86 k I-D.draft-* (i= .e., version-specific) entries. > > Gr=C3=BC=C3=9Fe, Carsten > > _______________________________________________ > xml2rfc-dev mailing list > xml2rfc-dev@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc-dev =2D- Cenk G=C3=BCndo=C4=9Fan Hamburg University of Applied Sciences Dept. of Computer Science / Internet Technologies Group Berliner Tor 7, 20099 Hamburg, Germany Fon: +49 40 42875 - 8426 Mail: cenk.guendogan@haw-hamburg.de Web: https://www.inet.haw-hamburg.de/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEO3dMsPVVAdvZ+Oc2o9vC90TUhNIFAl4zHCEACgkQo9vC90TU hNKE3hAAwa4789EC67Mgd6dnwHgKzjOWhVIcIA+/kIZqHAQrP02pQuaKxYZ9D0mB nI/+w1sDxLqNfJpr3T0hYb13mQ5S69RyjWFztX2Ub4yNef8n5Hnjixn0bVFAR6yu mU73O99JuJEH/6SrQkAVSgAN+g5vXYyQY1SsIKCvxy8874QM628f4bn6cyxnanW3 IeRL2FX0v62/rqVquin1UPBfENpWreQ4hXrT6afWpm/mJorhMcdB9sI/6cHrSzEL 8B3X+1tgTfK5PSBDDZ1lGajC0k1x/cNhi3XHQkpNZzjUEGZtuVcLeU5ExHKMyN6X GFq0JWEaRlQLfk6mPTu8ITr87ERq4M+ysLaqXffPvx5Drw6E5iotdMR1Vh2xkVjQ a+J5c3mwFEOOp//kXadTva/55LQCF09proOMfG7aBwLlpx/VdiNXfvQHLvt2+Ud/ eYxtR38nj6txmcEbOnusG+UbI70t3/gm0crIj4bZt2qD250ofl2hr2TqD4+Jtuzi RtadE+J3BIuK5deBgu3wPHCmyYKNI9cBKIlPt/JWnMckk+XghKl0rF/OBue1atvm fC3EER5Db6byfYhEbczTXX09iOfYto/FIKB0ZWCdS/txfsXqZLwYL+GQ/VAn1F3m zGvZyomLgVvD7t51Ia798huLnKj1jxQ3oJ4W+s1FmQFiUrZ34XI= =EJSk -----END PGP SIGNATURE----- --=-=-=-- From nobody Thu Jan 30 12:36:35 2020 Return-Path: X-Original-To: xml2rfc-dev@ietfa.amsl.com Delivered-To: xml2rfc-dev@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F082412001A for ; Thu, 30 Jan 2020 12:36:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.9 X-Spam-Level: X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=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 Dh2i5nhxFaKT for ; Thu, 30 Jan 2020 12:36:30 -0800 (PST) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E163C12002E for ; Thu, 30 Jan 2020 12:36:30 -0800 (PST) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:57771 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 1ixGXp-0003m4-Qb; Thu, 30 Jan 2020 12:36:30 -0800 To: Carsten Bormann References: <871rrh2gyi.fsf@gundogan.net> <4079c56d-882e-c552-d6ab-b0e96119d58e@levkowetz.com> <8166DFDF-98D6-4DF4-8CF6-C34A522F9F7C@tzi.org> Cc: =?UTF-8?B?Q2VuayBHw7xuZG/En2Fu?= , xml2rfc-dev@ietf.org From: Henrik Levkowetz Message-ID: Date: Thu, 30 Jan 2020 21:36:02 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <8166DFDF-98D6-4DF4-8CF6-C34A522F9F7C@tzi.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="SU25kcM1CcxjPX8v56iRPjdICqoSA8OAd" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: xml2rfc-dev@ietf.org, mail=2Bietf=40gundogan.net@dmarc.ietf.org, cabo@tzi.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-dev] Wrong surname and fullname in BibXML Ref X-BeenThere: xml2rfc-dev@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2020 20:36:34 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --SU25kcM1CcxjPX8v56iRPjdICqoSA8OAd Content-Type: multipart/mixed; boundary="XMCxC5RgVMaTXMXSaeDLk08QgxJwmLt83"; protected-headers="v1" From: Henrik Levkowetz To: Carsten Bormann Cc: =?UTF-8?B?Q2VuayBHw7xuZG/En2Fu?= , xml2rfc-dev@ietf.org Message-ID: Subject: Re: [xml2rfc-dev] Wrong surname and fullname in BibXML Ref References: <871rrh2gyi.fsf@gundogan.net> <4079c56d-882e-c552-d6ab-b0e96119d58e@levkowetz.com> <8166DFDF-98D6-4DF4-8CF6-C34A522F9F7C@tzi.org> In-Reply-To: <8166DFDF-98D6-4DF4-8CF6-C34A522F9F7C@tzi.org> --XMCxC5RgVMaTXMXSaeDLk08QgxJwmLt83 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Carsten, On 2020-01-30 16:53, Carsten Bormann wrote: > On 2020-01-30, at 16:36, Henrik Levkowetz wrote:= >>=20 >> I would suggest that you use the equivalent bibxml3 entries directly f= rom >> the datatracker. They have a better guarantee of being up-to-date: >=20 > Can we fix the official ones as well? I have a script to generate the same content as files. Once other fires are out, I'll set up a cronjob to generate such, and after testing, I hop= e to use those instead of the TCL-generated draft reference files. > I=E2=80=99m thinking about running a comparison, but I don=E2=80=99t kn= ow whether=20 > datatracker would fall over from 114 k requests (the official ones > come in via rsync). Maybe I can start out without the 86 k > I-D.draft-* (i.e., version-specific) entries. Be prepared for plenty of differences in non-essentials, and watch the response times, if you do this. Best regards, Henrik --XMCxC5RgVMaTXMXSaeDLk08QgxJwmLt83-- --SU25kcM1CcxjPX8v56iRPjdICqoSA8OAd Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl4zPjIACgkQTptXS4+7 FxpcMQ/9HSjJYbKUSX5X942ZekPk1AsfPNhabyOKzpXpH/8hT7JPRH0txPL4ay9p bDRmeIjZkNiylsdC5l/VEUXpq9oQRzRgjZoWN4FIrHyTXLEED3t7UjfbI2h3cEJC g0DZjL+23p8oHIJomKbhIe997NZMXgWXapVAEzzMaH0kb8rXoa5bvRdqtKc0IYQo msvmr5D2s+cKk5KipAh0mCKlTXrHbs9FiDDTnZA8Mmb3ROtDTqVRsKz/OiAET58n 1POh8wgdDvg0oYi/InA5fSJb8rvRW1LAqGSYvg6boAK17OuqUeuQH/SrWsJxOMUL NIJbWS8Ji83ttsuCDVPUBzApzudXA8TxyP+Nrf6x5X9EkYNqoaVK5u9Wi8n2hMev 5cgKtTv7POlgRs/tkVbVxDf6U55SqvHeZqBLFO80MESZs+iS44dcgTnUgK8XHJ8d a1dI0tWSx+sPcHYXw7i1j8HADroYSxytW/3a4mKDgUjcHWZv3EIGi65imUTzTudD poCfwpFq/mEdBHZaIAw6AHsReopkYOXWT4EWpqnLhnnCs3hiTGS45MQna7plY9oz goLk/17hyAvVC/q+eh3KmksxMC1GVlnQbraQW7vfVF9TFVN3RCeP2PJMt0dFJ2eo 22U8WFjzVC8rdHAKyIN1IzRzOFcvlvBcm51j5XcjCSQbFjgazO8= =Mjq6 -----END PGP SIGNATURE----- --SU25kcM1CcxjPX8v56iRPjdICqoSA8OAd-- From nobody Thu Jan 30 12:58:08 2020 Return-Path: X-Original-To: xml2rfc-dev@ietfa.amsl.com Delivered-To: xml2rfc-dev@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BA22120073 for ; Thu, 30 Jan 2020 12:58:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.9 X-Spam-Level: X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=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 p5KWDKpqWKe1 for ; Thu, 30 Jan 2020 12:58:03 -0800 (PST) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 910A412006F for ; Thu, 30 Jan 2020 12:58:03 -0800 (PST) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:57801 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 1ixGsg-0006D1-PU; Thu, 30 Jan 2020 12:58:03 -0800 To: =?UTF-8?B?Q2VuayBHw7xuZG/En2Fu?= , xml2rfc-dev@ietf.org References: <871rrh2gyi.fsf@gundogan.net> <4079c56d-882e-c552-d6ab-b0e96119d58e@levkowetz.com> <8166DFDF-98D6-4DF4-8CF6-C34A522F9F7C@tzi.org> <87zhe424ta.fsf@gundogan.net> From: Henrik Levkowetz Message-ID: <50929e78-6fd6-2036-04ce-86407fc0950f@levkowetz.com> Date: Thu, 30 Jan 2020 21:57:35 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <87zhe424ta.fsf@gundogan.net> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="f08uKPkwDiiO6Is3U8RObLKRtLQOo9gl7" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: xml2rfc-dev@ietf.org, mail=2Bietf=40gundogan.net@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-dev] Wrong surname and fullname in BibXML Ref X-BeenThere: xml2rfc-dev@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2020 20:58:06 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --f08uKPkwDiiO6Is3U8RObLKRtLQOo9gl7 Content-Type: multipart/mixed; boundary="qfm33Wn1gS6hF82rcXqSidX41dwfMpInh"; protected-headers="v1" From: Henrik Levkowetz To: =?UTF-8?B?Q2VuayBHw7xuZG/En2Fu?= , xml2rfc-dev@ietf.org Message-ID: <50929e78-6fd6-2036-04ce-86407fc0950f@levkowetz.com> Subject: Re: [xml2rfc-dev] Wrong surname and fullname in BibXML Ref References: <871rrh2gyi.fsf@gundogan.net> <4079c56d-882e-c552-d6ab-b0e96119d58e@levkowetz.com> <8166DFDF-98D6-4DF4-8CF6-C34A522F9F7C@tzi.org> <87zhe424ta.fsf@gundogan.net> In-Reply-To: <87zhe424ta.fsf@gundogan.net> --qfm33Wn1gS6hF82rcXqSidX41dwfMpInh Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Cenk, On 2020-01-30 19:10, Cenk G=C3=BCndo=C4=9Fan wrote: > Hello Henrik, Carsten, >=20 > On Thu, Jan 30 2020 at 16:53 +0100, Carsten Bormann wrote: >=20 >> On 2020-01-30, at 16:36, Henrik Levkowetz wrote= : >>> >>> I would suggest that you use the equivalent bibxml3 entries directly = from >>> the datatracker. They have a better guarantee of being up-to-date: >> >> Can we fix the official ones as well? >=20 > @Carsten: so around 0.5\% are broken? Darn my luck (: >=20 > @Henrik: Thanks for the alternative link. I wasn't aware of that > location. I actually would prefer the other location for its rsync > capability. I just did another rsync update and I saw that some drafts > have been fixed (probably manually?). Thank you (: One question, though= : Yes, I did that manually. > While drafts of the form > bibxml3/reference.I-D.draft-mosko-icnrg-beginendfragment-.xml > have a correct author field now, the document > bibxml3/reference.I-D.mosko-icnrg-beginendfragment.xml has still the > broken format. I like to use the latter reference to always have the > latest ID version in the bibliography. Is there a way to also update > these ones? I'll have to do it manually. Should be better now. Best regards, Henrik >=20 > Cheers, > Cenk >=20 >> >> I=E2=80=99m thinking about running a comparison, but I don=E2=80=99t k= now whether datatracker would fall over from 114 k requests (the official= ones come in via rsync). Maybe I can start out without the 86 k I-D.dra= ft-* (i..e., version-specific) entries. >> >> Gr=C3=BC=C3=9Fe, Carsten >> >> _______________________________________________ >> xml2rfc-dev mailing list >> xml2rfc-dev@ietf.org >> https://www.ietf.org/mailman/listinfo/xml2rfc-dev >=20 > -- > Cenk G=C3=BCndo=C4=9Fan >=20 > Hamburg University of Applied Sciences > Dept. of Computer Science / Internet Technologies Group > Berliner Tor 7, 20099 Hamburg, Germany > Fon: +49 40 42875 - 8426 > Mail: cenk.guendogan@haw-hamburg.de > Web: https://www.inet.haw-hamburg.de/ >=20 >=20 >=20 > _______________________________________________ > xml2rfc-dev mailing list > xml2rfc-dev@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc-dev >=20 --qfm33Wn1gS6hF82rcXqSidX41dwfMpInh-- --f08uKPkwDiiO6Is3U8RObLKRtLQOo9gl7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl4zQz8ACgkQTptXS4+7 Fxoc5hAAhbIrgMfiAMa+i2PSxGOjm4kG3nlt3jgxWp64QbMnpGXh1b8XZ1UnjX1P DgGI22l7MWDjqGPg0qe9ebWmsUIevF3V5i2czVQCcS5coadRO0gAVmc+x+cPdBW+ 99leDStCfbTaMPYlbLCxJ93BJPOQK2taE4r3cL1+hzLiFuGgvQ2BtFNlIonf8j5g V1tBeaSmJHwKehMAXTuvQgFH6Ay0YS01zPn9oN7aLATzA+eZY9rX8gw9boHMSehi 7+q/y/q5h1meRJJbzt4WNFh6qLI5mT5QhoOYAEZRQ8qhxVsu5WZr1mA8yHf5cZ9O Ssfx/gdEMa1wAX/+QgSmCD+8SNVYwrJSI7GyvJDe9KzkPQ/HZ1HHOFz5neNivrRf ensWjNib7S2qynwWhTUXvG6IQlmikKQyN3W3Xm7FjxGRJPbTpmmcSKHORNTYQwgu Il/w+sgpIFUgG1Lw0nP7BC5UTOi2/lqQT50/29Rtyu7rmO2mwnhlp36EGGP4xTya QznQGWRGG+twb6llDbrIf1MxooHWOnz62Aew6S8intTg/FOx+tlMDBUpvZyWWvnc 5wSx9WzFG2447mWikhVmBF/9oPL+L4RFR8fde88B/ulzxEzY+Sq0c3JfsWdlTtX7 5KnqFrrqLSB3NNuNx4wxxsJCJHdvvNBhvFbvsm7ZCTLrEFUQGac= =uNvN -----END PGP SIGNATURE----- --f08uKPkwDiiO6Is3U8RObLKRtLQOo9gl7-- From nobody Thu Jan 30 13:02:46 2020 Return-Path: X-Original-To: xml2rfc-dev@ietfa.amsl.com Delivered-To: xml2rfc-dev@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49F3812006F for ; Thu, 30 Jan 2020 13:02:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.7 X-Spam-Level: X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (bad RSA signature)" header.d=gundogan.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 7ICMY8t-wYIk for ; Thu, 30 Jan 2020 13:02:43 -0800 (PST) Received: from mail.localdomain (trantor.gundogan.net [37.120.167.193]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F41F120058 for ; Thu, 30 Jan 2020 13:02:43 -0800 (PST) Received: from localhost (unknown [141.22.28.164]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by mail.localdomain (Postfix) with ESMTPSA id 466EE2CF62 for ; Thu, 30 Jan 2020 21:55:21 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gundogan.net; s=201712; t=1580417721; bh=r6C6gumTST0mjBspTc5GRiCJQy+l4l5OCH10eMoGEp0=; h=References:From:To:Subject:In-reply-to:Date:From; b=K7p375B8nHnVY61nU1uWsr7CJBysdDRsarWJ0kY2V3gAqQv5ezu2vA9lZQbVGyely 8CM5vYFc6S6HkkyKLxgHNdBNfaHPadtM67RwjE1K2b9lYGhTXR02pKBjNS+MkbRBjO LOqusPwMNIIvVEnqp291663gVdk5HsWXKnVTeXViXIvJsuHPlLHw3BjmI1U2zlILG5 BJuz7XgW1hFkpxm3KTwDbgsCenO+l3uVCRJuNN6HgY5nOaUHVvW8srK2/gVpmeqWAr utKwSetIKYbMfyNia87G7002dQJzx16fTpD/S/hS/azo/EhfxuqnUVYJOB3esj1W85 2BRCj2vCgISWA== References: <871rrh2gyi.fsf@gundogan.net> <4079c56d-882e-c552-d6ab-b0e96119d58e@levkowetz.com> <8166DFDF-98D6-4DF4-8CF6-C34A522F9F7C@tzi.org> <87zhe424ta.fsf@gundogan.net> <50929e78-6fd6-2036-04ce-86407fc0950f@levkowetz.com> User-agent: mu4e 1.2.0; emacs 26.3 From: Cenk =?utf-8?B?R8O8bmRvxJ9hbg==?= To: xml2rfc-dev@ietf.org In-reply-to: <50929e78-6fd6-2036-04ce-86407fc0950f@levkowetz.com> Date: Thu, 30 Jan 2020 22:02:40 +0100 Message-ID: <87y2to1wun.fsf@gundogan.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Archived-At: Subject: Re: [xml2rfc-dev] Wrong surname and fullname in BibXML Ref X-BeenThere: xml2rfc-dev@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2020 21:02:44 -0000 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello Henrik, On Thu, Jan 30 2020 at 21:57 +0100, Henrik Levkowetz wrote: > I'll have to do it manually. Should be better now. did a quick rsync and values appear to be correct now. Thanks a lot! Cheers, Cenk =2D- Cenk G=C3=BCndo=C4=9Fan Hamburg University of Applied Sciences Dept. of Computer Science / Internet Technologies Group Berliner Tor 7, 20099 Hamburg, Germany Fon: +49 40 42875 - 8426 Mail: cenk.guendogan@haw-hamburg.de Web: https://www.inet.haw-hamburg.de/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEO3dMsPVVAdvZ+Oc2o9vC90TUhNIFAl4zRHAACgkQo9vC90TU hNI8zg//Yo/7YfTyIfoMctvVPOZ7fF/8Kb/8s405h5jUzko+Zvn1PzLy6yQ7wMUX gF7Hp+UhOAp/vL7WS3VO9K1s4NkER5KD1Qm9wdFTUOlTJY5bfZBGej3StqJCB+v6 oXhusSdH6oz/ScOMs9MeaWSK6H/YHFgzgFooYWNax6uiX3IP2X3UyzZB4g0jP4aF KWiKCHRgzh3VMTq6BML1qAZe/eTmaziUZA/KI9VSMUUg3q3z4DIAr2Pp9oeZO0Ab +A35Y0aTDYQkol2SfJee6WgyHC/dd5LXDdEXbjNRqQ4LQQYTk8A2WX/724gcuCpV isiNXt7jjxstkffbXnhZbMsfTJYm2YEeXmIcYE7S3f3rFvHAo6P1eOmFka8TeSna B9JFT1llI3fss5IntJbRW1Bezd21KzJK/FyvUCt/k8jMug1SMo8B3NCn0FOQ1dsw RUImgpGj1no3zkBNZvYA5UnZQ63wMizDxwZe4dIMNSjIIYakoNp543Y7ghZcM6JA 84LhWurqZU1Iazcu8XraM7xX5/LLcH4KE6Y/lJBjzWdt3C0JOscjKCdHnK4w0yfI SHPLfOhlZoF6qu0IbiHpZ6ClWj5lSYFBUeg1PbGV3t4cvxBkQh7CXc350yo36cxX in2dJOJiU+s2mFlkFm0XHmwRZoPbT+z2mLqyO3GukxBfgPkm+l8= =+fjE -----END PGP SIGNATURE----- --=-=-=-- From nobody Fri Jan 31 03:41:41 2020 Return-Path: X-Original-To: xml2rfc-dev@ietfa.amsl.com Delivered-To: xml2rfc-dev@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACB8412081D; Fri, 31 Jan 2020 03:41:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jvI-pO_Ip9zh; Fri, 31 Jan 2020 03:41:38 -0800 (PST) Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5018A12081A; Fri, 31 Jan 2020 03:41:38 -0800 (PST) Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from ) id 1ixUg6-0007pw-2Z; Fri, 31 Jan 2020 03:41:38 -0800 To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org Message-Id: From: Henrik Levkowetz Date: Fri, 31 Jan 2020 03:41:38 -0800 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-dev] New xml2rfc release: v2.39.0 X-BeenThere: xml2rfc-dev@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jan 2020 11:41:40 -0000 Hi, This is an automatic notification about a new xml2rfc release, v2.39.0, generated when running the mkrelease script. Release notes: xml2rfc (2.39.0) ietf; urgency=medium * Provided a rendering for with reference targets which are part of a and don't have a reference tag. * Added a --pdf-help command-like option, and tweaked the order of some command-line options in the --help output. * Added a new filter for pdf-gneration library warnings, to avoid it appearing on every xml2rfc invocation. * Added a v2v3 converter for dates with non-numeric years. * Added an error for attempting to insert a missing XInclude namespace prefix when 'xi' is already defined as something else. * Fixed a bug introduced with the refactoring in [3438]. -- Henrik Levkowetz 31 Jan 2020 10:03:13 +0000 The preferred way to install xml2rfc is by doing 'pip install xml2rfc', and 'pip install --upgrade xml2rfc' to upgrade. If there are system- installed python modules which pip will not upgrade, you may have to use 'pip install --upgrade --no-deps xml2rfc' and install dependencies manually. The new version is also available through SVN checkout, with 'svn checkout http://svn.tools.ietf.org/svn/tools/xml2rfc/tags/cli/2.39.0' Regards, Henrik (via the mkrelease script) From nobody Fri Jan 31 04:49:29 2020 Return-Path: X-Original-To: xml2rfc-dev@ietfa.amsl.com Delivered-To: xml2rfc-dev@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AF011200B3; Fri, 31 Jan 2020 04:49:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NlbDdULvuszN; Fri, 31 Jan 2020 04:49:18 -0800 (PST) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4F25120804; Fri, 31 Jan 2020 04:49:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1580474955; bh=cus10TVYjSaw2e+ICRJaVTkCFYvMZir8rSkQxYFQ7KA=; h=X-UI-Sender-Class:Subject:From:To:Cc:References:Date:In-Reply-To; b=OzW7R9ZJx9zhmA86JKr96Q1/goivKiWMN/i53yGngWdJi7ro++8WUX4Vtohx7vnis 8yZgOfOpbC7hQsuKjqVNVFwQlk26QEi/j+eUPa+xWNE0EIZsaSpdctd25nwpkiugt6 CFu3ciWkyR7wDyPF4GY6ILVF3KgxNEAEtqqHqiP8= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.1.81] ([217.91.35.233]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MmUHj-1jOHyl45B3-00iPja; Fri, 31 Jan 2020 13:49:15 +0100 From: Julian Reschke To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org References: <973bc456-19af-76e8-d8e5-ef506f587fe7@gmx.de> Message-ID: <3725603a-fe71-adbc-4c66-8669e2bce292@gmx.de> Date: Fri, 31 Jan 2020 13:49:10 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2 MIME-Version: 1.0 In-Reply-To: <973bc456-19af-76e8-d8e5-ef506f587fe7@gmx.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:tJx1qS5rahqCamZLq17SsWzS5IR4uoBaEsyUWjKScYjsKwDajRV fOly+wHbZHqHM2RS2vSi+OdensTinTRWL9v3iFGE49NIs+YaomR6gKigI1yhjYs5XYXSx1k KDjYWuYMHmz3PNBRqI55vNOpmV29x2dPl8eGQNONip027bKrnhu3P0AkAjhD1KgOx2CD8dU 4CFmc4qeOp+rsPmCyQB5w== X-UI-Out-Filterresults: notjunk:1;V03:K0:kFTpbfBxuRM=:pcMtC1OOBf8vgeb5ZWDl/M ms8lLbRZ1wTe1VJjpL40gAIxxq+aneiVjuHWHjRZnLcJ+FtnxsP7Rp+Sj8XLNPAPA6yI+EIuP dvkKLC9V0iCq4a0mazPBIK45ijOYL5aCN/rO8Uiqi/4yztNQqFDSUd89oGSKI60h+IZpBgj7p cUBhH4QkwZ58W9YTFgOaWXtNZzS2FDeLVXN3AQTUDTl7mbTRZALOR8UmzVtBOQtLjX/FE8/Po U5mgpltXtvX1UhqaoplTTKYPKovKi1FkLR0ulO0ebMR7M9jv3nbMqzu4T1Vektp4NCl5u6AA/ 3Whsc/Ndabs1/+CYiSVDlo/+aWviL9i7dWWCCbxcdzasdiOlOW2bWUWA2e2Lxj+mU9Kv5R8z6 pYLsXKB5D+K2byk3QCHebNZOQQvdJ+S4w7oW98aXfrWqqvUXbVawvXwEvd4Vx+4n2nCRjOkQa MQZsKQWflZ8cLx0wxaG/2y84rkb7B3a3PkDc+YonsZVLf+4rVa7IISVxs3JV+J3nywBk2yaLS FHKvL3UBi/akZs5uaXZMTk6I0oSwHVeiqqjmZuFS7F30ctkuRoZo7EFhH82IdTr4PX5jZ35IK qeMCiLclBvuyWQL1GYD8INJyrdEM2wS8mqH/+JZLA0YmIP1WwkamPQgn0JzEPYe+afC3rAqRd wjR+R7Y/fGoR9Su7ZvyUSU9e6ATPZKtW36ImMSaiCuU3HH+KArohprvU2RggdJRmfZlv5rWNz EqovCFv8khf4BRhH1dvbXcEaNbWlatg4RyBWnrkEDE20TLPBdzVpJUWs+t3+ybdqv61B8ySgq EyYG2n6qxQ49x+YiwEljstSpMaZMZmEATEZfsrKhcICLPluuGX/wLhffodiXnuSdE6rqp79cR J5QXaf3QVpfDDhmt5cRWx8okJiNd4/9H5rm5E3gTBUU/mGAuK0Piq2UwQJeezpWzIPTEuhzuM fRexJOhAgmY3QMQLSNyudyPqrVV1nCnnVJD9p7dm+IkDmAzfB50Mg+hlpSJ+9GUawj9MCSIWf Qy8ZUmd6BUaP3ASMD1t00YySf4AMJS+OFqqiTsS8pqVhBh/osq4jl35bgTUFDBuRQtgXnJO5F xgeEbtIpGqKO19d9V2fh5ygEvvmut0uQvKmf4DqaPD4ATtlZu+zVvjENaQdNzqR+vAjLiBXop JIUKZq+YBtBr64jycnGYNfMk87EMwxGHIi1/eGV0PI6MQ9ksvb9RBMBzSi0KxZ6xhMJ7l6hH3 xHH4ir9ABzlEhx5+9 Archived-At: Subject: Re: [xml2rfc-dev] [xml2rfc] New xml2rfc release: v2.38.1 X-BeenThere: xml2rfc-dev@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jan 2020 12:49:21 -0000 On 20.01.2020 19:33, Julian Reschke wrote: > On 20.01.2020 16:33, Henrik Levkowetz wrote: >> >> Hi, >> >> This is an automatic notification about a new xml2rfc release, >> v2.38.1, generated when running the mkrelease script. >> >> Release notes: >> >> xml2rfc (2.38.1) ietf; urgency=3Dmedium >> >> =C2=A0=C2=A0 * Added a preptool check for numbered sections occurring a= fter or >> under >> =C2=A0=C2=A0=C2=A0=C2=A0 unnumbered sections, and changed the code for = Reference sections to >> =C2=A0=C2=A0=C2=A0=C2=A0 not emit section numbers if the previous secti= on was unnumbered. >> =C2=A0=C2=A0=C2=A0=C2=A0 Fixes issue #433 >> >> =C2=A0=C2=A0 * Refactored the code for reference anchor to display stri= ng mapping, >> =C2=A0=C2=A0=C2=A0=C2=A0 locating it in a base class method.=C2=A0 Upda= ted it to honour the >> symRefs >> =C2=A0=C2=A0=C2=A0=C2=A0 setting.=C2=A0 Fixes issue #476. >> ... > > The above may have broken s to children of . See > . > ... I note that I didn't get a reply, and the bug that I reported is still labeled "new". In 2.39 the behavior indeed changed again; the processor now doesn't abort anymore, but the text inserted for reference group members lacks the brackets ("[....]"). Best regards, Julian