From nobody Fri Feb 1 14:08:33 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A13DD130EC5 for ; Fri, 1 Feb 2019 14:08:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.041 X-Spam-Level: X-Spam-Status: No, score=-2.041 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.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 gyEIcT7IoF_r for ; Fri, 1 Feb 2019 14:08:30 -0800 (PST) Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (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 C48F5130EBE for ; Fri, 1 Feb 2019 14:08:29 -0800 (PST) Received: by mail-lj1-x233.google.com with SMTP id x85-v6so7134310ljb.2 for ; Fri, 01 Feb 2019 14:08:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=dtW5vx8FSW5Am/rMTxeM1HoAVUnmyoepqd1LyXlf0rA=; b=09R6U0iq2g+fPNZY38mRQhLhJ9gZhvsvO1tMq62xPXRwnlsEBypdYPhuhlDahLaZe7 xJxm8Nfnp8KS/sHWOQ0/N9ckBgzx4TjCOtj95LfkncJ8V4/kGEQXQo54An7nzu7RBvgO fCs3g3fkjkjPpnFhua5I36y9ZqWnEl0F6QhnFZtK8O6CR5Yyk10n/djj9r6OadKMRmrf /QjIL/CI0rnv8HWJTV7lYCQUWke5GS+KEO/HYB33owszm4Gaca2RnAvfwkKvKpK63tUY ifzN0ra103TOxZx0B4YxHXlhtENIu2+HVc4o2SoPqj1ZIJbHqH9xwAcmcUrDzAVu2sD0 Qyow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=dtW5vx8FSW5Am/rMTxeM1HoAVUnmyoepqd1LyXlf0rA=; b=D/ROe+Vf0cftcyIj33c0vfGpTsW7aawNBtvhJMlRJFnZwWZ+H7e8G32oA0Mgq4LQ4u cmlianeAA0FrGGj3ST31RF0qoVfX2D/NGH3iTTyTKXOkPg3fbktkfbVY1WLrHG8lYJ18 Ufb1tnqmHXI6ixCJ3NwWPCBa/AFTb/09r+0jJfeIokltJ3565Q5xiRYc6tTQN0Xxa5L/ LPrzX+o395TbS92BmTPAqwbNcZFcsgN4sRglknWWRMbEpwJ/ILqtEy6Fh/QwCYC/H/UL hdHrqp7cHUPxYnYOFj9CU4xDkqPRWPm6VXJRY4IqpiF+AEtfDWscEDMTsWfH8YsKNPOD Kt6w== X-Gm-Message-State: AJcUukcW5XaAyqlk24b81Wfo2wvTqlXYWpIMfFoJt59+lGix3vQyM062 kFv3zWIQRw7LhAjrWuLzLvPV7hP2hwwDkDF9rj9DX7snim4= X-Google-Smtp-Source: ALg8bN6k/XRR+SZTfRwQTuHO/bLq98whCnA8ES/rueuNmk20LXCTVt6HvH5TztcHjodjClmN5nPs8WFF25RDeIYnVQw= X-Received: by 2002:a2e:5dd9:: with SMTP id v86-v6mr32663081lje.86.1549058907467; Fri, 01 Feb 2019 14:08:27 -0800 (PST) MIME-Version: 1.0 From: Eric Rescorla Date: Fri, 1 Feb 2019 14:07:51 -0800 Message-ID: To: tools-discuss Content-Type: multipart/alternative; boundary="000000000000ea8b120580dc611a" Archived-At: Subject: [Tools-discuss] Why does xml2rfc download over HTTP? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2019 22:08:32 -0000 --000000000000ea8b120580dc611a Content-Type: text/plain; charset="UTF-8" Hi folks, I recently went to build a draft and got a pile of errors about how the references didn't parse. Digging into things a bit, I discovered that the reference was the page from a captive portal on one of my flights. I'm not sure how this happened, but looking at xml2rfc, it appears that it tries HTTPS URIs and then HTTP URIs, which seems like it's going to have the wrong outcome in the situation where the captive portal blocks HTTPS and intercepts HTTP. Is there a good reason to continue to allow HTTP URIs in the tool? -Ekr --000000000000ea8b120580dc611a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi folks,

I recently went to= build a draft and got a pile of errors about how the references didn't= parse. Digging into things a bit, I discovered that the reference was the = page from a captive portal on one of my flights. I'm not sure how this = happened, but looking at xml2rfc, it appears that it tries HTTPS URIs and t= hen HTTP URIs, which seems like it's going to have the wrong outcome in= the situation where the captive portal blocks HTTPS and intercepts HTTP.

Is there a good reason to continue to allow HTTP UR= Is in the tool?

-Ekr


=


--000000000000ea8b120580dc611a-- From nobody Fri Feb 1 14:41:16 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E607130ECE for ; Fri, 1 Feb 2019 14:41:14 -0800 (PST) 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_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=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 8eSDjUYBHdGc for ; Fri, 1 Feb 2019 14:41:11 -0800 (PST) Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) (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 B9B9E130EBE for ; Fri, 1 Feb 2019 14:41:11 -0800 (PST) Received: by mail-vs1-xe2c.google.com with SMTP id z3so5208018vsf.7 for ; Fri, 01 Feb 2019 14:41:11 -0800 (PST) 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=ygXyhGJgTBgBmNVmznsIMfji1pE6FblcYP3Xa+tjRl0=; b=YFIE6KYQan+g/MiWXzU6AjCV5tuIGoMd+XIaHzXWaSqObhqjKuihmL9QPGzsyr0dSN FE64Q6E2jTUg2oaCbKs0XkhVM7UQFtgxyJkmWYBBkX/tXWGsuIjif+RaRUVJHmaaKoWQ TmmA5jtln7NyXmigF6UAkd4ID8F/A7mUDbGgtIkka4AuUpkqJlhip8S6BQJUAE6dLMHh DAU1G+hseyo9UuNzauG0Vs37WFoOkf+GAVREONAglDgelCllEalZkE0xp8Qjd1xFYq6l rq+oDHbHUe7oIzh7wXBeJt8R9rj+R+++nioC170S/GMPhJm3+PrEzypEorGrHfoHyNPd QGwA== 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=ygXyhGJgTBgBmNVmznsIMfji1pE6FblcYP3Xa+tjRl0=; b=f3EUJWo/KXKBB8h07HvqW/bVD9ak4gieqaJ1kiukNSw9jdkd9gXUeuGdXg7gYTJdvo o1uF7i1r2z9eTKxku+4a+OdeWlPUjzv0ctNvcq9Leuu7TcTeLsFLpy8vV9s2D9wvzJyS 6n4lJ4EWf0fFjdyOeEETiiC8G7L66E28Ftnz4z9jwXlYza0SZujnFEea2hBPPzOcgNjU GTmfb/qmuxnBJ1bXkd1+wsJMIBnmYINxCOGRy1eAA3+dNV6jU3OMVyK8sAAFyxNnl+Wr xG6sn5nDi0H1jahMA5IhPtFtwg0OOPV8ILgMBFQhTaq1u4n9peGs1qjHXkhxWcvYCJRm OMTg== X-Gm-Message-State: AJcUukdguacb0c+qk/UZEdq6EVA5Lnbjln4e+/RKdsHuKgY/YOxV8UOT IWtyHYDm3lJ+yLCiu89CjM9ZZlXQW06mXQOrOg2Db6/p X-Google-Smtp-Source: ALg8bN52LsuVFHCzFZEKHaSav4aitjVMxFEZLv1ds8AsCZzVNEauS8tmHpe/EG5rRioSDOvGh3Mpazr/89P43Si4fKs= X-Received: by 2002:a67:e15e:: with SMTP id o30mr18437250vsl.66.1549060870526; Fri, 01 Feb 2019 14:41:10 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Richard Barnes Date: Fri, 1 Feb 2019 17:40:54 -0500 Message-ID: To: Eric Rescorla Cc: tools-discuss Content-Type: multipart/alternative; boundary="000000000000ec5e7d0580dcd601" Archived-At: Subject: Re: [Tools-discuss] Why does xml2rfc download over HTTP? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2019 22:41:14 -0000 --000000000000ec5e7d0580dcd601 Content-Type: text/plain; charset="UTF-8" In particular, this seems to be the patch necessary to resolve the issue: Index: trunk/cli/xml2rfc/parser.py =================================================================== --- trunk/cli/xml2rfc/parser.py (revision 2965) +++ trunk/cli/xml2rfc/parser.py (working copy) @@ -53,8 +53,6 @@ no_network=None, network_locs= [ 'https://xml2rfc.ietf.org/public/rfc/', 'https://xml2rfc.tools.ietf.org/public/rfc/', - 'http://xml2rfc.ietf.org/public/rfc/', - 'http://xml2rfc.tools.ietf.org/public/rfc/', ], rfc_number=None, options=base.default_options): self.quiet = quiet if quiet != None else options.quiet On Fri, Feb 1, 2019 at 5:08 PM Eric Rescorla wrote: > Hi folks, > > I recently went to build a draft and got a pile of errors about how the > references didn't parse. Digging into things a bit, I discovered that the > reference was the page from a captive portal on one of my flights. I'm not > sure how this happened, but looking at xml2rfc, it appears that it tries > HTTPS URIs and then HTTP URIs, which seems like it's going to have the > wrong outcome in the situation where the captive portal blocks HTTPS and > intercepts HTTP. > > Is there a good reason to continue to allow HTTP URIs in the tool? > > -Ekr > > > > > ___________________________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/tools-discuss > > Please report datatracker.ietf.org and mailarchive.ietf.org > bugs at http://tools.ietf.org/tools/ietfdb > or send email to datatracker-project@ietf.org > > Please report tools.ietf.org bugs at > http://tools.ietf.org/tools/issues > or send email to webmaster@tools.ietf.org > --000000000000ec5e7d0580dcd601 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
In particular, this seems to be the patch= necessary to resolve the issue:

Index: trunk/cli/x= ml2rfc/parser.py
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D
--- trunk/cli/xml2rfc/parser.py (revision 2965)
+++ trunk/cli/xml2rfc/parser.py (working copy)
@@ -53,8 +53,6 @@<= /div>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 no= _network=3DNone, network_locs=3D [
=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 'https://xml2rfc.ietf.org/public/rfc/',<= /div>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 'h= ttps://xml2rfc.tools.ietf.org/public/rfc/',
-=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0'http://xml2rfc.ietf.org/public/= rfc/',
-=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0'http://xml2rfc.tools.ietf.org/public/rfc/',
= =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 rfc_number= =3DNone, options=3Dbase.default_options):
=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0self.quiet =3D quiet if quiet !=3D None else options.quiet

On Fri, Feb 1, 2019 at 5:08 PM Eric Rescorla <ekr@rtfm.com> wrote:
Hi folks,

I recently went to build a draft and got a pile of errors a= bout how the references didn't parse. Digging into things a bit, I disc= overed that the reference was the page from a captive portal on one of my f= lights. I'm not sure how this happened, but looking at xml2rfc, it appe= ars that it tries HTTPS URIs and then HTTP URIs, which seems like it's = going to have the wrong outcome in the situation where the captive portal b= locks HTTPS and intercepts HTTP.

Is there a good r= eason to continue to allow HTTP URIs in the tool?

= -Ekr




___________________________________________________________
Tools-discuss mailing list
Tools-discuss@i= etf.org
https://www.ietf.org/mailman/listinfo/tools-discu= ss

Please report datatracker.ietf.org and mailarchive.ietf.org
bugs at http://tools.ietf.org/tools/ietfdb
or send email to datatracker-project@ietf.org

Please report tools.ietf.org bugs at
http://tools.ietf.org/tools/issues
or send email to webmaster@tools.ietf.org
--000000000000ec5e7d0580dcd601-- From nobody Fri Feb 1 21:41:03 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E2EE128766 for ; Fri, 1 Feb 2019 21:41:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 rU-F6N4MX6N8 for ; Fri, 1 Feb 2019 21:40:59 -0800 (PST) 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 36D4B124D68 for ; Fri, 1 Feb 2019 21:40:58 -0800 (PST) Received: from [192.168.178.20] ([217.251.142.231]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Mam2Q-1gb1Fn13gQ-00KQUZ; Sat, 02 Feb 2019 06:40:53 +0100 To: Eric Rescorla , tools-discuss References: From: Julian Reschke Message-ID: <6d102ee0-2cb2-d789-d98f-e8e973a163e6@gmx.de> Date: Sat, 2 Feb 2019 06:40:52 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:BHt5vvGK0K7V9oRLqdT1rqcPRz6Qon8Tf7G4HKUJ+0Ltml03rPn +clDI3BoCIDJ5I/qmYG3mtV5lezoX/5jS8efBgnLp3ZVWeTy4bdblzbI6c0gZHUvVxmhl+Q Umlp0EOCygwndh/ntSL3EN9KyNai64mLEHXHrNKFl9eM7iSjmvOqE1/MP0F2eC1HvEL1W8s Nx8pE6LnVEFViHqqJNY6g== X-UI-Out-Filterresults: notjunk:1;V03:K0:y3CbQWQlPbg=:pw4w8gImD1B9DdaLhQjxwX rpsqsxz3bhMoMVNB8Ny+QMRKCE+KxqQvZVFTNPJC+nrtKFF2SuptBNMefP9ROEtKUB5cJntzC b5etJRj/c86JCDCzfXiUHyDt+She/7DwjxxjoiPWazgU+64b+b9GlFVImNA6IuyqIRbTvvX1E wl2/xPofzC/e7KmCpU+gE4tw2UkKVBvszd5or2OUizrDKNogPwcgCysbDuv075mhknQ9wbZH+ JskC/a4UZ7cJxlumMi8weL7jaIcpKh8n+qZ2f2bt0x3yt0r4JOrwksiqMy7OHb+YKm/tW1td3 2oRPgxVjc1y1aTh1pHE0FlCQzSv8R8pgIrNA1BjojCWx8yNp0kgc1U99NnRLqAhrdH/rTlw2Y D3l9NIsIWn784xXmhva+H3SEFGLWCsrAurTJK9+/olcBqcs90cEPj2V5Wv2Rb7RQuty+jnwYn Cfg8Hl03pZIFEz9MBdiEWW1L0j4o/oPyeuzidWJU/f2oCWtdMpDwIGpN2928OCvJJUL12opto d+w8BbwjRdOVKukAyE/zbg17exLMgbtxgRnwxrgEQTHFf3KnBsrdhRBpyiqqfTHwBcWfLjMOo ppku+noErEGMpj6Rn6FjLtGSU1uLLt20VioabneP5po56m1mSNKd/1UNAehP861zx+OuaJmGz /LXLfu8pJJ2qEQY7zNccSl5FP0GRmYJwnrLnVRJLgR8p2vsveF8bbMZD8Fl3XyVmIew9GQjy2 7XkRcmmbeDXfQWPTijl2FiZRiBjyJqXr2tQQOEM15z1TIg3ubTqIhL+ZDxBBvii2VeMlO4BEq N5Yz/MdlR7a4+WqnDPa61c6zyBiNf8jIADHM6wyBAgEyxwJ5zRRIZvVzS4NNE1aA8F+LHYr3o dySgTlpJ4oUlXk+KROqYpos0f5DO8iWUSc62RuJwDL3vMyrzmmnL0HpN9t+LWWV15abRTisSd iReXvY9F7QQ== Archived-At: Subject: Re: [Tools-discuss] Why does xml2rfc download over HTTP? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2019 05:41:02 -0000 On 2019-02-01 23:07, Eric Rescorla wrote: > Hi folks, > > I recently went to build a draft and got a pile of errors about how the > references didn't parse. Digging into things a bit, I discovered that > the reference was the page from a captive portal on one of my flights. > I'm not sure how this happened, but looking at xml2rfc, it appears that > it tries HTTPS URIs and then HTTP URIs, which seems like it's going to > have the wrong outcome in the situation where the captive portal blocks > HTTPS and intercepts HTTP. > > Is there a good reason to continue to allow HTTP URIs in the tool? The easiest fix is to always specify full HTTPs URIs for references or to inline them in the first place. Best regards, Julian From nobody Sat Feb 2 05:29:34 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB967128D09 for ; Sat, 2 Feb 2019 05:29:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.041 X-Spam-Level: X-Spam-Status: No, score=-2.041 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.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 9Yuw3wOvHdfz for ; Sat, 2 Feb 2019 05:29:31 -0800 (PST) Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (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 AFEFA130DF1 for ; Sat, 2 Feb 2019 05:29:30 -0800 (PST) Received: by mail-lj1-x235.google.com with SMTP id k15-v6so8149705ljc.8 for ; Sat, 02 Feb 2019 05:29:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wXDQMm2+nvyyEnnBOODZv8ftr5S/wXW9563f5elFC7k=; b=KwO0nE95oGh3dr7wjD61hr2JJsRj4KbhBmvBTKJpMrhypYikgF96lFxXOMZCATfKJT lvbjMJkTsQbn8LFPL02VQQTn+g5J9lBy/CO5/PP4kHpnkgW2N5B/X+GN3rFTFi2XXeMf gWjUPgG5oOx5KCZRiFnUKcT6/r3SyD/kXXYpVTf13q0ypK6A410t2eVF5h3kW7eImBbF iBgVNuoik16rXylyyQPFuuoow9sHGWZMr07hA3zo3QbJlmBfTOFDkXs54Plh2HRS/ldv 4TjPUbHrMVFJUN1ibWhny9uy4OQ3le4sSkMECV6vgFwaLbPlVrS6VRhp2DavVkAUgeJ0 vgZg== 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=wXDQMm2+nvyyEnnBOODZv8ftr5S/wXW9563f5elFC7k=; b=qDQowJxnxW7XVks/cPfg9MRc4wfC+sz9h/bTbZcRqY3fXlx+2/1vsw6yrtKVHjk9II k5Stc70K3C/NZuAV5W8yNl0S0SRDm/ZnjX6a+xiOb5nwCbGzXcX0BPqcEEc6Tbm2C11A 9d3b2cIJglZ0SP3PFhzATLA5O/thfsQhmtn34/l9pOC/6MJnjWBmBNx/D3q9hnCrZFB1 C7nsFTowK91vZxIO8amsL/vu2BWNyqLueIanX8lldE8Oe3O8I1Qo1nJGxdWbdGCiz4qy dkkyYszXdD6FnP73htm8uOpciUcWqzHpLn6NbFIPoC4ym1V1tlGmsZcPKrHsue2XFkpS JaLg== X-Gm-Message-State: AJcUukcYix9gYt6V73UrKYIriASFr0wKgLkrqaim4KtXXgbf/ID+rrZw kywvEsv218zSmphqjfYJUtVEcQ+Zo2jPp9hsb+OcnQ== X-Google-Smtp-Source: ALg8bN4xV3RbeNQgLn5bwwbUCV+bzdnoHW6UlmQQxP63Pm9zn1AdJK7Uvp5ju+sDu/lmDkMVgrqlrgvxpENtAtc0h7g= X-Received: by 2002:a2e:91d1:: with SMTP id u17-v6mr35061393ljg.160.1549114168852; Sat, 02 Feb 2019 05:29:28 -0800 (PST) MIME-Version: 1.0 References: <6d102ee0-2cb2-d789-d98f-e8e973a163e6@gmx.de> In-Reply-To: <6d102ee0-2cb2-d789-d98f-e8e973a163e6@gmx.de> From: Eric Rescorla Date: Sat, 2 Feb 2019 05:28:51 -0800 Message-ID: To: Julian Reschke Cc: tools-discuss Content-Type: multipart/alternative; boundary="000000000000c059e40580e93f96" Archived-At: Subject: Re: [Tools-discuss] Why does xml2rfc download over HTTP? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2019 13:29:34 -0000 --000000000000c059e40580e93f96 Content-Type: text/plain; charset="UTF-8" On Fri, Feb 1, 2019 at 9:40 PM Julian Reschke wrote: > On 2019-02-01 23:07, Eric Rescorla wrote: > > Hi folks, > > > > I recently went to build a draft and got a pile of errors about how the > > references didn't parse. Digging into things a bit, I discovered that > > the reference was the page from a captive portal on one of my flights. > > I'm not sure how this happened, but looking at xml2rfc, it appears that > > it tries HTTPS URIs and then HTTP URIs, which seems like it's going to > > have the wrong outcome in the situation where the captive portal blocks > > HTTPS and intercepts HTTP. > > > > Is there a good reason to continue to allow HTTP URIs in the tool? > > The easiest fix is to always specify full HTTPs URIs for references or > to inline them in the first place. > That seems like it's kind of working in the wrong direction. People shouldn't need to provide the URLs for IETF citations at all, just like the way they don't when using markdown. -Ekr > Best regards, Julian > --000000000000c059e40580e93f96 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Fri, Feb 1, 2019 at 9:40 PM Julian= Reschke <julian.reschke@gmx.de= > wrote:
= On 2019-02-01 23:07, Eric Rescorla wrote:
> Hi folks,
>
> I recently went to build a draft and got a pile of errors about how th= e
> references didn't parse. Digging into things a bit, I discovered t= hat
> the reference was the page from a captive portal on one of my flights.=
> I'm not sure how this happened, but looking at xml2rfc, it appears= that
> it tries HTTPS URIs and then HTTP URIs, which seems like it's goin= g to
> have the wrong outcome in the situation where the captive portal block= s
> HTTPS and intercepts HTTP.
>
> Is there a good reason to continue to allow HTTP URIs in the tool?

The easiest fix is to always specify full HTTPs URIs for references or
to inline them in the first place.

That= seems like it's kind of working in the wrong direction. People shouldn= 't
need to provide the URLs for IETF citations at all, just l= ike the way they
don't when using markdown.
-Ekr


Best regards, Julian
--000000000000c059e40580e93f96-- From nobody Sat Feb 2 05:32:26 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC007130DF1 for ; Sat, 2 Feb 2019 05:32:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 eZaGgAHyGT61 for ; Sat, 2 Feb 2019 05:32:23 -0800 (PST) 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 C0512130DEF for ; Sat, 2 Feb 2019 05:32:22 -0800 (PST) Received: from [192.168.178.20] ([217.251.142.231]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Lh7M3-1hSZs50lSp-00oUun; Sat, 02 Feb 2019 14:32:18 +0100 To: Eric Rescorla Cc: tools-discuss References: <6d102ee0-2cb2-d789-d98f-e8e973a163e6@gmx.de> From: Julian Reschke Message-ID: <71c2d408-6603-aec3-faba-d1a15bfa1a04@gmx.de> Date: Sat, 2 Feb 2019 14:32:16 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:hO5FGZlG9g3gPJpU6ykXyIz8lPaLgwJPNqS3qSgt9VxvbbxjaCo RqQNVLdBhFM/wP8/s8m8CsjLQpXfGzxMkQIhYZZdWmqbk3QkBN+Y2odx+RqMogUho5sx0mp FUevyjrBeEbjenlf5or6nYlvREseU5jvx70rVHTZrbMPUIwzKmZTA+w41FMkTxWnzfnneJm wO4mkafYefVIvMQvNdTBA== X-UI-Out-Filterresults: notjunk:1;V03:K0:u0WJdC/UvA8=:lHcKlmq1ecY3CfznDn9Z8K /FPWkYxggesXVuzC6dAD2YBtz1c6TeneuATE33A8txZWxBboZ87+mOo5VpAmr6yg+9gZpiU70 Lou1ohzdNM7TiCm0QfgF7HDlS9cP4LoaHp6h4XnQkrgpPMQGcKSXe1LvItasjtZNtU7cYRHTv 6hMnDTvnEre8mdAvUbmFkX83qPGvT0i8E+3Mn/1Am58zOvCEu6cVFsCMNb434cKJuYhvlzqeK lJEEBG/2S5WCyr4Ydt3/20dzN2tpI9jJEEDrPCFjI/SuUf4WwOKPT+Mr4yi/BiIxm8CkVOO4N tNamxncfQF4/ZRh9tzj+z0eqKmn8Zu0LBrQtYpTYTfoVSIcck3J99/8ZtM3S/AV6ItDlUL1/7 WMkyAmn5bEV8yAncDyeCvjC8haW4QCUX/0dmlZkphmKOt5pmZYODKZcoHGq+gzi/T1JPL4AuK NBFkMAoZASsxhvdB7V7eehF387xEUUQ0AwTMdpB8PRtbqJa5s24DnUJCA0XeUwT4pd3881veM HOlbqRUP4P0JbqMXYQJCSCf44R9qiLVCxpB5dOGIG6pvUI5EyUsPvbKmfF0b+RTxXMThcnx0+ DliXySZfAIgjd7PxxLyWB89wrLeCr/yd5UJvatL0HqM4mQZ6BDYyC6zTz6hmfpFc94r0Qsj1x n1Sl4OJFAPrBhsAzaXVN38FdFZ7Qx0GeOugHd7KhO1P910SVqI9aW6Wj/BpwaxxUL9bV0wjaL BZRRdbjvQHsqDNyjBqFs4Oe7YB2HEgjUykz3l/R7b1NwzlYfjyrXKBNp2Nedj6LMIMTOwcM5v 2pkloeeC4CpP5bMsLNRU5mbgUmEvkTQT04JQOv6c/Vx2k8zQtH2ahnCxlx7UnD1HW273AxooN 4CTI6P9yGqRIbPCmM6jDzQjcIiYMjqfnbAKBFkec06T/mm3iYHdPrWytJ+YM1VPeIHqR/DqiB XyTEL+RBOxQ== Archived-At: Subject: Re: [Tools-discuss] Why does xml2rfc download over HTTP? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2019 13:32:25 -0000 On 2019-02-02 14:28, Eric Rescorla wrote: > ... > That seems like it's kind of working in the wrong direction. People > shouldn't > need to provide the URLs for IETF citations at all, just like the way they > don't when using markdown. > ... Well - sounds like you should do a suggestion for the V3 vocabulary then... :-) From nobody Sat Feb 2 05:38:10 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B03A128CE4 for ; Sat, 2 Feb 2019 05:38:09 -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] 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 yRSnaYhLMAEp for ; Sat, 2 Feb 2019 05:38:06 -0800 (PST) Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 E877A126C7E for ; Sat, 2 Feb 2019 05:38:05 -0800 (PST) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [IPv6:2001:638:708:30c8:406a:91ff:fe74:f2b7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id x12DbvBP010373; Sat, 2 Feb 2019 14:38:02 +0100 (CET) Received: from [192.168.217.106] (p54A6CC50.dip0.t-ipconnect.de [84.166.204.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 43sFQr6Pmzz1Br6; Sat, 2 Feb 2019 14:37:56 +0100 (CET) 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: Sat, 2 Feb 2019 14:37:56 +0100 Cc: Eric Rescorla , tools-discuss X-Mao-Original-Outgoing-Id: 570807474.4031219-176c7f589621ebb445795129361448a9 Content-Transfer-Encoding: quoted-printable Message-Id: <098AAA72-450A-4376-983F-57F0C667C212@tzi.org> References: To: Richard Barnes X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [Tools-discuss] Why does xml2rfc download over HTTP? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2019 13:38:09 -0000 Right. However, who ever fixes this should keep in mind that software = installed on a laptop does not always have access to a good set of root = certificates (the browser is likely to, but Python software may not have = access to the browser set), so it would be useful to have an escape = hatch of some kind (preferably through environment variables, so complex = Makefiles don=E2=80=99t have to be touched). Maybe adding a little bit of robustness to the download process (e.g., = don=E2=80=99t cache it if it isn=E2=80=99t valid XML) would also help. Gr=C3=BC=C3=9Fe, Carsten > On Feb 1, 2019, at 23:40, Richard Barnes = wrote: >=20 > In particular, this seems to be the patch necessary to resolve the = issue: >=20 > Index: trunk/cli/xml2rfc/parser.py > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- trunk/cli/xml2rfc/parser.py (revision 2965) > +++ trunk/cli/xml2rfc/parser.py (working copy) > @@ -53,8 +53,6 @@ > no_network=3DNone, network_locs=3D [ > 'https://xml2rfc.ietf.org/public/rfc/', > 'https://xml2rfc.tools.ietf.org/public/rfc/', > - 'http://xml2rfc.ietf.org/public/rfc/', > - 'http://xml2rfc.tools.ietf.org/public/rfc/', > ], > rfc_number=3DNone, options=3Dbase.default_options): > self.quiet =3D quiet if quiet !=3D None else options.quiet >=20 > On Fri, Feb 1, 2019 at 5:08 PM Eric Rescorla wrote: > Hi folks, >=20 > I recently went to build a draft and got a pile of errors about how = the references didn't parse. Digging into things a bit, I discovered = that the reference was the page from a captive portal on one of my = flights. I'm not sure how this happened, but looking at xml2rfc, it = appears that it tries HTTPS URIs and then HTTP URIs, which seems like = it's going to have the wrong outcome in the situation where the captive = portal blocks HTTPS and intercepts HTTP. >=20 > Is there a good reason to continue to allow HTTP URIs in the tool? >=20 > -Ekr >=20 >=20 >=20 >=20 > ___________________________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/tools-discuss >=20 > Please report datatracker.ietf.org and mailarchive.ietf.org > bugs at http://tools.ietf.org/tools/ietfdb > or send email to datatracker-project@ietf.org >=20 > Please report tools.ietf.org bugs at > http://tools.ietf.org/tools/issues > or send email to webmaster@tools.ietf.org > ___________________________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/tools-discuss >=20 > Please report datatracker.ietf.org and mailarchive.ietf.org > bugs at http://tools.ietf.org/tools/ietfdb > or send email to datatracker-project@ietf.org >=20 > Please report tools.ietf.org bugs at > http://tools.ietf.org/tools/issues > or send email to webmaster@tools.ietf.org From nobody Sat Feb 2 09:32:52 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 822971277CC for ; Sat, 2 Feb 2019 09:32:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 bjDZddPWF7Jt for ; Sat, 2 Feb 2019 09:32:46 -0800 (PST) Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E4A5126C7E for ; Sat, 2 Feb 2019 09:32:46 -0800 (PST) Received: from dooku.sandelman.ca (CPE788a207f397a-CMbc4dfb96bb50.cpe.net.cable.rogers.com [99.249.53.27]) by relay.sandelman.ca (Postfix) with ESMTPS id 458D81F42E; Sat, 2 Feb 2019 17:32:45 +0000 (UTC) Received: by dooku.sandelman.ca (Postfix, from userid 179) id 1735F1101; Sat, 2 Feb 2019 12:32:22 -0500 (EST) From: Michael Richardson To: Carsten Bormann cc: Richard Barnes , tools-discuss In-reply-to: <098AAA72-450A-4376-983F-57F0C667C212@tzi.org> References: <098AAA72-450A-4376-983F-57F0C667C212@tzi.org> Comments: In-reply-to Carsten Bormann message dated "Sat, 02 Feb 2019 14:37:56 +0100." X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Date: Sat, 02 Feb 2019 12:32:22 -0500 Message-ID: <30833.1549128742@dooku.sandelman.ca> Archived-At: Subject: Re: [Tools-discuss] Why does xml2rfc download over HTTP? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2019 17:32:50 -0000 Carsten Bormann wrote: > Right. However, who ever fixes this should keep in mind that software > installed on a laptop does not always have access to a good set of ro= ot > certificates (the browser is likely to, but Python software may not > have access to the browser set), so it would be useful to have an > escape hatch of some kind (preferably through environment variables, = so > complex Makefiles don=E2=80=99t have to be touched). +1 > Maybe adding a little bit of robustness to the download process (e.g., > don=E2=80=99t cache it if it isn=E2=80=99t valid XML) would also help. That would have also solved the problem, which I've also experienced. --=20 ] Never tell me the odds! | ipv6 mesh network= s [=20 ] Michael Richardson, Sandelman Software Works | network architect= [=20 ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails = [=20 =09 From nobody Mon Feb 4 10:12:10 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B50D130ED7 for ; Mon, 4 Feb 2019 10:12:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.001 X-Spam-Level: X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mit.edu Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xa1mQuE-RZJC for ; Mon, 4 Feb 2019 10:12:06 -0800 (PST) Received: from NAM05-CO1-obe.outbound.protection.outlook.com (mail-eopbgr720131.outbound.protection.outlook.com [40.107.72.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0590D12008F for ; Mon, 4 Feb 2019 10:12:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=z+w2WwqYF46AhCiZT0ftZoKgWzo3w0Dwd3y/94tg6qw=; b=UqXjf0LP0LUmEsb4iTJFmCMZzquZ7ps3IUwOyQpyudtPv3Mdvy3nHzKSKm7U1rAgSbnCXCuPeuzP7CO/JMwqEQEz0mlWW9IbuKLobXFkPYw3G8CBt3MIFrqWGwozjtz/M09EL18mwubOXQh/PCcHbj9uS2iGhSGM/YGwSn87+24= Received: from SN6PR0102CA0008.prod.exchangelabs.com (2603:10b6:805:1::21) by DM6PR01MB4490.prod.exchangelabs.com (2603:10b6:5:78::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1580.22; Mon, 4 Feb 2019 18:12:04 +0000 Received: from CO1NAM03FT030.eop-NAM03.prod.protection.outlook.com (2a01:111:f400:7e48::205) by SN6PR0102CA0008.outlook.office365.com (2603:10b6:805:1::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1580.20 via Frontend Transport; Mon, 4 Feb 2019 18:12:04 +0000 Authentication-Results: spf=pass (sender IP is 18.9.28.11) smtp.mailfrom=mit.edu; ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=bestguesspass action=none header.from=mit.edu; Received-SPF: Pass (protection.outlook.com: domain of mit.edu designates 18.9.28.11 as permitted sender) receiver=protection.outlook.com; client-ip=18.9.28.11; helo=outgoing.mit.edu; Received: from outgoing.mit.edu (18.9.28.11) by CO1NAM03FT030.mail.protection.outlook.com (10.152.80.169) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1580.10 via Frontend Transport; Mon, 4 Feb 2019 18:12:03 +0000 Received: from kduck.mit.edu (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x14IC0pE019905 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 4 Feb 2019 13:12:02 -0500 Date: Mon, 4 Feb 2019 12:12:00 -0600 From: Benjamin Kaduk To: Message-ID: <20190204181159.GN92608@kduck.mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) X-EOPAttributedMessage: 0 X-Forefront-Antispam-Report: CIP:18.9.28.11; IPV:CAL; SCL:-1; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(376002)(346002)(396003)(39860400002)(136003)(2980300002)(53754006)(199004)(189003)(55016002)(97756001)(26005)(246002)(186003)(426003)(336012)(50466002)(33656002)(6306002)(8936002)(956004)(486006)(476003)(126002)(46406003)(75432002)(53416004)(8676002)(16586007)(2351001)(23726003)(106466001)(47776003)(26826003)(478600001)(966005)(6916009)(786003)(36906005)(316002)(104016004)(7696005)(106002)(2906002)(86362001)(356004)(1076003)(88552002)(4744005)(305945005)(58126008)(18370500001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR01MB4490; H:outgoing.mit.edu; FPR:; SPF:Pass; LANG:en; PTR:outgoing-auth-1.mit.edu; A:1; MX:1; X-Microsoft-Exchange-Diagnostics: 1; CO1NAM03FT030; 1:/HI9yfc6vO8IL2Q+lXW6as4eT+vYo1k8UGiSON3epMTFWp0/fjQ+RdeJEGyWAxHj7xFKh7yBww6oTn+mK72UEPJgpPgVlo7s9pSXUVlBGXVcBBSfZIz74CuwYhYFhrDDJEbOcgJ43j/RxbV3tVDNyL6CymJVwp4fOskrUt4zF/Q= X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: 6989feb2-fb90-4cdd-25b8-08d68acc43fd X-Microsoft-Antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600110)(711020)(4605077)(4608076)(4709027)(2017052603328)(7153060); SRVR:DM6PR01MB4490; X-Microsoft-Exchange-Diagnostics: 1; DM6PR01MB4490; 3:xQ5iRKiy8GMsrDIsn9Wh9YrkspevKvHme2S29tEGTlpC/ZAXLWLi2kMnMmSORoIYQOdsR+mYVkPiThDfRFxlx5Y8L/8aI2d7NcjQr1Dx/kkI53FtIMd7DX4rnaEHMi4G3ABf8Gvl9M4Je18sltTWOHlgKMcyRgPsT1u5YYfZIDD0X+ckzyoGe7KeWQ5cI51bZ/0/oxj/bHnx+aqx1WG7Gvy58xNABw5qOgwweWJNp57dXQthlgkLU1FWAGhI45Na+4q1ekxEXQbOeEr+dLVUlaACQq+QNlPEZptJm023EPrjHIJEJlxGYGBmbxtGH98h4cize34FW+3DSSKlQKavIstMRuPVwTjvgThikqB+aSZCknJWWIfKsF64pdaF1bSK; 25:PIAuOG+IKf9mUcFOkNOovtxn3NvqaxNtyRxNHu7jixm+cddWPc/Lfo+19QfQu8GrzVzZzzf2FjN3dyaO/FTL4Nw4ScKHilXegJDO3hlBbNDzICmeeVG+xz23Tcrf7A9h4YeGg8rwZzZJNj2y81gxXaG3LOpsrfItBnUzn760X22OTlajgryntwLCO2jKH074xPCOvwij4O15sAc/U4+spCFe3kpbSjNN8uA2NQLqKLua8dQBAKp/uolRED6G8RaH1j0Noto3SiMdGjcMZdvXPTHRPhg3hMgCth9bvTGHQdrc0AVB0GvB4TDaAUj1M9FJE6t7PNDkwM5egB4oqkIBmg== X-MS-TrafficTypeDiagnostic: DM6PR01MB4490: X-Microsoft-Exchange-Diagnostics: 1; DM6PR01MB4490; 31:L93it1yWnELWVKJ5A0Lexg2vzzWFhWRHLH+LpFYanvUBrcAEuP2AbWTf4YySbXLV8ws5yeY1cdQtjiCf+EM4HMvGdDgps0hRJmqcVMxzpsgV4jO9Y3xF0b6sVflDjOX3aKFTWLDWF8UCr8KpTdYe/BqYdVhrf5SDf6HSgnqynKfuAqa29Y6/1XI3c6tfU625bID+QugHvlTP8B8HKIndF+WDcZpl1gepo2sxT73B3wQ=; 20:k5idf5ysQBM1cJdYrGCsxayxvkgT+2Q3Jrzr46yolyqNy14rn+TxsEewvxwKvfDAdjMgsschhpkDrbhVLVa/kvOhvFeasIlPxLvIJlyBHp4hbdrwFBhr0VR2++aRsaiW5aw00dZStnGqfvORlCtRgYRXnfltc62qEpGkBQ3Cxzz7vRWq+G8ONtdX3oUucnq5jcbL0fJ7RK148G6DgOqt+enyTW8aZYHDdeI1OOa3p6RW91EJZNj2d2dtYe6F1ievg/IootnXgo0qqMwiAMvcZEGXllWtG2VrpZL4y4AHtKGNaJ6F0eP6oPsxNIPsB2g8nWW7WR0SKZO5ajMM2cYL0/YlCvO6o4Mixw0ZFXFc2p36Wvhn7eACE7xicUolOPUDa4ORRkI47WqaITWAh1OuIG0WO67NIG6h0Ct1RGAOaAUGIPmsvrZahRNFJUxIJKGX9W/fn8X5uyddxDzXzo/aQd/BeASUhti55D+zf+PfHtACoAmq4P6RWXJDPD2nPJYDD8jKO3w+QfchAkc7TvxXdJAPWLbN+p8Z30XUHiiLsH/5AVYGAwncKBw2VQzpZVbcdJzzrlCnC66Gy/+I9FSSv6wxzlnL3+Rhj5yfaylG4VA= X-Microsoft-Antispam-PRVS: X-Microsoft-Exchange-Diagnostics: 1; DM6PR01MB4490; 4:nq78gq58pqfjNdXVnf2BAHkYIgUd4iQb/I6b2zAXK2a8RBYcdW75IUF2gexU+/t2dnbawsXVWdbjsmhii6QnGbmDo4VLsc4S9kH7FTp5pc9wSLwXpctHDxnOpEiBbQ5TtZRlsk7oNinE/ZsBYB3YMIFey0Ug2qHDPqa1Hu6l76DypnEOCXy/LUmpMx5xxN4UTm7jB3b0jhDit9lI9K/xjGtwoDcH5g5U638wAMSgMAAy1Dpl8rVy8ca+P3AAA3jlA1HJVyip1klSd4vQbe1wW8oDuCavvDngnNf0iZtBasMDD2MnbmET2rXUVp5VcZk4 X-Forefront-PRVS: 0938781D02 X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; DM6PR01MB4490; 23:uuN5Zv03dE/exdd9dJ4asCFU1BPFzNR7Tw15XDWpX?= =?us-ascii?Q?Y0FtMByVU1mV+ZGEmvWI3W4VJvbZiSJsOx+p9XLuf4KUGQBIfuEPGvxdJ6K8?= =?us-ascii?Q?lmQVcnDtOpb+8lTixYLHmJ+PPch/HmqYd440SZ+2vR6iRlz4mqkwU2oxJDxe?= =?us-ascii?Q?Z2e3IZd/MLiQw3yAHlVsTZQeW3h5fuo63K7fXR684KpjyYBd8QE2d9+iVFRU?= =?us-ascii?Q?mUmXQBlm2l9r7ikXhtjOUydm43md9kARXRiL1QvGFYVC0Pgr/NNTBLpXYyL6?= =?us-ascii?Q?XP4Qm69cN8zqC0//sTwdNN83k/CrFRLvfX29tgkuqSHq93K+QL1hZvIR/C8S?= =?us-ascii?Q?uQe5Hti6yXBnAWT21L95ITBB61asLQXyKhDH2aChsLjeNmtiPUHHalGTCgc6?= =?us-ascii?Q?81rhrvjDpkc0WDmExNsUsHRsMwAzMfGFEynr8TWiglu35UVq/OyO7Y63LE1Z?= =?us-ascii?Q?RegQl8ainWEJtr0XvzYIqNYudmID1UWVgjG4TlxWCtTVdxcLuE0UJbOF7Y12?= =?us-ascii?Q?CHINHd4COygFPEhGfovS9Fa5zdyKbiOvA+8GQ79jKpiSQIwPJsCU71pJKbnz?= =?us-ascii?Q?r/eXR5Y8RHh7yp73z3ejgn4may4aInomUeE9fWMeKnlAtztry6bwEATDhLCt?= =?us-ascii?Q?OLaOdOKa4Fz5fLwI+RbZQh+QnshQfimmknQOLJO1jDLb+xx9t9jtI4UhnK50?= =?us-ascii?Q?JrP5479d4kXGgSYiQZNs9DjkQ7qHv9fxfbH5o2glQyUMVp6KmqwqKV3nsx4A?= =?us-ascii?Q?YNEy7SNBrlTI3YkYNhGu3uEMKm5tvZPLlqJSbw0CRXmboiuFeCvLo4w1R96s?= =?us-ascii?Q?bGbBg0zEhFVupWSW8yWU9SHUmD307rdX21HZuvIziODLqfmxSjRycymDllD0?= =?us-ascii?Q?u625KpV5Y8IYCyG47P3vYX9re9NJ6cFSUDhE7KVKDA1z9i0fryYIJV3t80pZ?= =?us-ascii?Q?Mmx2bVHsN2aOk3khicoVY6u80vZjKllI9deyFo3cBN1Z5FJqiTjrL1iyywIB?= =?us-ascii?Q?Fi7HSCIFFys47T6kfoD8B5MSWLqcUpgXp40fH3bLFD3JPrTi1FqzE7UOZEOW?= =?us-ascii?Q?I2sPG2Fbs/IAzI1waHV0KpqctQU3xRAL3nXPO1bmG+gg3sGL3Lb366BKd3jZ?= =?us-ascii?Q?LAiQDka3jUb2AURVQ7X4xmdtBWs7CFq?= X-MS-Exchange-SenderADCheck: 1 X-Microsoft-Antispam-Message-Info: a9xxq3iZ6jzSOBdsZplnz5uLTNMz30D6aOdVBjl1yBM2OjSERYNkkWSMYKrA4il3vHMV6HxCGHtbtLDwXnkrzTz/hfFHREcfJTjJN+r4xx5b+3OyF5RvizoxqzjWu8gWBDq1l4BbJrge949XV1JS1gfKLcGAqIvIWHSmWdRJAwJQEVDgGymw8BSQQwtvCVnMJ2XOhU61w92sIGmasCgYXwZ4rWeN48qeEfi8hhTcO+ggY8hlAWRZU8CJixPj6lhMaVHad1edF1MoxzGQwIRTCu/qd5l6YX8gZ20CJSDQ77LxHjot5Bfdfw7NbK1RXIQf8ctonox2tliOcVmoz3/93FEmd7czdp3ijA1/XN+4XlI1h0A/+KWl7n5WDXDQG6V1Fl5GHTqB1YwpiqJLi3XKUoP2NgiSMWm+syBIysbr3v8= X-Microsoft-Exchange-Diagnostics: 1; DM6PR01MB4490; 6:R0Kl741CLrDFzKDieCksPwUnz7WMb92LMg6A4FzaTzaesLJVudAG8rscukhBBEi/xBNohOdX+uC5HBYxj/+1cR+ftgCSgp9q2aCqsFct6NfnDWlcPQZ7PezIuRSUTNoH9bOypXl+HMx84Y3E0CNa1dy41xC55ZA3uA4XWAbqmWfh0i9HwvJDdiu52HzTt8NEw7cTqYgFnAs/Q3ojmvJOttbFaS91pQLAlRNQYR6uhEkZH0+j+TZh6M7vqzR1Krd3KdScPhwke3/T9AsvzDdgC9Nt9PT91wkCHaR58qGYmBYEa/Q9DsTKKQVnEO8TB8WIlV2f+p36EKTDnTgAQ0QXlLhTL6Nxqjb/shszLIiy+qbG0tcrmtYC3Nq+BJaRUScnHkbbCoA+NvyXdTjL9CvzzWHx6QwuC8IixmFfOhx3aFk+dqKuCog97CzfhCyCcH+ZUUy8vlBuM4tN2VkvKm2mdA==; 5:v3yOLFlREkwe8Ukmto4mb8zpTMOvw7Qu1r4/kVWzXoXedlTyv+J7I6ZvCMq7ErbOXonrpDs/PCsXzTbrlOth7m6UlUVMi0CIc1vwprhjdscVEGOv2bSk9TcjffUgG7+Ua3GT3cLgL1oOTEHPBa/YgOHe6i+5ERrHavZ3nESfNmZse0W8F2QVXlp1GOLoFeRb6Gx7x2kcEsb1xXc2w3y/mg==; 7:7hyOzUVFMfdaE1yxvRaTUkywsmlmMsUExvC+B+5q3wda1oY098+El7LjEbXAwTl6v6Ai7X52MbhqenRqlHjI7+W/FTxU2KrofcQ8+zclMOpFFLkQfwwxfYMFdMea7h01h8geZhkkCV3PfNj2jdmPPg== X-OriginatorOrg: mit.edu X-MS-Exchange-CrossTenant-OriginalArrivalTime: 04 Feb 2019 18:12:03.4895 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 6989feb2-fb90-4cdd-25b8-08d68acc43fd X-MS-Exchange-CrossTenant-Id: 64afd9ba-0ecf-4acf-bc36-935f6235ba8b X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=64afd9ba-0ecf-4acf-bc36-935f6235ba8b; Ip=[18.9.28.11]; Helo=[outgoing.mit.edu] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR01MB4490 Archived-At: Subject: [Tools-discuss] BCP 201 disagreement between tools page and RFC Editor X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2019 18:12:09 -0000 Hi all, https://tools.ietf.org/html/bcp201 loads up an interesting page for me, that includes the contents of RFC 7703; the RFC Editor claims that BCP 201 should be RFC 7696 (and the tools version of RFC 7696 also claims to be BCP 201). Am I just confused about how this is supposed to work? Thanks, Ben From nobody Mon Feb 4 10:37:21 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73C60130EE7 for ; Mon, 4 Feb 2019 10:37:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 3d7aDpCp7SZf for ; Mon, 4 Feb 2019 10:37:16 -0800 (PST) Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EE29130EE6 for ; Mon, 4 Feb 2019 10:37:16 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 03CB61C5748; Mon, 4 Feb 2019 10:36:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PkUJU77k5sH3; Mon, 4 Feb 2019 10:36:44 -0800 (PST) Received: from sandygiozasmbp2.frontierlocal.net (unknown [47.156.81.60]) by c8a.amsl.com (Postfix) with ESMTPSA id CF4F21C5725; Mon, 4 Feb 2019 10:36:44 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) From: Sandy Ginoza In-Reply-To: <20190204181159.GN92608@kduck.mit.edu> Date: Mon, 4 Feb 2019 10:33:31 -0800 Cc: tools-discuss@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20190204181159.GN92608@kduck.mit.edu> To: Benjamin Kaduk X-Mailer: Apple Mail (2.3273) Archived-At: Subject: Re: [Tools-discuss] BCP 201 disagreement between tools page and RFC Editor X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2019 18:37:20 -0000 Hi Benjamin, Thanks for bringing this to our attention. I believe this was due to a = bad link on the RFC Editor site. I corrected it, so I expect = https://tools.ietf.org/html/bcp201 will be updated shortly as well. =20 Thanks, Sandy > On Feb 4, 2019, at 10:12 AM, Benjamin Kaduk wrote: >=20 > Hi all, >=20 > https://tools.ietf.org/html/bcp201 loads up an interesting page for = me, > that includes the contents of RFC 7703; the RFC Editor claims that BCP = 201 > should be RFC 7696 (and the tools version of RFC 7696 also claims to = be BCP > 201). Am I just confused about how this is supposed to work? >=20 > Thanks, >=20 > Ben >=20 > ___________________________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/tools-discuss >=20 > Please report datatracker.ietf.org and mailarchive.ietf.org > bugs at http://tools.ietf.org/tools/ietfdb > or send email to datatracker-project@ietf.org >=20 > Please report tools.ietf.org bugs at > http://tools.ietf.org/tools/issues > or send email to webmaster@tools.ietf.org >=20 From nobody Tue Feb 5 11:18:08 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 467AD130ED8 for ; Tue, 5 Feb 2019 11:18:07 -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, 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 s6EzMXRMZxqv for ; Tue, 5 Feb 2019 11:18:05 -0800 (PST) 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 02FD6130ECD for ; Tue, 5 Feb 2019 11:18:05 -0800 (PST) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:56426 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 1gr6EN-0008FZ-Sj; Tue, 05 Feb 2019 11:18:04 -0800 To: Carsten Bormann , Richard Barnes References: <098AAA72-450A-4376-983F-57F0C667C212@tzi.org> Cc: tools-discuss From: Henrik Levkowetz Message-ID: <0ee1c021-b920-b7b9-b126-db5ea27ec3c6@levkowetz.com> Date: Tue, 5 Feb 2019 20:17:56 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <098AAA72-450A-4376-983F-57F0C667C212@tzi.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="PI1fubXIEO7Si3OHsmETaO0WJ4jNHUe2v" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, richard.barnes@gmail.com, 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: [Tools-discuss] Why does xml2rfc download over HTTP? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2019 19:18:07 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --PI1fubXIEO7Si3OHsmETaO0WJ4jNHUe2v Content-Type: multipart/mixed; boundary="JVma15BfjcxHX8UiEHFkovMNT7XIjhHjb"; protected-headers="v1" From: Henrik Levkowetz To: Carsten Bormann , Richard Barnes Cc: tools-discuss Message-ID: <0ee1c021-b920-b7b9-b126-db5ea27ec3c6@levkowetz.com> Subject: Re: [Tools-discuss] Why does xml2rfc download over HTTP? References: <098AAA72-450A-4376-983F-57F0C667C212@tzi.org> In-Reply-To: <098AAA72-450A-4376-983F-57F0C667C212@tzi.org> --JVma15BfjcxHX8UiEHFkovMNT7XIjhHjb Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, On 2019-02-02 14:37, Carsten Bormann wrote: > Right. However, who ever fixes this should keep in mind that software > installed on a laptop does not always have access to a good set of > root certificates (the browser is likely to, but Python software may > not have access to the browser set), so it would be useful to have an > escape hatch of some kind (preferably through environment variables, > so complex Makefiles don=E2=80=99t have to be touched). >=20 > Maybe adding a little bit of robustness to the download process > (e.g., don=E2=80=99t cache it if it isn=E2=80=99t valid XML) would also= help. Yes, that makes sense. Added in my sources, will be part of the next release. Thanks, and best regards, Henrik >=20 > Gr=C3=BC=C3=9Fe, Carsten >=20 >=20 >> On Feb 1, 2019, at 23:40, Richard Barnes wr= ote: >>=20 >> In particular, this seems to be the patch necessary to resolve the iss= ue: >>=20 >> Index: trunk/cli/xml2rfc/parser.py >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> --- trunk/cli/xml2rfc/parser.py (revision 2965) >> +++ trunk/cli/xml2rfc/parser.py (working copy) >> @@ -53,8 +53,6 @@ >> no_network=3DNone, network_locs=3D [ >> 'https://xml2rfc.ietf.org/public/rfc/', >> 'https://xml2rfc.tools.ietf.org/public/rfc/', >> - 'http://xml2rfc.ietf.org/public/rfc/', >> - 'http://xml2rfc.tools.ietf.org/public/rfc/', >> ], >> rfc_number=3DNone, options=3Dbase.default_options): >> self.quiet =3D quiet if quiet !=3D None else options.quiet >>=20 >> On Fri, Feb 1, 2019 at 5:08 PM Eric Rescorla wrote: >> Hi folks, >>=20 >> I recently went to build a draft and got a pile of errors about how th= e references didn't parse. Digging into things a bit, I discovered that t= he reference was the page from a captive portal on one of my flights. I'm= not sure how this happened, but looking at xml2rfc, it appears that it t= ries HTTPS URIs and then HTTP URIs, which seems like it's going to have t= he wrong outcome in the situation where the captive portal blocks HTTPS a= nd intercepts HTTP. >>=20 >> Is there a good reason to continue to allow HTTP URIs in the tool? >>=20 >> -Ekr >>=20 >>=20 >>=20 >>=20 >> ___________________________________________________________ >> Tools-discuss mailing list >> Tools-discuss@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-discuss >>=20 >> Please report datatracker.ietf.org and mailarchive.ietf.org >> bugs at http://tools.ietf.org/tools/ietfdb >> or send email to datatracker-project@ietf.org >>=20 >> Please report tools.ietf.org bugs at >> http://tools.ietf.org/tools/issues >> or send email to webmaster@tools.ietf.org >> ___________________________________________________________ >> Tools-discuss mailing list >> Tools-discuss@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-discuss >>=20 >> Please report datatracker.ietf.org and mailarchive.ietf.org >> bugs at http://tools.ietf.org/tools/ietfdb >> or send email to datatracker-project@ietf.org >>=20 >> Please report tools.ietf.org bugs at >> http://tools.ietf.org/tools/issues >> or send email to webmaster@tools.ietf.org >=20 > ___________________________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/tools-discuss >=20 > Please report datatracker.ietf.org and mailarchive.ietf.org > bugs at http://tools.ietf.org/tools/ietfdb > or send email to datatracker-project@ietf.org >=20 > Please report tools.ietf.org bugs at > http://tools.ietf.org/tools/issues > or send email to webmaster@tools.ietf.org >=20 --JVma15BfjcxHX8UiEHFkovMNT7XIjhHjb-- --PI1fubXIEO7Si3OHsmETaO0WJ4jNHUe2v Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAlxZ4WQACgkQTptXS4+7 FxoWqw//d9lPIcJqxb302ZkFzsAW7UN4zDtiRzkc2IOqrNK+CMEcCZ7iEQj/EqGB KWOHUR/ytzM9k67undhzEmW5uMnOu2lOgStuBMKp24c0Z9XFZqS4meoFRH2od2Bu crN5uTT0q4CzfDVw/sauQ0p/98XqpMMtOEw3JVpPEWOatddRrLBcrD2wWioI0T0X 4VsN221R2q0nXlOCpIJA2mIy9Wau0KAHMl3hjYiZRDgZbVFizTKm9WLf1Zs1LP9y KD5ck6c4Tz7gs42nVuEMPDzjoSiTOBjxDbpn31VEU0ucUHoTd82ohgwnBmsmyvXe bbRX2XPmn1mfbygM4rf2PpvpLYk64/fwTYboYbPh3oKvFL0GvNGU/pRIMXF1ZtvB bQZrJ+RLMc+8GqaXBkouhbrAn2e4xXrQBxPAwgSgpMelCak5WlGNbNv2rStYY5lh 8wzWlyPL+cfpiUcNbW2CNDMAjBDFhQQyBU01gBquV6hVvEWisjoMoN0LBLTVA0Gy UaIicDPDTVZhuMV0m6CeQSzbSB/DDhVGeh5UiacwiB6ZCczKvYto0bWDvVgj5+nx TkkMtje53oRSwm7pvRyYxo6jfM08vnr/Wr6sKvP7S3rJD8MNhm8geNRsSXnFIkgI LvGYAdmvUBSWxePouwBZBoq/gXZ3Nd1s6I0xRgZGickPeOoPBOQ= =q2QA -----END PGP SIGNATURE----- --PI1fubXIEO7Si3OHsmETaO0WJ4jNHUe2v-- From nobody Tue Feb 12 15:53:23 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2CF8130E11 for ; Tue, 12 Feb 2019 15:53:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca 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 5wyp5IlBvLpz for ; Tue, 12 Feb 2019 15:53:12 -0800 (PST) Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (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 BE2A1130E78 for ; Tue, 12 Feb 2019 15:53:12 -0800 (PST) Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 43zfc60F99zK7p for ; Wed, 13 Feb 2019 00:53:10 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1550015590; bh=EckrRd+5a7BQaepuSKdrxk9ioeIsrIxRdn4cviWR/PU=; h=Date:From:To:Subject; b=ltl5hyoG+FIo71Hrv1EDIN4iVsypmGDYJJsuzx4RXYnXQzj70Dv+LQnzrRajOZnt3 wzWqkIEgesnmopY+8IXTtV0yqbRAqo3muFXNo4WaWLpM6XJ8DK1MEGXRNCJDtXhF8G E5m/Oug0q++Az+A0Ceb5DmcFyOqnCwbD9MTCpPGg= X-Virus-Scanned: amavisd-new at mx.nohats.ca Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id lMngIuVAnQ-y for ; Wed, 13 Feb 2019 00:53:08 +0100 (CET) Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS for ; Wed, 13 Feb 2019 00:53:08 +0100 (CET) Received: by bofh.nohats.ca (Postfix, from userid 1000) id B9C1DA7E0C; Tue, 12 Feb 2019 18:53:07 -0500 (EST) DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca B9C1DA7E0C Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id AF78B40D358A for ; Tue, 12 Feb 2019 18:53:07 -0500 (EST) Date: Tue, 12 Feb 2019 18:53:07 -0500 (EST) From: Paul Wouters To: tools-discuss@ietf.org Message-ID: User-Agent: Alpine 2.21 (LRH 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII Archived-At: Subject: [Tools-discuss] xml2rfc license file and git repository ? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2019 23:53:21 -0000 Hi, While upgrading xml2rfc, I found that the LICENSE file has vanished. Can this be re-added in the next version. This allows packages, such as those on fedora/rhel/centos at least, to ship the license file using the %license macro. I could find no such file and had to look into PKG-INFO to find some odd flavour of BSD license mentioned. Also, where is the git repo? I wanted to see the history of this file but I cannot find the source code repository. Thanks, Paul From nobody Tue Feb 12 16:37:40 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50ED1130E8B for ; Tue, 12 Feb 2019 16:37: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, 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 pR2FemAMciDH for ; Tue, 12 Feb 2019 16:37:37 -0800 (PST) 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 950AD130E83 for ; Tue, 12 Feb 2019 16:37:37 -0800 (PST) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:61282 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 1gtiYS-0002oP-HF; Tue, 12 Feb 2019 16:37:36 -0800 To: Paul Wouters , tools-discuss@ietf.org References: From: Henrik Levkowetz Message-ID: <6af526a4-1b57-d93c-590d-74828b41546a@levkowetz.com> Date: Wed, 13 Feb 2019 01:37:28 +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: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="1xf9bjm9xRSuolcsdNJfbQBnn6SPFhBRv" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, paul@nohats.ca 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: [Tools-discuss] xml2rfc license file and git repository ? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2019 00:37:39 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --1xf9bjm9xRSuolcsdNJfbQBnn6SPFhBRv Content-Type: multipart/mixed; boundary="3e20kWFtAiWLebJ0gxwjhT1LAcR58A8KF"; protected-headers="v1" From: Henrik Levkowetz To: Paul Wouters , tools-discuss@ietf.org Message-ID: <6af526a4-1b57-d93c-590d-74828b41546a@levkowetz.com> Subject: Re: [Tools-discuss] xml2rfc license file and git repository ? References: In-Reply-To: --3e20kWFtAiWLebJ0gxwjhT1LAcR58A8KF Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Paul, On 2019-02-13 00:53, Paul Wouters wrote: >=20 > Hi, >=20 > While upgrading xml2rfc, I found that the LICENSE file has vanished. Ca= n > this be re-added in the next version. This allows packages, such as > those on fedora/rhel/centos at least, to ship the license file using > the %license macro. Huh. Indeed, it has, but not intentionally. I'll put it back. > I could find no such file and had to look into PKG-INFO to find some od= d > flavour of BSD license mentioned. >=20 > Also, where is the git repo? I wanted to see the history of this file > but I cannot find the source code repository. https://svn.tools.ietf.org/svn/tools/xml2rfc/trunk/cli/ Regards, Henrik --3e20kWFtAiWLebJ0gxwjhT1LAcR58A8KF-- --1xf9bjm9xRSuolcsdNJfbQBnn6SPFhBRv Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAlxjZskACgkQTptXS4+7 Fxpdjw/+PEDVuvAhJqW7oEpMPdFkXC5cAgckDdCMQ2tijq/lMZM0P5A0bnM/X9Zi 0vVDF0f3L2LhqiJWuhpqZGk58LpIjnZm9trWV1zF+w4zawAYKWKV8K9KiqRZbArN 40jibBdKFQYUSx/XVktm4ELxOVBNcMD2olZZ43Xg+2ijIgUAtGmzfSwBJVh4XVFu 4VogMkpOnjZva6xOdYDEsJzY/c7YydGEOaFnMXf+ZL1/yoJF4etAFc+GiXbN3VMO F7DKp2EOUaZoyf6oHGUsEOpcwG5g+Asimxfs5AOifek+EiE8cmglIG7tFkOahSkW YN9DblqAicPADmT6+biF5cybCtw+klRLITZGEjLhUDE7MWPAavCCAze658YMDVfM 3HpstH1DLqsQALPiT8DGse9bIGntZtjUgPcnui75k82f3He1+K8M6pF+yrcBndRn 7DS+bjSQWkEyo+ZLzM9CK00yi0Nf34Y5XNyI3utPfKi2XytYLGzrCdLoSDJpVmnu 1k4ySISs3MOqXbQKjdZsAo1OPtapT/2oxnZ/vj7sC/8q1n7p3zNsPYCoai+hYyLl wcEVYo3xOwogGvK/+A3fU9mcsuluH/UGQxZ8ySfHRRHKBvBrBvgo8JVISHx+07qj HBbe0WO9Jvvg4yRsat/hOHkEeXr05t6gRIQdV4YiHOHchFJSHjo= =nrAB -----END PGP SIGNATURE----- --1xf9bjm9xRSuolcsdNJfbQBnn6SPFhBRv-- From nobody Tue Feb 12 17:42:39 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17478130EDA for ; Tue, 12 Feb 2019 17:42:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca 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 UMlz9sX0fm-E for ; Tue, 12 Feb 2019 17:42:36 -0800 (PST) Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 98D33130DE4 for ; Tue, 12 Feb 2019 17:42:36 -0800 (PST) Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 43zj2K28H0zK7b; Wed, 13 Feb 2019 02:42:33 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1550022153; bh=zFPqBs8QRQ0iBZERvfaDVfmJBhftqM/Yq4Ktyx7gxdU=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=PN1AJB5v0qevbeDNHWG3x4hc83UWKDhQjueuvowhM4zspQCX+j1tKBJOYQhVGNKo3 BKZc7/SVZNHBBT+RzVjN7T/V3xZ6wAEGgqdP9o3qCb+KR/KAkZjExDwYJ4E8Th4XQH 09KRY6V0IbvRkjvVnJ3ziqo/BKDE4zlbIzAiiyN8= X-Virus-Scanned: amavisd-new at mx.nohats.ca Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id YfnW7PCKDCEU; Wed, 13 Feb 2019 02:42:31 +0100 (CET) Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Wed, 13 Feb 2019 02:42:30 +0100 (CET) Received: by bofh.nohats.ca (Postfix, from userid 1000) id D775AA7E0C; Tue, 12 Feb 2019 20:42:29 -0500 (EST) DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca D775AA7E0C Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id CCA6040D358A; Tue, 12 Feb 2019 20:42:29 -0500 (EST) Date: Tue, 12 Feb 2019 20:42:29 -0500 (EST) From: Paul Wouters To: Henrik Levkowetz cc: tools-discuss@ietf.org In-Reply-To: <6af526a4-1b57-d93c-590d-74828b41546a@levkowetz.com> Message-ID: References: <6af526a4-1b57-d93c-590d-74828b41546a@levkowetz.com> User-Agent: Alpine 2.21 (LRH 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Archived-At: Subject: Re: [Tools-discuss] xml2rfc license file and git repository ? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2019 01:42:38 -0000 On Wed, 13 Feb 2019, Henrik Levkowetz wrote: > Huh. Indeed, it has, but not intentionally. I'll put it back. Thanks! I've gone through a lot of python upgrading to get the fedora/centos package to be up to date, but I failed to find the python pango bindings it complains about when I run it. Where can these be found? Requirements I needed that were not listed in requirements.txt: weasyprint pango ? And is "six" really needed on a python3 system? Thanks for having the online version. I had to go that since I couldn't generate the rfc txt from xml :/ Thanks, Paul From nobody Wed Feb 13 04:29:55 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C20612DDA3 for ; Wed, 13 Feb 2019 04:29:54 -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] 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 IJj5HNIIdRkV for ; Wed, 13 Feb 2019 04:29:52 -0800 (PST) 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 B2BDA128CB7 for ; Wed, 13 Feb 2019 04:29:52 -0800 (PST) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:49952 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 1gttfi-0001DT-FJ; Wed, 13 Feb 2019 04:29:52 -0800 To: Paul Wouters References: <6af526a4-1b57-d93c-590d-74828b41546a@levkowetz.com> Cc: tools-discuss@ietf.org From: Henrik Levkowetz Message-ID: <695ea802-d3eb-416a-b8f8-da0187c1b672@levkowetz.com> Date: Wed, 13 Feb 2019 13:29:42 +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: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="QnXc53QmEOLnOu6V9souACcU7TGrEJ7Hc" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, paul@nohats.ca 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: [Tools-discuss] xml2rfc license file and git repository ? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2019 12:29:54 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --QnXc53QmEOLnOu6V9souACcU7TGrEJ7Hc Content-Type: multipart/mixed; boundary="PTSq6DlCu8ImiQF5SJFSB3fhWrbuHPKfb"; protected-headers="v1" From: Henrik Levkowetz To: Paul Wouters Cc: tools-discuss@ietf.org Message-ID: <695ea802-d3eb-416a-b8f8-da0187c1b672@levkowetz.com> Subject: Re: [Tools-discuss] xml2rfc license file and git repository ? References: <6af526a4-1b57-d93c-590d-74828b41546a@levkowetz.com> In-Reply-To: --PTSq6DlCu8ImiQF5SJFSB3fhWrbuHPKfb Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2019-02-13 02:42, Paul Wouters wrote: > On Wed, 13 Feb 2019, Henrik Levkowetz wrote: >=20 >> Huh. Indeed, it has, but not intentionally. I'll put it back. >=20 > Thanks! >=20 > I've gone through a lot of python upgrading to get the fedora/centos > package to be up to date, but I failed to find the python pango binding= s > it complains about when I run it. Where can these be found? They should be part of the pango install. Fedora/centos may have some additional build system dependencies for the pango python bindings to appear, though. On Debian/Devuan, I've installed libpango, libcairo, libpangocairo, and things have worked. > Requirements I needed that were not listed in requirements.txt: > weasyprint > pango ? Since weasyprint is dependent on the native libs for pango and cairo, it's not meaningful to force an installation without those. > And is "six" really needed on a python3 system? Six provides both the py27 and py3X sides of compatibility services that makes it feasible (even easy) to write code that works on both py2 and py= 3. When we remove py27 support, we can rewrite without six. > Thanks for having the online version. I had to go that since I couldn't= > generate the rfc txt from xml :/ Hmm. As long as you didn't need to produce v3 pdf, the install without weasyprint, pango, and cairo should have been able to work just fine. Any more details on where you ran into problems? Best, Henrik --PTSq6DlCu8ImiQF5SJFSB3fhWrbuHPKfb-- --QnXc53QmEOLnOu6V9souACcU7TGrEJ7Hc Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAlxkDbcACgkQTptXS4+7 Fxo2gxAAsysZzYI5g/HrO1a0KBXfKg3GvEyfqRSi0C5WjzUmqeODJY1efwTsRWNS k/+eh6w12pOHGwjMf6xfU2w9wG5L77HhVEi7z+zb+4Y1vowKyVhYEwCICl2w4zgw scloHZjm0C8e6GJYIDVqYOwOewYQonQq2SLzpHGmZL4VVVnb+tSkmTDjHaP7ztYK OlnPDRai+e0db/CeuiSNhEMCE2wqDH4Hhs7yPiRdCt2FeQYC4Ow/gUSZhZuYTYGW uoPY/ath8TZ7aUpyPcXz3+a90KtY/3ba66hppQwpTuBLb6BP++vrloSIEv887oxV 5aUyOw1H4O5WgmulZGfn1cG4imch6qGFvyVOqe9IMTAD3z0vxHn7kl6vKT2jeJ+k yi+ZEH+NOr2gwkT8xXyuJkIx8o8uDgUExIBuGYJEBUs2ZCXDryDyCTCwgwDnpcNg gs3u4Qi7qDsPvPEYb0UYM2l5JjJCj9FBb1PDcuvSOi8sfC1Z7a+IEVh0BesOor5S 1QbPCWN01NryKOOdKeP5DQFH9zuFxoRYaL6h7kC7L595PmUj3RdjiG14UKM57Hde uKwiYCI/SV4ffMMjtQeOsYhgJ1RSgn8Q2wkEMY6FaOPJl5vhj+i01eNHxXwFntP9 KCTKfpeQ1ms1cahIna6frun1rljYfPXx5+7Gv50r1mXDKHuTmi4= =rMkV -----END PGP SIGNATURE----- --QnXc53QmEOLnOu6V9souACcU7TGrEJ7Hc-- From nobody Wed Feb 13 12:10:04 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F46F128B01 for ; Wed, 13 Feb 2019 12:10:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca 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 0y_9RUX0WURi for ; Wed, 13 Feb 2019 12:10:00 -0800 (PST) Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 9E50E1200B3 for ; Wed, 13 Feb 2019 12:09:59 -0800 (PST) Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4409c43hsCzK85; Wed, 13 Feb 2019 21:09:56 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1550088596; bh=ggKWJsEWsmeH4kngoQsaXYl1ayBV2pQ9/v4wn8KWrDs=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=Kbhn/KSGasgLdnYmbWbFz4PspZz2QZ6JGNxiXdVTYXl+mLwBF4aGHDImOqxolJmhp 6dMRbqDNHbCGAdabGaPYajqznvHJEeO75q2cD97dzAfwajQpji7fAK0nEZ9t+4HFiP w7XTQR2zRxU+rj43v2wnl7wwRm3Escml1pGCHQHQ= X-Virus-Scanned: amavisd-new at mx.nohats.ca Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id XiE_IP0M4b-B; Wed, 13 Feb 2019 21:09:54 +0100 (CET) Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Wed, 13 Feb 2019 21:09:53 +0100 (CET) Received: by bofh.nohats.ca (Postfix, from userid 1000) id BFA622FCBF; Wed, 13 Feb 2019 15:09:52 -0500 (EST) DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca BFA622FCBF Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id B6B5040D358A; Wed, 13 Feb 2019 15:09:52 -0500 (EST) Date: Wed, 13 Feb 2019 15:09:52 -0500 (EST) From: Paul Wouters To: Henrik Levkowetz cc: tools-discuss@ietf.org In-Reply-To: <695ea802-d3eb-416a-b8f8-da0187c1b672@levkowetz.com> Message-ID: References: <6af526a4-1b57-d93c-590d-74828b41546a@levkowetz.com> <695ea802-d3eb-416a-b8f8-da0187c1b672@levkowetz.com> User-Agent: Alpine 2.21 (LRH 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Archived-At: Subject: Re: [Tools-discuss] xml2rfc license file and git repository ? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2019 20:10:03 -0000 On Wed, 13 Feb 2019, Henrik Levkowetz wrote: >> I've gone through a lot of python upgrading to get the fedora/centos >> package to be up to date, but I failed to find the python pango bindings >> it complains about when I run it. Where can these be found? > > They should be part of the pango install. Fedora/centos may have some > additional build system dependencies for the pango python bindings to > appear, though. On Debian/Devuan, I've installed libpango, libcairo, > libpangocairo, and things have worked. I thought I had installed all relevants parts. I'll check again. > When we remove py27 support, we can rewrite without six. Ok. Looks like I have yet another package to package up then :P > Hmm. As long as you didn't need to produce v3 pdf, the install without > weasyprint, pango, and cairo should have been able to work just fine. > Any more details on where you ran into problems? paul@thinkpad python-xml2rfc]$ xml2rfc draft-ietf-dnsop-algorithm-update-05.xml Traceback (most recent call last): File "/usr/bin/xml2rfc", line 11, in load_entry_point('xml2rfc==2.18.0', 'console_scripts', 'xml2rfc')() File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 476, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2700, in load_entry_point return ep.load() File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2318, in load return self.resolve() File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2324, in resolve module = __import__(self.module_name, fromlist=['__name__'], level=0) File "/usr/lib/python3.6/site-packages/xml2rfc/__init__.py", line 52, in PANGO_VERSION = pango.pango_version File "/usr/lib64/python3.6/site-packages/cffi/api.py", line 882, in __getattr__ make_accessor(name) File "/usr/lib64/python3.6/site-packages/cffi/api.py", line 877, in make_accessor raise AttributeError(name) AttributeError: pango_version From nobody Wed Feb 13 12:55:55 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03CD012E04D for ; Wed, 13 Feb 2019 12:55:54 -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, 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 JuuIH_gV1Rtf for ; Wed, 13 Feb 2019 12:55:52 -0800 (PST) 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 B687E12DF71 for ; Wed, 13 Feb 2019 12:55:52 -0800 (PST) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:55565 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 1gu1ZP-000444-QX; Wed, 13 Feb 2019 12:55:52 -0800 To: Paul Wouters References: <6af526a4-1b57-d93c-590d-74828b41546a@levkowetz.com> <695ea802-d3eb-416a-b8f8-da0187c1b672@levkowetz.com> Cc: tools-discuss@ietf.org From: Henrik Levkowetz Message-ID: <45067a37-7f49-bc77-e3d4-94851dd17a92@levkowetz.com> Date: Wed, 13 Feb 2019 21:55:44 +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: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="V124LaFMbX7kIS5EdxLnVoS1e2tAQsMt6" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, paul@nohats.ca 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: [Tools-discuss] xml2rfc license file and git repository ? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2019 20:55:54 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --V124LaFMbX7kIS5EdxLnVoS1e2tAQsMt6 Content-Type: multipart/mixed; boundary="aGF3ueQxkm7f6sqGfUOSVTX72TM6qx4m3"; protected-headers="v1" From: Henrik Levkowetz To: Paul Wouters Cc: tools-discuss@ietf.org Message-ID: <45067a37-7f49-bc77-e3d4-94851dd17a92@levkowetz.com> Subject: Re: [Tools-discuss] xml2rfc license file and git repository ? References: <6af526a4-1b57-d93c-590d-74828b41546a@levkowetz.com> <695ea802-d3eb-416a-b8f8-da0187c1b672@levkowetz.com> In-Reply-To: --aGF3ueQxkm7f6sqGfUOSVTX72TM6qx4m3 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Paul, On 2019-02-13 21:09, Paul Wouters wrote: >> Hmm. As long as you didn't need to produce v3 pdf, the install withou= t >> weasyprint, pango, and cairo should have been able to work just fine. >> Any more details on where you ran into problems? >=20 <> > File "/usr/lib64/python3.6/site-packages/cffi/api.py", line 877, in > make_accessor > raise AttributeError(name) > AttributeError: pango_version Ah. Ok. I've added that to the import exception catch. Will be part of t= he next release. Thanks! Henrik --aGF3ueQxkm7f6sqGfUOSVTX72TM6qx4m3-- --V124LaFMbX7kIS5EdxLnVoS1e2tAQsMt6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAlxkhFAACgkQTptXS4+7 FxpJ9hAAnK+sfY1Y6krVhaVV0+VLZAugTanJ+HfhfMpi6TYycuu8OxpIOrsIVfrD r/MBrFsEBnvd6jCWCbYBbxMNPXnuzlJHusjjsi1sgcIhLUJIowfzeKoS2qqS+hTH DUqS5JUSsq+J6R4M/UCFol9MsFsMMe+rzo6wtjALsbCU4EX4Amh6jvBIEZ6u9+nR h/hZrjjomHT/YHp+a1BmcAcyHzv4P1EY7BOHOFk3/L+3/OGvy56eqeprzal9SVwl jqLzlqUfziGquufx0XaBJchRMnDPlv7J+iR87G59Rz2h751qpBMJy6Xz7diMjyOK oBvnogQKEEMqRl7Tnvw8ivVaUJ/9gyHwCGy+73OTQGv7/gB2KJlCD3CYIaY07gDs M/xC1rDZOYNlsSTxd/JYsd6MSE/oXUou23NBC4DaNXY8eKpB3J04TB8B6cSo2AY+ acPB0JmzOcMKFgSgtJotSKYMJTe8fU7xO8GgwzqAfNc2yasx0r39AOky7G7TTzMA kGhQK83+u9OtErLiq8BQnewekcU22WPq97q6HAvnJ7D3J6id5EohiF3m//C9znPt zsrQl2KOawPKdMjjpfY/LGt4r6EqGRbkHrQVCmwWbz1452Hs7aEs2Y1OPdYgIyKK FocV47OxE5VozIBARJDDm1+0UyVQVb80nDM/rq9siXT6OAgQeos= =zeqX -----END PGP SIGNATURE----- --V124LaFMbX7kIS5EdxLnVoS1e2tAQsMt6-- From nobody Fri Feb 15 06:28:30 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77603130FC1 for ; Fri, 15 Feb 2019 06:28:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.199 X-Spam-Level: X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 Sghh-txJ65Mg for ; Fri, 15 Feb 2019 06:28:27 -0800 (PST) Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 CED19124D68 for ; Fri, 15 Feb 2019 06:28:26 -0800 (PST) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [134.102.200.7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id x1FESHhX025466 for ; Fri, 15 Feb 2019 15:28:22 +0100 (CET) Received: from sev.informatik.uni-bremen.de (sev.informatik.uni-bremen.de [134.102.218.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 441Fwx58Rgz1Br6; Fri, 15 Feb 2019 15:28:17 +0100 (CET) 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: Fri, 15 Feb 2019 15:28:17 +0100 X-Mao-Original-Outgoing-Id: 571933695.4613219-e6601e5ecd369bef2987f32d971baacf Content-Transfer-Encoding: quoted-printable Message-Id: References: To: tools-discuss X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [Tools-discuss] IEEE in bibxml2 vs. bibxml6 X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Feb 2019 14:28:29 -0000 At some point I=E2=80=99d like to have a rational solution for the = below. Copying the IEEE cobwebs from bibxml2 to bibxml6 would solve the problem = (I.e., allow me to look up IEEE in bibxml6 as opposed to bibxml2 as of = now). As would creating a bibxml.IEEE or some such from both = directories and keeping them in sync. Gr=C3=BC=C3=9Fe, Carsten > On Mar 15, 2017, at 08:36, Carsten Bormann wrote: >=20 > There are IEEE citation files both in bibxml2 and bibxml6. > Is there a way to automatically decide with one to use? > Could the bibxml2 files maybe be copied over to bibxml6 so we can = always use bibxml6 for IEEE? >=20 > (kramdown-rfc currently uses bibxml2 for IEEE; there is currently no = easy way to access bibxml6. I can=E2=80=99t switch that over to = bibxml6, as the bibxml2 references are in use in existing documents, = e.g. for IEEE 754. Why are we even doing this splitting up? 90 % of = the files are in bibxml3 anyway.) >=20 > Gr=C3=BC=C3=9Fe, Carsten >=20 From nobody Tue Feb 19 08:30:55 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4EC5130F20 for ; Tue, 19 Feb 2019 08:30:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.001 X-Spam-Level: X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mit.edu Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AEJkOBHFkrCl for ; Tue, 19 Feb 2019 08:30:51 -0800 (PST) Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-eopbgr750135.outbound.protection.outlook.com [40.107.75.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FC84130F1F for ; Tue, 19 Feb 2019 08:30:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1y1o1MBePyM96pqPjU9lfDxcSY0ZD0bEvo7FssdSehs=; b=yMvWIbROBvda+7M7LP9uO4EsCjRTh90W6u3SVXSres5IffjrJQPXRqi9ltYmUvDYWpbY4q5P7EJIMh5qRytNoLRE68dWf3ZKTUI73Eh8gLw3VIiIP/bvpEnufhgg82qOH7UnJek7/IZA5CxkSWraUxzJ5q5iTEv7KmWfZa9eNsw= Received: from DM5PR0101CA0033.prod.exchangelabs.com (2603:10b6:4:28::46) by CY1PR01MB2091.prod.exchangelabs.com (2a01:111:e400:c610::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1622.18; Tue, 19 Feb 2019 16:30:49 +0000 Received: from DM3NAM03FT050.eop-NAM03.prod.protection.outlook.com (2a01:111:f400:7e49::209) by DM5PR0101CA0033.outlook.office365.com (2603:10b6:4:28::46) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1643.14 via Frontend Transport; Tue, 19 Feb 2019 16:30:49 +0000 Authentication-Results: spf=pass (sender IP is 18.9.28.11) smtp.mailfrom=mit.edu; ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=bestguesspass action=none header.from=mit.edu; Received-SPF: Pass (protection.outlook.com: domain of mit.edu designates 18.9.28.11 as permitted sender) receiver=protection.outlook.com; client-ip=18.9.28.11; helo=outgoing.mit.edu; Received: from outgoing.mit.edu (18.9.28.11) by DM3NAM03FT050.mail.protection.outlook.com (10.152.82.252) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1643.13 via Frontend Transport; Tue, 19 Feb 2019 16:30:48 +0000 Received: from kduck.mit.edu (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x1JGUkm7001421 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 19 Feb 2019 11:30:47 -0500 Date: Tue, 19 Feb 2019 10:30:45 -0600 From: Benjamin Kaduk To: Message-ID: <20190219163045.GU24387@kduck.mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) X-EOPAttributedMessage: 0 X-Forefront-Antispam-Report: CIP:18.9.28.11; IPV:CAL; SCL:-1; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(346002)(396003)(136003)(39860400002)(376002)(2980300002)(189003)(199004)(53754006)(23726003)(33656002)(46406003)(486006)(6916009)(356004)(426003)(956004)(2906002)(106002)(336012)(5660300002)(126002)(47776003)(305945005)(476003)(7696005)(106466001)(88552002)(86362001)(55016002)(558084003)(186003)(246002)(50466002)(26005)(478600001)(2351001)(53416004)(16586007)(58126008)(104016004)(786003)(97756001)(316002)(26826003)(75432002)(36906005)(8936002)(1076003)(8676002)(18370500001); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR01MB2091; H:outgoing.mit.edu; FPR:; SPF:Pass; LANG:en; PTR:outgoing-auth-1.mit.edu; MX:1; A:1; X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: d2e9478e-b4fb-4fdf-24da-08d696879b61 X-Microsoft-Antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600110)(711020)(4605104)(4608103)(4709054)(2017052603328)(7153060); SRVR:CY1PR01MB2091; X-MS-TrafficTypeDiagnostic: CY1PR01MB2091: X-Microsoft-Exchange-Diagnostics: 1; CY1PR01MB2091; 20:gtaaqsZ1hSqKBdtAGSk1OaF/SislASu1ekybqFRkHCIP7MQ6Y/T7cC1gUEXcwBPrx5gkMMXF03cId1aEsgcRTXFwEgoSCZ856MiXhR6ht/5q9WQxkxBVxIt6xgQwibMbaCBxaG6rh5wilsw2rgb+McuUMFP/uIjqQUERlMAU+yJ/AzDDvBK0U3jzV/+Rqn4xDzsg9kJa27dAFVkYakPtgBMBMTwGBfUpMtIOhEwZu0h9kJLhQ1fFY8fWbO+NMnZe56urdHfUWpZSUDRRV0HXPlgTyvI7SJ8gJXdaOyl+9GruRDLBGUqqwlE6HTP35QoPxX9oU5YWluOJtqTzPtNPWHABCo4z4Npcu2EwoJipklylHuO5A1e24Z5Z4e3Hpc6h5KD61W0ua2PQ5yCqnpuJn7PZoCN3KqKEnBZJ//FOe14g1OZKYlOlN44/DYuxszs6jPmBvpr1/t1Z5CAzphFca1/yX4LDwSMygf3UAMufW2+HwgD8BBLhH1KN9H1i/vF7Wt1WHf59zL063XYfb6T7NMwuUgON1L6BdAqduq5V7f53C4u0xeL+EsbOyDhtukArngocL6puAtbU0zg6VS8wyGB5Edhz+82zl2EC4BbJLAk= X-Microsoft-Antispam-PRVS: X-Forefront-PRVS: 09538D3531 X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; CY1PR01MB2091; 23:1CEzvRVCTCrqmQcAPntlzyJk2lBUf+hb51llUpRwN?= =?us-ascii?Q?2LYCf5FCrMsjo2NYyPGG8qQXC99Y9XULsWG5GJc/hRsNvR3QwF5bsAZpepDo?= =?us-ascii?Q?dy+HVgFgmXPrXIPyDd9YdLDH3CfPW40RbLzfxIS+gB7OMOzf1eT2o7ZdJ4eD?= =?us-ascii?Q?jNWp2TDmMFSsTNukXabhKfDL5Q1O0eeXAhg1DeeaWSuLfw+t8zBsxCVKfdD2?= =?us-ascii?Q?wPDLT3gKrgGy+8wFqDBC1/ZSkf9VNxuaEnnWbGOfTxg4NCtQ0H+083aGeaOQ?= =?us-ascii?Q?5zuBEgcqNWs4FCpgAWd1ryMVUeTYWLYyObp6IpwK+2PqQzyw54iDVge4mGDN?= =?us-ascii?Q?0xO0f11BdvRBBKqRWOQpil2wlRzE7r6GEQ4ZJl2ipw3J0D9MtgbCWbQhSdJI?= =?us-ascii?Q?Bm3V/WapGfL1UxRUnemK+KzEFc2NX+yzJ2+00LDEJUYDn1845MS1wnDBzrYp?= =?us-ascii?Q?w6gOv9PABbhnxN9Ap3e0d2QQiXlDa0mQZmWnb4oL1aK83q80UuRfDx4qEGAe?= =?us-ascii?Q?HZm/oz/6+PcZQJchuiL46ccjqILwIaPe0T3thsPdpkPEAN76vHeD40JERIlR?= =?us-ascii?Q?pheGch63vqeNSwX5Ud47TrrT+Xa2Zotiiwn0/FHxmiQr6xyKx25jy5cOw5hj?= =?us-ascii?Q?xnae4xiPGAIDIZqHHqMeRiX7gRuTnfdvdaHveVuRvwn6xXWUOheNp+lz4O/t?= =?us-ascii?Q?PFU8IhB+UAtr5rMN+rceZXQv5BBTjTDJBnhgjAUB5G4iPtWBa2NC/QKaAknZ?= =?us-ascii?Q?m0jGtcPv28bMuMOixpPK2M2pou+oLBgkDhzLMDel2Xqwh7TyvH1l5noOoyiU?= =?us-ascii?Q?Vfcp/8ui9jbrm9NmBIfN/5qffEns0JX5RPvU7IdsnWLssUK4K2pmY4JSSJ5M?= =?us-ascii?Q?HW1TNf28BoT9GXTpUbxsMIR0B+HwhkkhOq0+NhgevgfvUsqXXnXprNXzWbnJ?= =?us-ascii?Q?gF+1b3xwb+uthn7Jx3YYWsCysceR6xOT+1kimrjZE1Zrh5iV6bcDdtuqqhVY?= =?us-ascii?Q?YNInxFooU7CLW1wQQnakujxVHsI7jJkY8Tg09kKRe1tpKmnCtZYJ9XOuHjPa?= =?us-ascii?Q?Yrcwuf2PaimMlUjsZ9U1bLG+t6yqPuQd535S8Edp76/GQYAF/Q4QPQVsQCLh?= =?us-ascii?Q?7JumurlZfwhSKuLiY2XBZk3+a8SCiJh?= X-MS-Exchange-SenderADCheck: 1 X-Microsoft-Antispam-Message-Info: dJ0ZiYQEw2EPXa07rzOz8luZ3U4wL5ddYgWhfuSMKfCe3/6ku67CmRPn+/aHhqUpzEMbalyTA40fuA67bduVXrZn/yhdwbIfGq7vTfKA61OcD2yf5yR9HfIAolW9y2RoZDgzyV9vj3eCO85MNcZPLymdW2z0fS7KSutypskpBC/JsltyWKTnwMi5gpSPLruCCLVy3um+Hs9kBTAKTZhX1AC20VS44Wg90gISZa5tQO4x/TrKSXnfh/OuP7UfX0kMmgEefT3Wsx0zIuo9OS+HVccf2ASM/uwBwo/FuLRxG97s/qCuPxUBOvSa//q01lt+YVfFe8upqLKlzDN5/2axXrH/Ozx/puwovcOJqetsHF5FHHDtqrgUCzaPAIduVe3cgpp7z2WSuOqq8F9zj+dS++G9X9Ry1gjCH35rI7hUbBY= X-OriginatorOrg: mit.edu X-MS-Exchange-CrossTenant-OriginalArrivalTime: 19 Feb 2019 16:30:48.8498 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: d2e9478e-b4fb-4fdf-24da-08d696879b61 X-MS-Exchange-CrossTenant-Id: 64afd9ba-0ecf-4acf-bc36-935f6235ba8b X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=64afd9ba-0ecf-4acf-bc36-935f6235ba8b; Ip=[18.9.28.11]; Helo=[outgoing.mit.edu] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR01MB2091 Archived-At: Subject: [Tools-discuss] intermittent TLS issues with tools.ietf.org? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Feb 2019 16:30:53 -0000 Hi all, I've been seeing some intermittent periods of TLS connection failures to tools.ietf.org, at times with different clients experiencing different behavior. Is there perhaps an issue with one of the backend machines? Thanks, Ben From nobody Tue Feb 19 08:44:04 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81F4F130F1E for ; Tue, 19 Feb 2019 08:44:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Qu6HJ3KtjRkI for ; Tue, 19 Feb 2019 08:44:01 -0800 (PST) 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 19BF1130F14 for ; Tue, 19 Feb 2019 08:44:01 -0800 (PST) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:64796 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 1gw8Ux-0004ha-6h; Tue, 19 Feb 2019 08:44:00 -0800 To: Benjamin Kaduk , tools-discuss@ietf.org References: <20190219163045.GU24387@kduck.mit.edu> From: Henrik Levkowetz Message-ID: <91c4dfec-96f5-6e61-f7ab-d713e920d6e7@levkowetz.com> Date: Tue, 19 Feb 2019 17:43:51 +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: <20190219163045.GU24387@kduck.mit.edu> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="XOUbTKngjoQxpgbSnxxkVvpMikdU3qMgV" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, kaduk@mit.edu X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org) X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [Tools-discuss] intermittent TLS issues with tools.ietf.org? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Feb 2019 16:44:03 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --XOUbTKngjoQxpgbSnxxkVvpMikdU3qMgV Content-Type: multipart/mixed; boundary="40BkeGUp6KqL7ECawrI3MfjJ2M2pJOObD"; protected-headers="v1" From: Henrik Levkowetz To: Benjamin Kaduk , tools-discuss@ietf.org Message-ID: <91c4dfec-96f5-6e61-f7ab-d713e920d6e7@levkowetz.com> Subject: Re: [Tools-discuss] intermittent TLS issues with tools.ietf.org? References: <20190219163045.GU24387@kduck.mit.edu> In-Reply-To: <20190219163045.GU24387@kduck.mit.edu> --40BkeGUp6KqL7ECawrI3MfjJ2M2pJOObD Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Ben, Yes, durif.tools.ietf.org is in trouble after a heavy spam run. I'm working at getting it back. Best, Henrik On 2019-02-19 17:30, Benjamin Kaduk wrote: > Hi all, >=20 > I've been seeing some intermittent periods of TLS connection failures t= o > tools.ietf.org, at times with different clients experiencing different > behavior. Is there perhaps an issue with one of the backend machines?= >=20 > Thanks, >=20 > Ben >=20 > ___________________________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/tools-discuss >=20 > Please report datatracker.ietf.org and mailarchive.ietf.org > bugs at http://tools.ietf.org/tools/ietfdb > or send email to datatracker-project@ietf.org >=20 > Please report tools.ietf.org bugs at > http://tools.ietf.org/tools/issues > or send email to webmaster@tools.ietf.org >=20 --40BkeGUp6KqL7ECawrI3MfjJ2M2pJOObD-- --XOUbTKngjoQxpgbSnxxkVvpMikdU3qMgV Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAlxsMkgACgkQTptXS4+7 Fxr9ABAAxhMJ/pYPiJA9q1i4gjnXU3hUGN0DAWDzkJr03mHSKt0PDFAuCPfTN7gY hdwFZnq/m8OAMJAOiwyeA2gYauEbTFWq/pwSf5gSB03OezHJu/AvRtFLJejEJYJ6 U8yn3qeHI306BzJfuMn4Us05yeH4iyAvLbtB34iSFgAdfzzKiNZSK5ZMtp/vKYsY 9RqXZAyQGpBm5JrxCFSwrKjlPzvIX7Kj3t6Fr1MteN9cVLcVs5EsaRAV5Wci9YOI CxiLzZ8a6FDZ8Z3p7skROdtRfNXJw8iLkuGrH2kxLlvPYYyd1w18oRuLpAPgwgY0 a3Oz6wt9h7Eqop/Snsk7wF5TirWXOj83jQvGHZFE8RKzghdNhyZYLwQ5pMYnf99w ZxN7zVXXlVSiG5YR3wgBRXCB7Jhpv0N13jtdvKgqza7SyFBZK9i7Fk/1IPInden6 dXorAMTOm5q3JZDqPJP45NU8XQwH1ABCwzqrj0LUz/f75o07Qx0P+mbptskwsbgq maSkOmTIsuIKvZ1VRyrOomgug4ZXC3xNqoJHdaOGR9OvBB6bAg695oYaPm88A7sL IFzwfC4FUGyE549V34/DwEb+k/qrkUjaUczmN4X2+h9Xw6WRrI9pGUJpFoPN02wv tWIFXTTdw6ObI13BTdEST3+uzorYuJBHR74j4xI+h3ENm+FHubg= =oKGi -----END PGP SIGNATURE----- --XOUbTKngjoQxpgbSnxxkVvpMikdU3qMgV-- From nobody Wed Feb 27 05:34:14 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 898EE127287 for ; Wed, 27 Feb 2019 05:34:12 -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, 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 Aeem3SScQdSN for ; Wed, 27 Feb 2019 05:34:10 -0800 (PST) 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 992EA130EAA for ; Wed, 27 Feb 2019 05:34:10 -0800 (PST) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:58431 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 1gyzLc-0005Yp-FL; Wed, 27 Feb 2019 05:34:09 -0800 To: Carsten Bormann , tools-discuss References: From: Henrik Levkowetz Message-ID: <465df686-2543-2b8d-df81-3de036452a16@levkowetz.com> Date: Wed, 27 Feb 2019 14:34:01 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="MWhc7TN5QeRQVfg3NoQD92sXsURCxoGOs" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: tools-discuss@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: [Tools-discuss] IEEE in bibxml2 vs. bibxml6 X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2019 13:34:12 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --MWhc7TN5QeRQVfg3NoQD92sXsURCxoGOs Content-Type: multipart/mixed; boundary="GqFSbJ8mlD9qrnCRrJC8dl2RFPa2FvnMn"; protected-headers="v1" From: Henrik Levkowetz To: Carsten Bormann , tools-discuss Message-ID: <465df686-2543-2b8d-df81-3de036452a16@levkowetz.com> Subject: Re: [Tools-discuss] IEEE in bibxml2 vs. bibxml6 References: In-Reply-To: --GqFSbJ8mlD9qrnCRrJC8dl2RFPa2FvnMn Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Carsten, Sorry for the delay in responding to this. On 2019-02-15 15:28, Carsten Bormann wrote: > At some point I=E2=80=99d like to have a rational solution for the belo= w.=20 > Copying the IEEE cobwebs from bibxml2 to bibxml6 would solve the > problem (I.e., allow me to look up IEEE in bibxml6 as opposed to > bibxml2 as of now). As would creating a bibxml.IEEE or some such from > both directories and keeping them in sync. I don't know why the split exist. It looks as if the bibxml2 IEEE items haven't been updated since 2013, bibxml6 since 2015. I have a dim recollection of looking into that some years ago, and discovering that the web resource used to populate one of these had stopped being maintained. In the long run, rather than trying to patch up the old TCL scripts, I would prefer to build new bibxml generation infrastructure on www.ietf.org or datatracker.ietf.org. For now, I'll happily copy the bibxml2 IEEE entries to bibxml6. Shall I do so? Best regards, Henrik >=20 > Gr=C3=BC=C3=9Fe, Carsten >=20 >=20 >> On Mar 15, 2017, at 08:36, Carsten Bormann wrote: >>=20 >> There are IEEE citation files both in bibxml2 and bibxml6. >> Is there a way to automatically decide with one to use? >> Could the bibxml2 files maybe be copied over to bibxml6 so we can alwa= ys use bibxml6 for IEEE? >>=20 >> (kramdown-rfc currently uses bibxml2 for IEEE; there is currently no e= asy way to access bibxml6. I can=E2=80=99t switch that over to bibxml6, = as the bibxml2 references are in use in existing documents, e.g. for IEEE= 754. Why are we even doing this splitting up? 90 % of the files are in= bibxml3 anyway.) >>=20 >> Gr=C3=BC=C3=9Fe, Carsten >>=20 >=20 > ___________________________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/tools-discuss >=20 > Please report datatracker.ietf.org and mailarchive.ietf.org > bugs at http://tools.ietf.org/tools/ietfdb > or send email to datatracker-project@ietf.org >=20 > Please report tools.ietf.org bugs at > http://tools.ietf.org/tools/issues > or send email to webmaster@tools.ietf.org >=20 --GqFSbJ8mlD9qrnCRrJC8dl2RFPa2FvnMn-- --MWhc7TN5QeRQVfg3NoQD92sXsURCxoGOs Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAlx2kckACgkQTptXS4+7 FxrerA//UXDY3YkMEtmY/yQQeObzamcrW53wWJvQO7mk0apoI1mM1U0XvIJi/pM9 umjuPP6tMnNbEdXJBl2gqW9VfHIhCzZy/MAm/X7PPgQzBdzatebTenSv83TPjhl6 eeHSWiom0fD0ZZV3kspJhMA9eOukWUAQ3I9G6ISjZussI1afKCmhU9qqxl9xPOfK w0DP1qYJ5Vejk1Uv84dLJIOhJZdxsOxr77zGgYRtS9eWYuhZUiMfliUf03rvQ85p MdwOCWpVGdY4OAgoQe7e7TJrzryLPuaUYwbtjpxcCv8a4KDo/VLfsnt5N0OXHOKG kpc8GLkncwI0R8v7r1peCXaiOGxA4QZWp+kATwxbukodeZJDQxW5Pp93zLT3zBOg 1dwZq8rIrIJ5AaFg6Qpe28gNKn9w5p47PCWD0w1a/eg5kEx3NPNqNNb72Naw6EmQ jiV0oUksF8M/AvVkPWRUcZwiLilVLcmggkkaWDPWbaCFRhH6VXiyv6aiDJZbqxdt 2gHvxHdIIy8D29sdnbIMqGhUPdYmNfTpK37yXulr0Ty7SuNYVRgsFqPwqeZGt7Ol 0CMUwU3T+kGGaqMCk9ad1NDHbyxaqNb9B7vnASxiaKB+wqBd/NRzuUMHP7UfbRaS mVkNfEEyd3UQj8q0R1MYEpmRWuTjmmYWbtu2Vc6/HS8pXaunMY0= =0Zbz -----END PGP SIGNATURE----- --MWhc7TN5QeRQVfg3NoQD92sXsURCxoGOs-- From nobody Wed Feb 27 05:38:40 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEB50130EC5 for ; Wed, 27 Feb 2019 05:38:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.199 X-Spam-Level: X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 sJGQn-GsK-p3 for ; Wed, 27 Feb 2019 05:38:36 -0800 (PST) Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 DC0E9127287 for ; Wed, 27 Feb 2019 05:38:35 -0800 (PST) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [IPv6:2001:638:708:30c8:406a:91ff:fe74:f2b7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id x1RDcRTM017576; Wed, 27 Feb 2019 14:38:32 +0100 (CET) Received: from [192.168.217.106] (p54A6C2FE.dip0.t-ipconnect.de [84.166.194.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 448cFv1RSZz1Br7; Wed, 27 Feb 2019 14:38:27 +0100 (CET) Content-Type: multipart/signed; boundary="Apple-Mail=_0756311A-DE67-4629-854F-D9755ABA3300"; protocol="application/pgp-signature"; micalg=pgp-sha256 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Carsten Bormann In-Reply-To: <465df686-2543-2b8d-df81-3de036452a16@levkowetz.com> Date: Wed, 27 Feb 2019 14:38:26 +0100 Cc: tools-discuss X-Mao-Original-Outgoing-Id: 572967504.740648-d3d2ec68c21a91794a3f0e5be2362668 Message-Id: References: <465df686-2543-2b8d-df81-3de036452a16@levkowetz.com> To: Henrik Levkowetz X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [Tools-discuss] IEEE in bibxml2 vs. bibxml6 X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2019 13:38:38 -0000 --Apple-Mail=_0756311A-DE67-4629-854F-D9755ABA3300 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 On Feb 27, 2019, at 14:34, Henrik Levkowetz = wrote: >=20 > For now, I'll happily copy the bibxml2 IEEE entries to bibxml6. >=20 > Shall I do so? Please do, assuming there are no conflicts. Then I=E2=80=99ll switch to bibxml6 for IEEE.* references in the next = version of kramdown-rfc. Gr=C3=BC=C3=9Fe, Carsten --Apple-Mail=_0756311A-DE67-4629-854F-D9755ABA3300 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIzBAEBCAAdFiEEcr05t4NZlx5Xee/8VkscnDT509sFAlx2ktEACgkQVkscnDT5 09uKcw//QQyWB34G3dZlMXl2KkC40/Rpn306uWpORPtORRrdfDoc3tV+t0fYfNQE T80vlTjxLlx+rDlwApnIAvtFO2tYmH2ooYfL5d8H+Kb+ouMVloffBUWyYy6BbPmy 8KRMJzjd5WaSnVY8yVDojFVfO4/oDR5imqf1UoPcI56J1I/Jl/TVZFU3DGAxRUCu BkFWQhruuZE5HwVjfJKIFRtl/NpeK+TW3z9Z4RApPLt2xOnGImR4KworXMbt3ebU /wYLumZ6mM4FfWZjVC/gzyV+RF2ziAXjcZ/qZvjhVjwAiuGLC3wLeyM+CK/Edfy0 00whRfx70bf10TZmkKH/HZHP5xr2NUkecx6ttGqPSv3yEdAX/zHcrSo7p2OxUlRy XkbfUfkkJBWMR5+1yvOS9hxbkc5Dxb+NvQjMHsIDXnoMkCCxWVhXcJ0m836SD6aU uyuF/P0WbzzYv3llnQ03c98fmFYbo9YxI6U25pfj+BnRGb8lmnqGjGEyj09TeeQI 18rbV2pnhLax6JfhmKkiv5KcIJud0OXEAEZ9nIlk80YevbYVpOi99mKZkYqVCrsj PkiaLsxnrLAMISNrwE152i8AnAStjKya7/OLpgRVQ4kmKW4ONQsGwSjduTO0Sw2l Euz9n2spNvWXlqBj3NUMcoaQIDaJsHyfCJu3WORjR6dj5D0uyvM= =6FbY -----END PGP SIGNATURE----- --Apple-Mail=_0756311A-DE67-4629-854F-D9755ABA3300-- From nobody Wed Feb 27 05:45:54 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2D07130FC7 for ; Wed, 27 Feb 2019 05:45:52 -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, 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 yIM5wyRmryyZ for ; Wed, 27 Feb 2019 05:45:51 -0800 (PST) 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 6761F124C04 for ; Wed, 27 Feb 2019 05:45:51 -0800 (PST) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:58529 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 1gyzWw-0002jD-LT; Wed, 27 Feb 2019 05:45:51 -0800 To: Carsten Bormann References: <465df686-2543-2b8d-df81-3de036452a16@levkowetz.com> Cc: tools-discuss From: Henrik Levkowetz Message-ID: <295f4971-c8b5-aca8-e25f-8a26f949bde2@levkowetz.com> Date: Wed, 27 Feb 2019 14:45:43 +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: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="etdVxMpPMfoQsArIAnjksJpW8FClFMXTu" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: tools-discuss@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: [Tools-discuss] IEEE in bibxml2 vs. bibxml6 X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2019 13:45:53 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --etdVxMpPMfoQsArIAnjksJpW8FClFMXTu Content-Type: multipart/mixed; boundary="Vwm2VpnD6XJuJSEsCGNqDSpl5cUM20aKR"; protected-headers="v1" From: Henrik Levkowetz To: Carsten Bormann Cc: tools-discuss Message-ID: <295f4971-c8b5-aca8-e25f-8a26f949bde2@levkowetz.com> Subject: Re: [Tools-discuss] IEEE in bibxml2 vs. bibxml6 References: <465df686-2543-2b8d-df81-3de036452a16@levkowetz.com> In-Reply-To: --Vwm2VpnD6XJuJSEsCGNqDSpl5cUM20aKR Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2019-02-27 14:38, Carsten Bormann wrote: > On Feb 27, 2019, at 14:34, Henrik Levkowetz wrot= e: >>=20 >> For now, I'll happily copy the bibxml2 IEEE entries to bibxml6. >>=20 >> Shall I do so? >=20 > Please do, assuming there are no conflicts. > Then I=E2=80=99ll switch to bibxml6 for IEEE.* references in the next v= ersion of kramdown-rfc. Ok, done. Best, Henrik --Vwm2VpnD6XJuJSEsCGNqDSpl5cUM20aKR-- --etdVxMpPMfoQsArIAnjksJpW8FClFMXTu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAlx2lIcACgkQTptXS4+7 FxoxkhAAxsPBVGF7ZDzOkrMwo6ZjCNqElrnmdWwrIyNGvtM3RFl/iH8gIv6NZw2H h/0+stFkhniJkjmFDbRqmDQUeGmPx2/VZD4j3qUllekhyyJIaXRHqzxCdZtq9L07 59iYYekfDjmscYfnvUOLQFYREwD6ocMLarlb/rX29/ZFMEM/2UYYnr15z+CObMJw R07E+DRtaHy5dRm2LbND7GkAC/klQU+8SZ6Nf7+qThegty9EjUV2EQTqNsvyVe1z 6gasHP4ZYPM3zLbhbgM0TOn6b+bJJDQfCsBbX/0biH3XUmucqhEbt/jN232Su+iX 5uVJz//hQW7SYhvDPNAoeiITn7kKdEQ/Ka1gpC2ohEVPTSVuqT3aBgOGx5AHIPpm OwlTbATipepTmhecsSHucGgpbdGzuVxp4IxJNY9mAitHw0jCVq3+qKgnb9KNm0Ko QchhVQnYLdN7SyLmfOLfxVEJF6NX7VN2HOphpxwywoHkrsNlkGzcCiqaHezNylz0 HvuMDzK/7cUhve0pSc4VUonBPicrkgHpLKaixKVP44Ie+iWWhyKn7He5/DU16fhM ODYpH96uB+p+gl/hqhJmq+kSXGQ798a3i2ico7ZXWZNklecEkXwCzTkL+kPjXc9j LJZWSedW0PQ4R7KOtw4npsZLKZHjtBIXxzNpNLJx2A59us/EOI4= =rTev -----END PGP SIGNATURE----- --etdVxMpPMfoQsArIAnjksJpW8FClFMXTu-- From nobody Wed Feb 27 06:53:37 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36CA7130FCF; Wed, 27 Feb 2019 06:53:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.199 X-Spam-Level: X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 nXz4H6NyfOQm; Wed, 27 Feb 2019 06:53:33 -0800 (PST) Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 9B96C130EDE; Wed, 27 Feb 2019 06:53:33 -0800 (PST) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [134.102.200.7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id x1RErOAI016194; Wed, 27 Feb 2019 15:53:29 +0100 (CET) Received: from [192.168.217.106] (p54A6C2FE.dip0.t-ipconnect.de [84.166.194.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 448dwN0cpNz1Bp8; Wed, 27 Feb 2019 15:53:23 +0100 (CET) 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: <295f4971-c8b5-aca8-e25f-8a26f949bde2@levkowetz.com> Date: Wed, 27 Feb 2019 15:53:23 +0100 Cc: tools-discuss , Henrik Levkowetz X-Mao-Original-Outgoing-Id: 572972001.2844959-b42bc5a4d812a976107026a904cc3579 Content-Transfer-Encoding: quoted-printable Message-Id: <73C747D7-442B-4AD6-9DB5-4B9209E03B4F@tzi.org> References: <465df686-2543-2b8d-df81-3de036452a16@levkowetz.com> <295f4971-c8b5-aca8-e25f-8a26f949bde2@levkowetz.com> To: RFC Markdown X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [Tools-discuss] IEEE in bibxml2 vs. bibxml6 X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2019 14:53:35 -0000 Kramdown-rfc2629 version 1.2.11 now searches bibxml6 for IEEE.* = references such as: IEEE.754.1985: There should be no user-visible change for IEEE.* references that = already worked. But new ones should now be working: those that have been added to = bibxml6, but not to bibxml2. See for yourself: http://xml2rfc.tools.ietf.org/public/rfc/bibxml6/ As always, update via gem update kramdown-rfc2629 (add a sudo if needed on your platform), or simply `gem update` to = update all rubygems. Gr=C3=BC=C3=9Fe, Carsten > On Feb 27, 2019, at 14:45, Henrik Levkowetz = wrote: >=20 >=20 > On 2019-02-27 14:38, Carsten Bormann wrote: >> On Feb 27, 2019, at 14:34, Henrik Levkowetz = wrote: >>>=20 >>> For now, I'll happily copy the bibxml2 IEEE entries to bibxml6. >>>=20 >>> Shall I do so? >>=20 >> Please do, assuming there are no conflicts. >> Then I=E2=80=99ll switch to bibxml6 for IEEE.* references in the next = version of kramdown-rfc. >=20 > Ok, done. >=20 > Best, > Henrik >=20