From nobody Wed Jun 13 15:33:56 2018 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 02EBD130DC9 for ; Wed, 13 Jun 2018 15:33:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.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 T5UXuYWUHkAc for ; Wed, 13 Jun 2018 15:33:51 -0700 (PDT) Received: from mail-wr0-x234.google.com (mail-wr0-x234.google.com [IPv6:2a00:1450:400c:c0c::234]) (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 C4A4E124BE5 for ; Wed, 13 Jun 2018 15:33:50 -0700 (PDT) Received: by mail-wr0-x234.google.com with SMTP id l10-v6so4362990wrn.2 for ; Wed, 13 Jun 2018 15:33:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/JEs59E3YAMaHJ38DxxTZDz9NOfToAVI7Oxu1e3NWDw=; b=XMyLjfJ5Ga6fc9LLPcy5a8G3v9Gvp+Kh4dtWERUqL7Pbkn3fRc1XPtwvUCU5K630G0 H18BY4ffH8lINrLUtdLLC8wHfSZxlVm/1qlSedlzBlxS/S8syX/7xlNgmFvxhS8FSaDb qzUXTimfdIZ766BxnCa1F7Su1sGYhsm9WLKiUNRYix+zxuTNQcDlRlzVB4ru9yVlkxFz Cef04G22yBdO1McsMqqyuKD+I2diarnP6rohoaMay/xepvxu7jsUC54hwScIbqCBKFWB zgfglICLqizYyEis0s8zJ+6KYQIQ7d7xIJLTkT6n7Zg7qpXp9sO0LDPIPFNYew9YaJLS uSLw== 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=/JEs59E3YAMaHJ38DxxTZDz9NOfToAVI7Oxu1e3NWDw=; b=C/PLhQQXfFJZzx8ZEnLYzMiuZKOHuNx/M2TAtqhk1HLFyH2o31u31JoBSRutrQBk5g 4Uv4uafk583K1Z6gcSad4pE8bHxUj0f2bcX/7GlwF2tREM1K77UhgZvMvlh48Cv+XZSj gY2WxA47vUbUco2fT3FAv9WqdUoJMLuoBL43PcSV7Y+z1L6RMUZQ7h16kPt3EHxI6KZ5 vqaT/w4pMJKfo8MoDLcPpGXfBVKvp8nk/4M3mMvHpm/EiVxCJOH+Q8oIk5014t7PcICG tNF1EleT4Zi5gd7MEoWpR+70zr8xaOgSrqzh2a/5KJ8qaQ76iCx+UGiHnGfjJMhReKZ5 aFXw== X-Gm-Message-State: APt69E26IYdPMCqT2jDccg4omtpx54vx9mJyQ3QDvqP+cxG1KQJIqbZD UrPYtt6vtsfiZvlBFZ4B0VIeW2rCPnr+3ZL3praobU6lD1E= X-Google-Smtp-Source: ADUXVKKSiyPJHRf7kgtn9ql9+KFYCEUjM3oj6NXNRFMutbLAaJENuaX8Ixt4TMvJqPqd1XaoIku05vdF7+lBe5TSJzc= X-Received: by 2002:adf:bbcd:: with SMTP id z13-v6mr26513wrg.183.1528929228765; Wed, 13 Jun 2018 15:33:48 -0700 (PDT) MIME-Version: 1.0 References: <3141C32A-E190-4DE8-9E6A-1462EFD0E47B@vigilsec.com> <3EF35561-FCB9-449A-ABC4-8AC936267170@vigilsec.com> In-Reply-To: <3EF35561-FCB9-449A-ABC4-8AC936267170@vigilsec.com> From: Warren Kumari Date: Wed, 13 Jun 2018 18:33:12 -0400 Message-ID: To: Russ Housley Cc: Eric Rescorla , Tools Discussion Content-Type: multipart/alternative; boundary="000000000000915107056e8d930f" Archived-At: Subject: Re: [Tools-discuss] Reviewing with Phabricator (and Datatracker integration) X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 22:33:55 -0000 --000000000000915107056e8d930f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, May 31, 2018 at 4:43 PM Russ Housley wrote: > > On May 31, 2018, at 4:27 PM, Eric Rescorla wrote: > > On Thu, May 31, 2018 at 10:30 AM, Russ Housley > wrote: > >> I would be interested in the experiences of other ADs. >> > > I think Warren has spent a little time on it. > > > =E2=80=8BYup, Warren has spent some time on it, and there are some bits whi= ch he loves, and some bits which are less than great. The bits which he doesn't like (much of this may be user error): 1: I'd like there to be an easier way to =E2=80=8Bfind what drafts I need t= o review - currently I go to the agenda, find a draft name, and then search for that in Phabricator. 2: I do my reviews on an iPad, reading and annotating (using GoodReader) the PDFs. This is partly because I like the layout / ease of annotation, but also because I do a lot of this on planes and similar, where I have no Internets. I'd like some magic way for this to integrate (note the "magic" in the previous sentence). 3: I complete the review, and then copy and paste the review bits into the Datatracker manually. Basically I am using Phabricator simply as a stand-alone code review tool, without any of the integrations, etc. None of these are Phabricator's fault, rather a: my not having figured out a work flow yet, and b: the fact that it isn't really integrated with Datatracker. I'm also somewhat confused about how multiple people's reviews would interact with each others -- it almost feels like each AD having their own separate instance would make more sense (but this might be because, until now, we've largely worked separately. So, with the "bits that I don't like" out of the way: I really like how easy it is to indicate where in a document the issue / nits are. As an example: " Section: Abstract This document discusses most common scenarios of connecting an O: discusses most common P: discusses the most common" Copying and pasting the above is a huge waste of time (probably 25 seconds per), being able to scroll in Phabricator, click a line and say "add 'the'" is much faster and more efficient. There is also the issue at the end of the process -- if I've submitted 15 comments scattered throughout the document, it is a massive waste of time to confirm that all have been addressed -- Phabricator makes this much better. So, some more / better tooling around this to: 1: provide links from the telechat agenda (or a clone of the telechat page with links to Phabricator) 2: some way to autogenerate the ballot for users other than EKR. 3: encouraging people to use this instead of the current only emil system all seem like they would be great. W > I would like to know how easy it would be for Directorates and Review >> Teams to leverage your work. >> > > Understanding that would, I think, require understanding how those tools > work. I don't have a real sense of how those tools work. I know Tero has > some secdir stuff. Does everyone have their own thing? > > > No. The datatracker supports all of the reviews in a manner similar to > ballots. The reviewer two options. First, the reviewer puts text into a > frame on a datatracker page, and then the datatracker turns it into email= . > This is very similar to the way IESG ballots are handled. Second, the > reviewer sends his own email and give the datatracker the URL into the ma= il > archive. > > Your description makes me wonder if this tooling could work with an API > related to the first approach. > > Russ > > ___________________________________________________________ > 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 > --=20 I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf --000000000000915107056e8d930f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Th= u, May 31, 2018 at 4:43 PM Russ Housley <housley@vigilsec.com> wrote:

On May 31, 2018, at 4:27 PM, Eric Rescorla <ekr@rtfm.com> wrote:

On T= hu, May 31, 2018 at 10:30 AM, Russ Housley <housley@vigilsec.com>= ; wrote:
I would be interested in the experiences of other ADs.
<= /blockquote>

I think Warren has spent a little time on i= t.


=

=E2=80=8BYup, Warren has spent some= time on it, and there are some bits which he loves, and some bits which ar= e less than great.

The bits which he doesn't like (much of this ma= y be user error):
1: I'd like there to be an easier way to =E2=80=8Bfin= d what drafts I need to review - currently I go to the agenda, find a draft= name, and then search for that in=C2=A0Phabricator.

2: I do my reviews o= n an iPad, reading and annotating (using GoodReader) the PDFs. This is part= ly because I like the layout / ease of annotation, but also because I do a = lot of this on planes and similar, where I have no Internets. I'd like = some magic way for this to integrate (note the "magic" in the pre= vious sentence).

3= : I complete the review, and then copy and paste the review bits into the D= atatracker manually. Basically I am using=C2=A0Phabricat= or simply as a stand-alone code review tool, without any of the integration= s, etc.=C2=A0

None of these are=C2=A0Phabricator's fault, rather a: my not having figured out= a work flow yet, and b: the fact that it isn't really integrated with = Datatracker.=C2=A0

I'm also somewhat confused about how mult= iple people's reviews would interact with each others -- it almost feel= s like each AD having their own separate instance would make more sense (bu= t this might be because, until now, we've largely worked separately.=C2= =A0

<= span style=3D"color:rgb(34,34,34);font-family:sans-serif;font-size:13px;fon= t-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-= weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-tran= sform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255= ,255);text-decoration-style:initial;text-decoration-color:initial;float:non= e;display:inline">So, with the "bits that I don't like" out o= f the way:
I really like how easy it is to indicate where in a document = the issue / nits are.=C2=A0

As an example:
<= div class=3D"gmail_default" style=3D"font-family:verdana,sans-serif">"= Section: Abstract
   This document discusses most common scenarios of connecting a=
n
O: discusses most common
P: dis=
cusses the most common"

Copying and pasting the above is a huge waste of time (probably 2=
5 seconds per), being able to scroll in Phabricator, click a line and say &=
quot;add 'the'" is much faster and more efficient.
There is also the issue at the end of the process -- if I'=
;ve submitted 15 comments scattered throughout the document, it is a massiv=
e waste of time to confirm that all have been addressed -- Phabricator make=
s this much better. 

So, some more / better tooling around this to:
2: some way to autoge=
nerate the ballot for users other than EKR.
3: enc=
ouraging people to use this instead of the current only emil system
<= pre style=3D"font-family:verdana,sans-serif;white-space:pre-wrap;font-size:= 13px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:norm= al;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;t= ext-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-= decoration-style:initial;text-decoration-color:initial;color:rgb(0,0,0);wor= d-wrap:break-word">all seem like they would be great.
W

=C2=A0
=
<= div>I would like to know how easy it would be for Directorates and Review T= eams to leverage your work.

Und= erstanding that would, I think, require understanding how those tools work.= I don't have a real sense of how those tools work. I know Tero has som= e secdir stuff. Does everyone have their own thing?

No.=C2=A0 The datatracker supports al= l of the reviews in a manner similar to ballots.=C2=A0 The reviewer two opt= ions.=C2=A0 First, the reviewer puts text into a frame on a datatracker pag= e, and then the datatracker turns it into email.=C2=A0 This is very similar= to the way IESG ballots are handled.=C2=A0 Second, the reviewer sends his = own email and give the datatracker the URL into the mail archive.
Your description makes me wonder if this tooling could work= with an API related to the first approach.

Russ

__________________________________________________= _________
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


--
I don't t= hink the execution is relevant when it was obviously a bad idea in the firs= t place.
This is like putting rabid weasels in your pants, and later exp= ressing regret at having chosen those particular rabid weasels and that pai= r of pants.
=C2=A0 =C2=A0---maf
--000000000000915107056e8d930f-- From nobody Fri Jun 15 09:14:36 2018 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 72E05130FDA for ; Fri, 15 Jun 2018 09:14:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.909 X-Spam-Level: X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] 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 aXcNMvbAWqAh for ; Fri, 15 Jun 2018 09:14:22 -0700 (PDT) Received: from mail-ot0-x22e.google.com (mail-ot0-x22e.google.com [IPv6:2607:f8b0:4003:c0f::22e]) (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 2ED5E130FEC for ; Fri, 15 Jun 2018 09:14:22 -0700 (PDT) Received: by mail-ot0-x22e.google.com with SMTP id 92-v6so11563478otw.9 for ; Fri, 15 Jun 2018 09:14:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=02fG+zMliXTENbpJPQBSnOCsmj71xR0u++WBEIeUnY0=; b=LdVArIBEb+j7YOZvUXRh6l5aUi3pQstqK36lw24GVjpbPbFpd7VXR1vLOrMFUGKeLh ltI9zgLoSuM/GevdXmN3ljgzFDJB6tv8bJbYfYFFrj6w4ppB44SGkBpRy8KL9kMe2ON/ c3K/L0UuwAMRqPMAgRD2YjWFFv/YK4wZtm64vkYesjwHtLCRJuAyUylExi/PwS6IUrgu fOcqsX2pcaGbO9Dx4wfORIuYuZc0eu6qimqVwsmqiUhlYJtkXTKV0ujVyMGwTTDPeV6F wLJr5z6Uf/54KygyAn5SoRyr3P7kzRhZIBsUM0YWo3erFKUnavzboWImddR/oPt4f59f vpfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=02fG+zMliXTENbpJPQBSnOCsmj71xR0u++WBEIeUnY0=; b=NdrY2o88WIUtwFyINo6AD5mPYnkyXyRzvpiO2skpU6TT2TfQlajViuEpMG72KPAtHt rMVluREPxiE/VI+lkZ9W2Yqql67QXRVhpk0WbcSF/qeuCg3J+5juYis+PJxcrAdS9APl JKiiZf7XBIeCzuAB+Mm4mE1HL6/dja+LUvHay5WG3AjtXMoLT61YSN5MG0Zj9pXqfSPV RQhp2eOmB5lQ8LpsAtIrpv6Y1jd5jkbdFSe1Am8wuKXPq1VFoIVFN5bm58v6RLNH+lDS qfnrfnKfovKC5qQyEIBzkbECNvGIxNjWbKmBbzOPRCR8HU3VRhplbU5upkmL/oGiiLeK jBGw== X-Gm-Message-State: APt69E0Ah0GRpushN4Ukyr21hFX53edgpKDDgHMYiruQTxc/e+dOi/B2 Bb8M0uutastrNI6msDUp6Pa2vpvPM28E5WIiy/AG2u8L X-Google-Smtp-Source: ADUXVKKIokfLmJqToG/d7GjGmfhXmeM62H0J/PTS3wllKPVXPfjx2RCld6olydwYGOEAaPzLZa7D0y2/ZCIjqF+OhR8= X-Received: by 2002:a9d:4905:: with SMTP id e5-v6mr1480921otf.101.1529079261508; Fri, 15 Jun 2018 09:14:21 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac9:3a8a:0:0:0:0:0 with HTTP; Fri, 15 Jun 2018 09:13:41 -0700 (PDT) In-Reply-To: References: <3141C32A-E190-4DE8-9E6A-1462EFD0E47B@vigilsec.com> <3EF35561-FCB9-449A-ABC4-8AC936267170@vigilsec.com> From: Eric Rescorla Date: Fri, 15 Jun 2018 09:13:41 -0700 Message-ID: To: Warren Kumari Cc: Russ Housley , Tools Discussion Content-Type: multipart/alternative; boundary="0000000000003743ab056eb08298" Archived-At: Subject: Re: [Tools-discuss] Reviewing with Phabricator (and Datatracker integration) X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 16:14:35 -0000 --0000000000003743ab056eb08298 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Jun 13, 2018 at 3:33 PM, Warren Kumari wrote: > > > On Thu, May 31, 2018 at 4:43 PM Russ Housley wrote= : > >> >> On May 31, 2018, at 4:27 PM, Eric Rescorla wrote: >> >> On Thu, May 31, 2018 at 10:30 AM, Russ Housley >> wrote: >> >>> I would be interested in the experiences of other ADs. >>> >> >> I think Warren has spent a little time on it. >> >> >> > =E2=80=8BYup, Warren has spent some time on it, and there are some bits w= hich he > loves, and some bits which are less than great. > > The bits which he doesn't like (much of this may be user error): > 1: I'd like there to be an easier way to =E2=80=8Bfind what drafts I need= to > review - currently I go to the agenda, find a draft name, and then search > for that in Phabricator. > This I actually do have some tooling for: the system will automatically scrape the agenda and assign things for you to review. It doesn't work perfectly though, because it currently just adds them to your list and it doesn't run them automatically. 2: I do my reviews on an iPad, reading and annotating (using GoodReader) > the PDFs. This is partly because I like the layout / ease of annotation, > but also because I do a lot of this on planes and similar, where I have n= o > Internets. I'd like some magic way for this to integrate (note the "magic= " > in the previous sentence). > This I don't know how to fix. 3: I complete the review, and then copy and paste the review bits into the > Datatracker manually. Basically I am using Phabricator simply as a > stand-alone code review tool, without any of the integrations, etc. > This should actually just work, if you run my tools locally with iphab.py ballot . Have you tried? None of these are Phabricator's fault, rather a: my not having figured out > a work flow yet, and b: the fact that it isn't really integrated with > Datatracker. > > I'm also somewhat confused about how multiple people's reviews would > interact with each others -- it almost feels like each AD having their ow= n > separate instance would make more sense (but this might be because, until > now, we've largely worked separately. > Yeah, basically you just end up with a zillion comments from different people. I wonder if that's good? 2: some way to autogenerate the ballot for users other than EKR. > > As above, this should work now. Can you try? -Ekr 3: encouraging people to use this instead of the current only emil system > > all seem like they would be great. > > W > > > > >> I would like to know how easy it would be for Directorates and Review >>> Teams to leverage your work. >>> >> >> Understanding that would, I think, require understanding how those tools >> work. I don't have a real sense of how those tools work. I know Tero has >> some secdir stuff. Does everyone have their own thing? >> >> >> No. The datatracker supports all of the reviews in a manner similar to >> ballots. The reviewer two options. First, the reviewer puts text into = a >> frame on a datatracker page, and then the datatracker turns it into emai= l. >> This is very similar to the way IESG ballots are handled. Second, the >> reviewer sends his own email and give the datatracker the URL into the m= ail >> archive. >> >> Your description makes me wonder if this tooling could work with an API >> related to the first approach. >> >> Russ >> >> ___________________________________________________________ >> 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 >> > > > -- > I don't think the execution is relevant when it was obviously a bad idea > in the first place. > This is like putting rabid weasels in your pants, and later expressing > regret at having chosen those particular rabid weasels and that pair of > pants. > ---maf > --0000000000003743ab056eb08298 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, Jun 13, 2018 at 3:33 PM, Warren Kumari <warren@kumari.net&= gt; wrote:


On Thu, May 31, 2018 at 4:43 PM Rus= s Housley <hou= sley@vigilsec.com> wrote:

O= n May 31, 2018, at 4:27 PM, Eric Rescorla <ekr@rtfm.com> wrote:

On Thu, May 31, = 2018 at 10:30 AM, Russ Housley <housley@vigilsec.com> wro= te:
I would be interested in the experiences of other ADs.
=

I think Warren has spent a little time on it.


=

=E2=80=8BYup, Warren has spent some time on it, and there are so= me bits which he loves, and some bits which are less than great.

The bits which he doesn't like (much of this may = be user error):
1: I'= ;d like there to be an easier way to =E2=80=8Bfind what drafts I need to re= view - currently I go to the agenda, find a draft name, and then search for= that in=C2=A0Phabricator.

This I actually do have some tooling for:= the system will automatically scrape the agenda and assign things for you = to review. It doesn't work perfectly though, because it currently just = adds them to your list and it doesn't run them automatically.



2: I do my reviews on an iPad, reading = and annotating (using GoodReader) the PDFs. This is partly because I like t= he layout / ease of annotation, but also because I do a lot of this on plan= es and similar, where I have no Internets. I'd like some magic way for = this to integrate (note the "magic" in the previous sentence).

This I don'= ;t know how to fix.


3: I complete the re= view, and then copy and paste the review bits into the Datatracker manually= . Basically I am using=C2=A0Phabricator simply as a stan= d-alone code review tool, without any of the integrations, etc.=C2=A0

This shoul= d actually just work, if you run my tools locally with iphab.py ballot <= whatever>. Have you tried?
=C2=A0


None of these are=C2=A0Phabri= cator's fault, rather a: my not having figured out a work flow yet, and= b: the fact that it isn't really integrated with Datatracker.=C2=A0

I'm also somewhat confused about ho= w multiple people's reviews would interact with each others -- it almos= t feels like each AD having their own separate instance would make more sen= se (but this might be because, until now, we've largely worked separate= ly.=C2=A0
Yeah, basically you just end up with a zillion comments from di= fferent people. I wonder if that's good?


<= /div>
2: some way to autogenerate the ballot for users other than EKR.
=

As above, this sho= uld work now. Can you try?

-Ekr

= 
all seem like they would be great.
W

=C2=A0
I would like to know how easy it would be fo= r Directorates and Review Teams to leverage your work.

Understanding that would, I think, require understa= nding how those tools work. I don't have a real sense of how those tool= s work. I know Tero has some secdir stuff. Does everyone have their own thi= ng?

No.=C2=A0 = The datatracker supports all of the reviews in a manner similar to ballots.= =C2=A0 The reviewer two options.=C2=A0 First, the reviewer puts text into a= frame on a datatracker page, and then the datatracker turns it into email.= =C2=A0 This is very similar to the way IESG ballots are handled.=C2=A0 Seco= nd, the reviewer sends his own email and give the datatracker the URL into = the mail archive.

Your description makes me wonder= if this tooling could work with an API related to the first approach.

Russ

___________________________________________________________
Tools-discuss mailing list
Tools-discuss@i= etf.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

--
I don't t= hink the execution is relevant when it was obviously a bad idea in the firs= t place.
This is like putting rabid weasels in your pants, and later exp= ressing regret at having chosen those particular rabid weasels and that pai= r of pants.
=C2=A0 =C2=A0---maf
--0000000000003743ab056eb08298-- From nobody Fri Jun 15 10:20:16 2018 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 58631124D68 for ; Fri, 15 Jun 2018 10:20:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] 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 oFoO-hbjbA0c for ; Fri, 15 Jun 2018 10:20:09 -0700 (PDT) Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE3FF12F18C for ; Fri, 15 Jun 2018 10:20:09 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 94E65300A46 for ; Fri, 15 Jun 2018 13:20:07 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail.smeinc.net Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id NQz-haPXvMBx for ; Fri, 15 Jun 2018 13:20:06 -0400 (EDT) Received: from a860b60074bd.home (pool-71-127-50-4.washdc.fios.verizon.net [71.127.50.4]) by mail.smeinc.net (Postfix) with ESMTPSA id 09B9E300541; Fri, 15 Jun 2018 13:20:06 -0400 (EDT) From: Russ Housley Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_9745483E-B549-4D3A-94D9-7F128ACF9984" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Date: Fri, 15 Jun 2018 13:20:07 -0400 In-Reply-To: Cc: Tools Discussion To: Eric Rescorla , Warren Kumari References: <3141C32A-E190-4DE8-9E6A-1462EFD0E47B@vigilsec.com> <3EF35561-FCB9-449A-ABC4-8AC936267170@vigilsec.com> X-Mailer: Apple Mail (2.3273) Archived-At: Subject: Re: [Tools-discuss] Reviewing with Phabricator (and Datatracker integration) X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 17:20:14 -0000 --Apple-Mail=_9745483E-B549-4D3A-94D9-7F128ACF9984 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Jun 15, 2018, at 12:13 PM, Eric Rescorla wrote: >=20 > On Wed, Jun 13, 2018 at 3:33 PM, Warren Kumari > wrote: >=20 > On Thu, May 31, 2018 at 4:43 PM Russ Housley > wrote: >=20 >> On May 31, 2018, at 4:27 PM, Eric Rescorla > wrote: >>=20 >> On Thu, May 31, 2018 at 10:30 AM, Russ Housley > wrote: >> I would be interested in the experiences of other ADs. >> I think Warren has spent a little time on it. >=20 >=20 > =E2=80=8BYup, Warren has spent some time on it, and there are some = bits which he loves, and some bits which are less than great. >=20 > The bits which he doesn't like (much of this may be user error): > 1: I'd like there to be an easier way to =E2=80=8Bfind what drafts I = need to review - currently I go to the agenda, find a draft name, and = then search for that in Phabricator. >=20 > This I actually do have some tooling for: the system will = automatically scrape the agenda and assign things for you to review. It = doesn't work perfectly though, because it currently just adds them to = your list and it doesn't run them automatically. The use of the word "scrape" makes me wonder if you are using the JSON = form of the telechat agenda: = http://datatracker.ietf.org/iesg/agenda/agenda.json = Russ --Apple-Mail=_9745483E-B549-4D3A-94D9-7F128ACF9984 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
On Jun 15, 2018, at 12:13 PM, Eric Rescorla <ekr@rtfm.com> = wrote:

On Wed, = Jun 13, 2018 at 3:33 PM, Warren Kumari <warren@kumari.net> wrote:

On Thu, May 31, 2018 at 4:43 PM Russ Housley = <housley@vigilsec.com> wrote:

On May = 31, 2018, at 4:27 PM, Eric Rescorla <ekr@rtfm.com> wrote:

On Thu, May 31, 2018 at 10:30 AM, = Russ Housley <housley@vigilsec.com> wrote:
I would be interested in the = experiences of other ADs.
I think = Warren has spent a little time on = it.

=E2=80=8BYup, Warren = has spent some time on it, and there are some bits which he loves, and = some bits which are less than great.

The bits which he doesn't like (much of this may be user = error):
1: = I'd like there to be an easier way to =E2=80=8Bfind what drafts I need = to review - currently I go to the agenda, find a draft name, and then = search for that in Phabricator.

This I actually do have = some tooling for: the system will automatically scrape the agenda and = assign things for you to review. It doesn't work perfectly though, = because it currently just adds them to your list and it doesn't run them = automatically.

The use of the word "scrape" makes me wonder if you are = using the JSON form of the telechat agenda: http://datatracker.ietf.org/iesg/agenda/agenda.json
Russ

= --Apple-Mail=_9745483E-B549-4D3A-94D9-7F128ACF9984-- From nobody Fri Jun 15 10:22:34 2018 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 18471130E36 for ; Fri, 15 Jun 2018 10:22:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.909 X-Spam-Level: X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] 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 GqTyixnf3pHn for ; Fri, 15 Jun 2018 10:22:30 -0700 (PDT) Received: from mail-ot0-x236.google.com (mail-ot0-x236.google.com [IPv6:2607:f8b0:4003:c0f::236]) (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 1E64212F18C for ; Fri, 15 Jun 2018 10:22:30 -0700 (PDT) Received: by mail-ot0-x236.google.com with SMTP id i19-v6so11783847otk.10 for ; Fri, 15 Jun 2018 10:22:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=C6HF2WXw4l4jAuNjhmUy0aoAev/zqvw1X/397tuIJis=; b=Jv8tqdlT2Vi4NZat+H2pFCAMKbiqrpF6tfDRIR3vklV3uxWokfPpjS2GG9xBnJlQmk F5gZBFCMaJJeb3/ozHueTixeX+pGyz7Awmr5VxRko29xhAM3fTBWdMfqpWDzvk0Xbhhb 7UUjXkAadRt+1XEFP9rzm/nu4ly0qv4GEbZLgpbJVP/aZze2qFezn8E3erXkHITtA0VY ZOHPrYGNWi3gYRjnNUZqav+m33u5mS6ewLOIpGFv4GFEeVP3EU9xMfSBt/XiN09+O3wO lD3WY81hJONvMSjuXwE4/UJSHmT82x49NsWXjroJwpnLiwipwxLtJOt8heKKlAYrfYLr KCyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=C6HF2WXw4l4jAuNjhmUy0aoAev/zqvw1X/397tuIJis=; b=frbh0YRmwDfFK8tNLA1/WoUrHD2nvw0XDL3xN09LDLo/+opRPh9j+SET5toPydN4Dh ufudD7oFwQvDMOw43bL4b4AIwymec5RV8+RKIl3HKg+YfmJ6sKw4ZhDGHHQcPvu0vfQB 7Ej+ze6RK9EVu6XZ0cRMJDNGq1hP+I4f2euObejp2QimHXTLIT/nrBkNPqbtc7dPjNXD SFVOykqaG4NYQ+ra3X3WjA+JSw6G7g0lJiwNiDcf63evVBlT3zYRLX6qU5EiWIPwaFOT Fj7V1q+RPUsIPJ/MVukd3+5QEis3gNKVG1M2/v6SpsfRvnCxvns4r7sV+lJhY4U3vxht LWiw== X-Gm-Message-State: APt69E14L5EQHsQicbbgcqgl0hidBVF0wRfzm6dsdVTtOukZpZr/Agvo zYwj7jJIeeAlvwJmJ5bnGpaAng26dY4RURJOTR3Wx9dZ X-Google-Smtp-Source: ADUXVKJcGIQdgN6S1WqN0U8BfU8ghAqJTCzwKUB864etDVm91nzs9vZ9OulTaQ8U17Hil7r3R+IR40zLZDDO1jzgVmk= X-Received: by 2002:a9d:42b0:: with SMTP id r45-v6mr1748900ote.44.1529083349427; Fri, 15 Jun 2018 10:22:29 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac9:3a8a:0:0:0:0:0 with HTTP; Fri, 15 Jun 2018 10:21:48 -0700 (PDT) In-Reply-To: References: <3141C32A-E190-4DE8-9E6A-1462EFD0E47B@vigilsec.com> <3EF35561-FCB9-449A-ABC4-8AC936267170@vigilsec.com> From: Eric Rescorla Date: Fri, 15 Jun 2018 10:21:48 -0700 Message-ID: To: Russ Housley Cc: Warren Kumari , Tools Discussion Content-Type: multipart/alternative; boundary="000000000000dffbdc056eb17588" Archived-At: Subject: Re: [Tools-discuss] Reviewing with Phabricator (and Datatracker integration) X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 17:22:32 -0000 --000000000000dffbdc056eb17588 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Jun 15, 2018 at 10:20 AM, Russ Housley wrote= : > > On Jun 15, 2018, at 12:13 PM, Eric Rescorla wrote: > > On Wed, Jun 13, 2018 at 3:33 PM, Warren Kumari wrote: > >> >> On Thu, May 31, 2018 at 4:43 PM Russ Housley >> wrote: >> >>> >>> On May 31, 2018, at 4:27 PM, Eric Rescorla wrote: >>> >>> On Thu, May 31, 2018 at 10:30 AM, Russ Housley >>> wrote: >>> >>>> I would be interested in the experiences of other ADs. >>>> >>> I think Warren has spent a little time on it. >>> >>> >> =E2=80=8BYup, Warren has spent some time on it, and there are some bits = which he >> loves, and some bits which are less than great. >> >> The bits which he doesn't like (much of this may be user error): >> 1: I'd like there to be an easier way to =E2=80=8Bfind what drafts I nee= d to >> review - currently I go to the agenda, find a draft name, and then searc= h >> for that in Phabricator. >> > > This I actually do have some tooling for: the system will automatically > scrape the agenda and assign things for you to review. It doesn't work > perfectly though, because it currently just adds them to your list and it > doesn't run them automatically. > > > The use of the word "scrape" makes me wonder if you are using the JSON > form of the telechat agenda: http://datatracker. > ietf.org/iesg/agenda/agenda.json > Yes, I use the JSON form. -Ekr > Russ > > --000000000000dffbdc056eb17588 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, Jun 15, 2018 at 10:20 AM, Russ Housley <housley@vigilsec.co= m> wrote:

On Jun 15, 2018, at 12:13 PM, Eric Rescorla <ekr@rtfm.com> wrote:

On Wed, Jun 1= 3, 2018 at 3:33 PM, Warren Kumari <warren@kumari.net> wrote:=

On Thu, May 31, 2018 at 4:43 PM Russ Housley <housley@vigilsec.com> wrote= :

On May 31, 2018, at 4:27 PM, Eri= c Rescorla <ekr@rtfm.c= om> wrote:
On Thu, May 31, 2018 at 10:30 AM, Russ Housley = <housley@vigilsec.com> wrote:
I would be interested in the = experiences of other ADs.
I think Warren has spent a= little time on it.
<= /blockquote>

=E2=80=8BYup, Warren has spent some time on it, and there are som= e bits which he loves, and some bits which are less than great.

The bits which he doesn't like (much of this may b= e user error):
1: I'= d like there to be an easier way to =E2=80=8Bfind what drafts I need to rev= iew - currently I go to the agenda, find a draft name, and then search for = that in=C2=A0Phabricator.
=

This I actually do have some tooling for: = the system will automatically scrape the agenda and assign things for you t= o review. It doesn't work perfectly though, because it currently just a= dds them to your list and it doesn't run them automatically.

The use of the word &= quot;scrape" makes me wonder if you are using the JSON form of the tel= echat agenda:=C2=A0http://datatracker.ietf.org/iesg/agenda/agen= da.json

Yes, I use the= JSON form.

-Ekr


Russ


--000000000000dffbdc056eb17588-- From nobody Fri Jun 15 10:57:04 2018 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 7E613130E36 for ; Fri, 15 Jun 2018 10:57:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.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 T7aaNDquv--B for ; Fri, 15 Jun 2018 10:56:58 -0700 (PDT) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (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 9DFFB124D68 for ; Fri, 15 Jun 2018 10:56:57 -0700 (PDT) Received: by mail-wm0-x22f.google.com with SMTP id p126-v6so4809193wmb.2 for ; Fri, 15 Jun 2018 10:56:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qwAbe2i9qn6eKNcFyw1asvkm8Wf/bJmXSUUW8XvUm1Q=; b=RtY4HsMR8hNeOO1CKqXrMrDO/iLWVJq0bK0nW6CZuSE1k6BVPnyhlH+UQ8jAqd37Jj nFjRs05x5s9pRDigJmeWmMKcM5M+cmVNKZnr3stHd5DM/pa3SOAYA+mRqfievB6LFdSA 6Sv9M556+M4lKIR/5lWPanfQ6TaWgIFxhSUBLLyuZzbRS48EfPwX7rAOuj7Nf/QkYi6C sopsnI6AnYt8xXcS4W3ezOC5oF7QcG76G67d8hPfuEZqJ5ElN5wbJpEEeCGqAN84OmRg 0Hgfou6LXLi8OZksHZ1oXlIdKPhgThfMFneorJ7e+/EETHvY66amjFjuUErgSjCaRDcQ W6mg== 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=qwAbe2i9qn6eKNcFyw1asvkm8Wf/bJmXSUUW8XvUm1Q=; b=alhc6sHZ2cr+BZ70wyOVjnDFkNUFnxHRGd6T8qecBfK6zMxpe/AK8gbFbQAKh61mKZ CCoHTAISnyZ2dGdMtMJZJ+33F0urpSiCeQlBjPTFacu5bIRUoyHgCGKVpeLoRlDzOB9S 9bHCclm+R3iJTAxUK6L+BRZfuVzGPqSNOiYpCR4IuHFaa29qU3QnRgaIt9cEbKNjyZ10 AUYrBq2aCSrJdfB1B93nNDLzLwMX90Swao1pbC252dF57v8wTmNw22BkNPy+eVrhjlKX rcU2mwyuotGGV77i8NkoFZxzGlkYSCZTDG8Ze5sU/ladGGGqmjBhnkuRlQtWdCz0JogW 53CQ== X-Gm-Message-State: APt69E2wljJKdnEutx/sdpN0KncIoz6UBhqIFKYEybsX1ndAbmiVtzKw fGYb4D/NE4iOOL6SFgSoU2r3GjttK8ojc7Rt9DGl2lpSqDE= X-Google-Smtp-Source: ADUXVKK1IB6bk1IE/AsqL5T5byfRDiQKX8fDjEnnvjRgk7qGlGSf9JUiAga9e3WIF1iZtZRh5Co4Ih0GPZIZi7kBsT8= X-Received: by 2002:a1c:4189:: with SMTP id o131-v6mr1878964wma.7.1529085415750; Fri, 15 Jun 2018 10:56:55 -0700 (PDT) MIME-Version: 1.0 References: <3141C32A-E190-4DE8-9E6A-1462EFD0E47B@vigilsec.com> <3EF35561-FCB9-449A-ABC4-8AC936267170@vigilsec.com> In-Reply-To: From: Warren Kumari Date: Fri, 15 Jun 2018 13:56:18 -0400 Message-ID: To: Eric Rescorla Cc: Russ Housley , Tools Discussion Content-Type: multipart/alternative; boundary="0000000000000996b0056eb1f175" Archived-At: Subject: Re: [Tools-discuss] Reviewing with Phabricator (and Datatracker integration) X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 17:57:02 -0000 --0000000000000996b0056eb1f175 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Jun 15, 2018 at 12:14 PM Eric Rescorla wrote: > > > On Wed, Jun 13, 2018 at 3:33 PM, Warren Kumari wrote: > >> >> >> On Thu, May 31, 2018 at 4:43 PM Russ Housley >> wrote: >> >>> >>> On May 31, 2018, at 4:27 PM, Eric Rescorla wrote: >>> >>> On Thu, May 31, 2018 at 10:30 AM, Russ Housley >>> wrote: >>> >>>> I would be interested in the experiences of other ADs. >>>> >>> >>> I think Warren has spent a little time on it. >>> >>> >>> >> =E2=80=8BYup, Warren has spent some time on it, and there are some bits = which he >> loves, and some bits which are less than great. >> >> The bits which he doesn't like (much of this may be user error): >> 1: I'd like there to be an easier way to =E2=80=8Bfind what drafts I nee= d to >> review - currently I go to the agenda, find a draft name, and then searc= h >> for that in Phabricator. >> > > This I actually do have some tooling for: the system will automatically > scrape the agenda and assign things for you to review. It doesn't work > perfectly though, because it currently just adds them to your list and it > doesn't run them automatically. > > > > 2: I do my reviews on an iPad, reading and annotating (using GoodReader) >> the PDFs. This is partly because I like the layout / ease of annotation, >> but also because I do a lot of this on planes and similar, where I have = no >> Internets. I'd like some magic way for this to integrate (note the "magi= c" >> in the previous sentence). >> > > This I don't know how to fix. > > > 3: I complete the review, and then copy and paste the review bits into th= e >> Datatracker manually. Basically I am using Phabricator simply as a >> stand-alone code review tool, without any of the integrations, etc. >> > > This should actually just work, if you run my tools locally with iphab.py > ballot . Have you tried? > =E2=80=8BNope. So far all I've been doing is using the https://mozphab-ietf.devsvcdev.mozaws.net/ instance, and have not yet tried any of your tools -- they sound like they accomplish much of what I'm looking for. W > > > > None of these are Phabricator's fault, rather a: my not having figured >> out a work flow yet, and b: the fact that it isn't really integrated wit= h >> Datatracker. >> >> I'm also somewhat confused about how multiple people's reviews would >> interact with each others -- it almost feels like each AD having their o= wn >> separate instance would make more sense (but this might be because, unti= l >> now, we've largely worked separately. >> > > Yeah, basically you just end up with a zillion comments from different > people. I wonder if that's good? > > > > 2: some way to autogenerate the ballot for users other than EKR. >> >> > As above, this should work now. Can you try? > > -Ekr > > 3: encouraging people to use this instead of the current only emil system >> >> all seem like they would be great. >> >> W >> >> >> >> >>> I would like to know how easy it would be for Directorates and Review >>>> Teams to leverage your work. >>>> >>> >>> Understanding that would, I think, require understanding how those tool= s >>> work. I don't have a real sense of how those tools work. I know Tero ha= s >>> some secdir stuff. Does everyone have their own thing? >>> >>> >>> No. The datatracker supports all of the reviews in a manner similar to >>> ballots. The reviewer two options. First, the reviewer puts text into= a >>> frame on a datatracker page, and then the datatracker turns it into ema= il. >>> This is very similar to the way IESG ballots are handled. Second, the >>> reviewer sends his own email and give the datatracker the URL into the = mail >>> archive. >>> >>> Your description makes me wonder if this tooling could work with an API >>> related to the first approach. >>> >>> Russ >>> >>> ___________________________________________________________ >>> 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 >>> >> >> >> -- >> I don't think the execution is relevant when it was obviously a bad idea >> in the first place. >> This is like putting rabid weasels in your pants, and later expressing >> regret at having chosen those particular rabid weasels and that pair of >> pants. >> ---maf >> > > --=20 I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf --0000000000000996b0056eb1f175 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fr= i, Jun 15, 2018 at 12:14 PM Eric Rescorla <ekr@rtfm.com> wrote:


= On Wed, Jun 13, 2018 at 3:33 PM, Warren Kumari <warren@kumari.net><= /span> wrote:


On Thu, May 31, 2018 at 4:43 PM Russ Housley <<= a href=3D"mailto:housley@vigilsec.com" target=3D"_blank">housley@vigilsec.c= om> wrote:

On May 31, 2018,= at 4:27 PM, Eric Rescorla <ekr@rtfm.com> wrote:

On Thu, May 31, 2018 at 10:30 A= M, Russ Housley <housley@vigilsec.com> wrote:
I would be in= terested in the experiences of other ADs.

=
I think Warren has spent a little time on it.



=E2= =80=8BYup, Warren has spent some time on it, and there are some bits which = he loves, and some bits which are less than great.

The bits which he doesn't like (much of this may be user error)= :
1: I'd like there = to be an easier way to =E2=80=8Bfind what drafts I need to review - current= ly I go to the agenda, find a draft name, and then search for that in=C2=A0= Phabricator.
=

This I actually do have some tooling for: the system wi= ll automatically scrape the agenda and assign things for you to review. It = doesn't work perfectly though, because it currently just adds them to y= our list and it doesn't run them automatically.
=C2=A0
<= div>

2: I do my reviews on an iPad, reading and annotati= ng (using GoodReader) the PDFs. This is partly because I like the layout / = ease of annotation, but also because I do a lot of this on planes and simil= ar, where I have no Internets. I'd like some magic way for this to inte= grate (note the "magic" in the previous sentence).

This I don't know how = to fix.


=
3: I complete the review, and then c= opy and paste the review bits into the Datatracker manually. Basically I am= using=C2=A0Phabricator simply as a stand-alone code rev= iew tool, without any of the integrations, etc.=C2=A0

This should actually just = work, if you run my tools locally with iphab.py ballot <whatever>. Ha= ve you tried?

<= br>
=E2=80=8BNope. So far all I've been doing is using the=C2=A0=C2=A0https://mozphab-ietf.devsv= cdev.mozaws.net/=C2=A0instance, and have not yet tried any of your tool= s -- they sound like they accomplish much of what I'm looking for.



W
=C2=A0
=C2=A0


None o= f these are=C2=A0Phabricator's fault, rather a: my n= ot having figured out a work flow yet, and b: the fact that it isn't re= ally integrated with Datatracker.=C2=A0
=
I'm also somewhat confused about how multiple people's reviews w= ould interact with each others -- it almost feels like each AD having their= own separate instance would make more sense (but this might be because, un= til now, we've largely worked separately.=C2=A0

Yeah, basically you j= ust end up with a zillion comments from different people. I wonder if that&= #39;s good?



2: some way to autogenerate =
the ballot for users other than EKR.

As above, this should work now. Can you try?

-Ekr

3: encouraging people to use th=
is instead of the current only emil system 
all se=
em like they would be great.
W

=C2=A0
I would like to= know how easy it would be for Directorates and Review Teams to leverage yo= ur work.

Understanding that wou= ld, I think, require understanding how those tools work. I don't have a= real sense of how those tools work. I know Tero has some secdir stuff. Doe= s everyone have their own thing?

No.=C2=A0 The datatracker supports all of the reviews in= a manner similar to ballots.=C2=A0 The reviewer two options.=C2=A0 First, = the reviewer puts text into a frame on a datatracker page, and then the dat= atracker turns it into email.=C2=A0 This is very similar to the way IESG ba= llots are handled.=C2=A0 Second, the reviewer sends his own email and give = the datatracker the URL into the mail archive.

You= r description makes me wonder if this tooling could work with an API relate= d to the first approach.

Russ

=
________________________________________________________= ___
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


--
I don't think the execution is relevant wh= en it was obviously a bad idea in the first place.
This is like putting = rabid weasels in your pants, and later expressing regret at having chosen t= hose particular rabid weasels and that pair of pants.
=C2=A0 =C2=A0---ma= f



--
I don't t= hink the execution is relevant when it was obviously a bad idea in the firs= t place.
This is like putting rabid weasels in your pants, and later exp= ressing regret at having chosen those particular rabid weasels and that pai= r of pants.
=C2=A0 =C2=A0---maf
--0000000000000996b0056eb1f175-- From nobody Mon Jun 18 13:47:03 2018 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 5349B130E22 for ; Mon, 18 Jun 2018 13:47:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 l2Y5ASgNyX6S for ; Mon, 18 Jun 2018 13:46:58 -0700 (PDT) Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C65FD1277BB for ; Mon, 18 Jun 2018 13:46:58 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id B79EA300A03 for ; Mon, 18 Jun 2018 16:46:56 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail.smeinc.net Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id gAnDo8dpQAve for ; Mon, 18 Jun 2018 16:46:55 -0400 (EDT) Received: from a860b60074bd.home (pool-71-127-50-4.washdc.fios.verizon.net [71.127.50.4]) by mail.smeinc.net (Postfix) with ESMTPSA id BD547300250 for ; Mon, 18 Jun 2018 16:46:55 -0400 (EDT) From: Russ Housley Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Message-Id: <7C9480FF-B1EC-47C9-9D88-E87ECD6A9493@vigilsec.com> Date: Mon, 18 Jun 2018 16:46:56 -0400 To: Tools Discussion X-Mailer: Apple Mail (2.3273) Archived-At: Subject: [Tools-discuss] rfcdiff with inputs that have long lines X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2018 20:47:01 -0000 On the tao-discuss mail list, we have been talking about a proposed = update to the Tao of the IETF. Since the Tao is now published as a = webpage (https://www.ietf.org/tao/), the proposed new text was provided = in a file with long lines. By wrapping the lines at 72 character, the rfcdiff tool then provides a = useful output. How hard would it be to have = https://www.ietf.org/tools/rfcdiff/ do that automatically? Perhaps it = could count the number of lines greater that 80, and if there are many, = wrap the lines and then run the diff. Russ From nobody Wed Jun 20 05:21:44 2018 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 2B7AE1310AC for ; Wed, 20 Jun 2018 05:21:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 yQ9oqozybuv9 for ; Wed, 20 Jun 2018 05:21:41 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C806B1310A9 for ; Wed, 20 Jun 2018 05:21:41 -0700 (PDT) Received: from h-99-61.a357.priv.bahnhof.se ([82.196.99.61]:64512 helo=[192.168.1.120]) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1fVc7I-000436-To; Wed, 20 Jun 2018 05:21:41 -0700 To: Russ Housley , Tools Discussion References: <7C9480FF-B1EC-47C9-9D88-E87ECD6A9493@vigilsec.com> From: Henrik Levkowetz Message-ID: <81c09d2b-c9d5-8c9e-9e11-7c3eb47b822f@levkowetz.com> Date: Wed, 20 Jun 2018 14:21:33 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <7C9480FF-B1EC-47C9-9D88-E87ECD6A9493@vigilsec.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 82.196.99.61 X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, housley@vigilsec.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org) X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [Tools-discuss] rfcdiff with inputs that have long lines X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2018 12:21:43 -0000 Hi Russ, On 2018-06-18 22:46, Russ Housley wrote: > On the tao-discuss mail list, we have been talking about a proposed > update to the Tao of the IETF. Since the Tao is now published as a > webpage (https://www.ietf.org/tao/), the proposed new text was > provided in a file with long lines. > > By wrapping the lines at 72 character, the rfcdiff tool then provides > a useful output. How hard would it be to have > https://www.ietf.org/tools/rfcdiff/ do that automatically? Perhaps it > could count the number of lines greater that 80, and if there are > many, wrap the lines and then run the diff. Not that hard. I should be able to have a new release available later today. Best regards, Henrik > > Russ > > ___________________________________________________________ > 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 > From nobody Wed Jun 20 05:32:14 2018 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 C92D6130E6A for ; Wed, 20 Jun 2018 05:32:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 2LYxKpEnV1SQ for ; Wed, 20 Jun 2018 05:32:10 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07959130E43 for ; Wed, 20 Jun 2018 05:32:08 -0700 (PDT) Received: from [192.168.178.20] ([93.217.75.252]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MKHtm-1fWAmF2rHa-001igX; Wed, 20 Jun 2018 14:32:01 +0200 To: Russ Housley , Tools Discussion References: <7C9480FF-B1EC-47C9-9D88-E87ECD6A9493@vigilsec.com> From: Julian Reschke Message-ID: <98a404af-1431-8fc2-96f1-ba3fad80a0e1@gmx.de> Date: Wed, 20 Jun 2018 14:31:57 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <7C9480FF-B1EC-47C9-9D88-E87ECD6A9493@vigilsec.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:7gCCiIr0ctUaBmm6/gHQZUDhRwpnP6jcTZeoNOZzp8Zk+3a5iC0 Hvo0Y+8emamaosyl4z2T9kOymuMc5obCDrA8VQ6YyTVEHW85jGLen5/iO6d9nASZWoQwlLE kiSFlw7AgFFRX4PWSRUQyWPPooJLbIzSM989cIB3F5Ic4BO+rSS9oEe4HTAm+mSes4tco1E po5EcEeQb7nULNto+dr/w== X-UI-Out-Filterresults: notjunk:1;V01:K0:XIImPX3ZiFY=:o3rjeWMCFPy2OMAEuRblGx YooVoSYkUvLZ7ZyqAjhNeKRT7EWBY71CDTnnjQeKzWFOXL2/VKXfEPjKAUQoLJI4CqtfbZ45j koQaFVoOJdLT6nu/PZj+rrhjWkib4syDf3bWOfnb9U1XBJEkqrYgSsTo05iC8oB4hjR8slG7j ZFBLJaC+wgDylWO4aqK2Iq1KWl/KZYQYJcsPw91y7PYxg8pGyhtqVT0ea/vjYr3MRdv/NDwWM TG0NiGg980fivxppRRPwF/sPGlJeJooKvKJVMPCCvLY5LPmaAEvQg6idoNhXcIywXtH3c397R 2OhrKcDvzIBPBlADgEnRsTTlUl8FtSHK14tifogIABi7wKoZ06gD8Kb/M7DqZcF+fnpbf6nxU XkqWpQMt+7J0i7bIt8oM+A3k5sBsQ8UODeUGrbu/jYvNkaTqkX3IA+3MbVISMQoECwVBOl7rt ydSsqMLSv/Bvc4oMUzy9VHevq1UsXZnUeQvzxZyhD0MjX3pElNPKg0yjK3FS99fsC9PulF23e pWhYwHRVGx2G9XMJjc12W6/Rhhi4DLq8tTsxcNKqfqG5h7m1VIxcEniVawiBVlqPcOm/EntQb GahPfJgdpsz7aHMl7Kq7mMnKZFnkU6OUFJDrHVyodGoYOPdbgloNwh2B3I2gCPjEmzy6FF78Y RV6VGUKPH3amfRJdyoqj6sZa6w3RbXGMjiV2ZcMIJReBQC+Wa9PNC3nn8YvHN8DGyX5vEEpEB cuejawRXt0mJrC33CLB9gqk7y0J3iF+QlfZ0kjCKjr1C3L5KfrxcGMBo8ltGM9Ml5bEl/XupH uycPoLH Archived-At: Subject: Re: [Tools-discuss] rfcdiff with inputs that have long lines X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2018 12:32:12 -0000 On 2018-06-18 22:46, Russ Housley wrote: > On the tao-discuss mail list, we have been talking about a proposed update to the Tao of the IETF. Since the Tao is now published as a webpage (https://www.ietf.org/tao/), the proposed new text was provided in a file with long lines. > ... It escapes me why we don't produce documents like these with the same tool set we publish technical documents with... Best regards, Julian From nobody Wed Jun 20 05:55:09 2018 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 C1ADF130E6D for ; Wed, 20 Jun 2018 05:55:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 IFhMwGLI6SOp for ; Wed, 20 Jun 2018 05:55:02 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6438A130E6C for ; Wed, 20 Jun 2018 05:55:02 -0700 (PDT) Received: from [192.168.178.20] ([93.217.75.252]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MPm54-1fZUG0210U-0053BH; Wed, 20 Jun 2018 14:54:58 +0200 From: Julian Reschke To: Russ Housley , Tools Discussion References: <7C9480FF-B1EC-47C9-9D88-E87ECD6A9493@vigilsec.com> <98a404af-1431-8fc2-96f1-ba3fad80a0e1@gmx.de> Message-ID: Date: Wed, 20 Jun 2018 14:54:55 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <98a404af-1431-8fc2-96f1-ba3fad80a0e1@gmx.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K1:xU6PpG5tRpNcSCfXQYW3Zj7/pw/8ODe2iJNrsr7ZeXPlzK7tmCk 1Yo9zlGsAtmiVTcsLG4K+7XrfZXtay9mzneL46j1c7urYGjMycd439o0cB2/S6UKysxZql3 tAN0A5UR6LzSD0oanWFV/fFfkZ2/7b4K6/xSxh+hM5dTwFM873TkMzd0cEeqXRW05RUbHjw 4PfSK+WbULscjo52mGPKA== X-UI-Out-Filterresults: notjunk:1;V01:K0:W0exXTw9oag=:NqjLngmSfJdRr/aBonTwhe EPfIPyt78SDBTDKqNSNLTvw8nIgkUYodV/bzcThQV98aaUAZH/Hr2Mw6OF5pnuofDpltUPryj ckN+Vz1f1+OgmsczvlAGK8yl4VAwJlhPaZX1y1Ox2fc245aoY1ej04TbLmL4UsAumRy4CSHWO oM6QSA5ElFrQNgYf6NUFf62wCtTOPXpn1nVV64FDwdY59uL2KyS92uVaycZtFokVicKrYccYT cwWWLDOiBO4cefbOp4wcir6j65IDBeoTE+wI8HjrDyhki4DmCUxQaiho+uzepV5sQg1+HOeBz v+Rtlz/SmaUxpc17R8ADG6evlPLKf2X1H0rHF1L5F9JNvQQeQ/X5OTTLNsRZwA/wkwj7SpEFT QH6zw7YTOM9f+VWWpMFJbvgKmFiVkXrhObOjPIWI9SpgQhL8mWFO4irh7zFT5zxnIS4Rty22/ GMA2R8jXXnZIh6OIOsLHch35d7AGBpxKoHbqV7V4hCyz5fAt+oM132EXIYY2agFvvVTQ+nEYq 0cbI4ADJJkCUk7RVxNMJ1LKDGNtezF1AJ7Z0U32b64/5oW57lzS2pAXOZh9Zv1rj4m4opiWkP kch2OD8AyZ6+kVSnkUc3X1JhSXVnf3/3xvj+fCX44n3xxNCI06P2DJTWNsAPfqCGnIHmaMWUk uHnKxCeo5Fh4KRz/K2WrAJKg35ahbj86aq86/6vrG1zzsXfldF2y0lmMX4ZX9Ma/XNdsCBEDf Bq14ZTec/S9I8uSc9eQsht/LycL/J7RMpcQekuktM/Cl8y8ZHI1F+UsvC8wBSLj4kga1SpkJ3 KzArNR7 Archived-At: Subject: Re: [Tools-discuss] rfcdiff with inputs that have long lines X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2018 12:55:05 -0000 On 2018-06-20 14:31, Julian Reschke wrote: > On 2018-06-18 22:46, Russ Housley wrote: >> On the tao-discuss mail list, we have been talking about a proposed >> update to the Tao of the IETF.  Since the Tao is now published as a >> webpage (https://www.ietf.org/tao/), the proposed new text was >> provided in a file with long lines. >> ... > > It escapes me why we don't produce documents like these with the same > tool set we publish technical documents with... > ... As a matter of fact, earlier versions of the document *have* been produced with xml2rfc. So IMHO the best way to proceed would be to diff and maintain that source file... (or, as a matter of fact, to rfcdiff the plain text output). Best regards, Julian From nobody Wed Jun 20 07:27:19 2018 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 BFDE8130E90 for ; Wed, 20 Jun 2018 07:27:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 RwE9Xtes7Llt for ; Wed, 20 Jun 2018 07:27:13 -0700 (PDT) Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E687130DE2 for ; Wed, 20 Jun 2018 07:27:13 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 21D0F300A08 for ; Wed, 20 Jun 2018 10:27:11 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail.smeinc.net Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 99AKHhDTZDyF for ; Wed, 20 Jun 2018 10:27:09 -0400 (EDT) Received: from a860b60074bd.home (pool-71-127-50-4.washdc.fios.verizon.net [71.127.50.4]) by mail.smeinc.net (Postfix) with ESMTPSA id 7E3A03004B7; Wed, 20 Jun 2018 10:27:09 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) From: Russ Housley In-Reply-To: Date: Wed, 20 Jun 2018 10:27:10 -0400 Cc: Tools Discussion Content-Transfer-Encoding: quoted-printable Message-Id: References: <7C9480FF-B1EC-47C9-9D88-E87ECD6A9493@vigilsec.com> <98a404af-1431-8fc2-96f1-ba3fad80a0e1@gmx.de> To: Julian Reschke X-Mailer: Apple Mail (2.3445.8.2) Archived-At: Subject: Re: [Tools-discuss] rfcdiff with inputs that have long lines X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2018 14:27:16 -0000 > On Jun 20, 2018, at 8:54 AM, Julian Reschke = wrote: >=20 > On 2018-06-20 14:31, Julian Reschke wrote: >> On 2018-06-18 22:46, Russ Housley wrote: >>> On the tao-discuss mail list, we have been talking about a proposed = update to the Tao of the IETF. Since the Tao is now published as a = webpage (https://www.ietf.org/tao/), the proposed new text was provided = in a file with long lines. >>> ... >> It escapes me why we don't produce documents like these with the same = tool set we publish technical documents with... >> ... >=20 > As a matter of fact, earlier versions of the document *have* been = produced with xml2rfc. So IMHO the best way to proceed would be to diff = and maintain that source file... (or, as a matter of fact, to rfcdiff = the plain text output). An author or editor could do so. In fact, there are several pages that = the IESG maintains that do exactly that. That said, this is not a = requirement that we impose on them. Russ From nobody Wed Jun 20 10:07:59 2018 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 BCF56130DC0 for ; Wed, 20 Jun 2018 10:07:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 ENL0wlpe435B for ; Wed, 20 Jun 2018 10:07:57 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 183CB12F1A2 for ; Wed, 20 Jun 2018 10:07:57 -0700 (PDT) Received: from h-99-61.a357.priv.bahnhof.se ([82.196.99.61]:49790 helo=[192.168.1.120]) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1fVgaJ-0003rk-Ok; Wed, 20 Jun 2018 10:07:56 -0700 To: Russ Housley , Tools Discussion References: <7C9480FF-B1EC-47C9-9D88-E87ECD6A9493@vigilsec.com> <81c09d2b-c9d5-8c9e-9e11-7c3eb47b822f@levkowetz.com> From: Henrik Levkowetz Message-ID: <864c9d5a-4690-99c1-bdd9-15b60dc980f0@levkowetz.com> Date: Wed, 20 Jun 2018 19:07:48 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <81c09d2b-c9d5-8c9e-9e11-7c3eb47b822f@levkowetz.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 82.196.99.61 X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, housley@vigilsec.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org) X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [Tools-discuss] rfcdiff with inputs that have long lines X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2018 17:07:59 -0000 On 2018-06-20 14:21, Henrik Levkowetz wrote: > Hi Russ, > > On 2018-06-18 22:46, Russ Housley wrote: >> On the tao-discuss mail list, we have been talking about a proposed >> update to the Tao of the IETF. Since the Tao is now published as a >> webpage (https://www.ietf.org/tao/), the proposed new text was >> provided in a file with long lines. >> >> By wrapping the lines at 72 character, the rfcdiff tool then provides >> a useful output. How hard would it be to have >> https://www.ietf.org/tools/rfcdiff/ do that automatically? Perhaps it >> could count the number of lines greater that 80, and if there are >> many, wrap the lines and then run the diff. > > Not that hard. I should be able to have a new release available later today. A new version is available here: https://tools.ietf.org/rfcdiff If you add the desired fold column in the fold lines form field, you'll get line folding before diffing. You can also use a query parameter, if constructing the url by hand, by adding this: "&--fold=80" The new version will be available on the https://www.ietf.org/tools/rfcdiff/ page when installed by the secretariat. Henrik From nobody Wed Jun 20 13:51:32 2018 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 3DF5E130EBF for ; Wed, 20 Jun 2018 13:51:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yrv8fVv_nlmH for ; Wed, 20 Jun 2018 13:51:28 -0700 (PDT) Received: from mail-pl0-x22e.google.com (mail-pl0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) (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 BE9BC130E1B for ; Wed, 20 Jun 2018 13:51:28 -0700 (PDT) Received: by mail-pl0-x22e.google.com with SMTP id t12-v6so407348plo.7 for ; Wed, 20 Jun 2018 13:51:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=9Fj/otFHJ1lq/wiS70TyENe8GaOlV2VyoLhpnBefkZE=; b=WOFbIaAFLYLFM3QMMHyJUG5ARdvxENL2OJ6D7TGTyIbV59V5TuwFvh3B8Jyii2OJ8I D+QoGPfdyTVdRngTq0E2s2R7HP3agZ69B5a5R0AIrPxQCPDdS2NzKF9U47ha5x4gt9+Z Y0cZTgrpvXRf6VSTVsFw2+LaEg05vHOaVjPgZOK/nmFhKDpwTdkRoSdSGMr7mlmo+C16 +ElAfO4UUnlUqnLAJFFK9YYp15W10ZduFC/YD55ysP7+A4lvp5HBaH+g73TdiM+FFFAS mBllMUb2BFI0rYWOlYa8D2YI0Ti8aeNA/P4QE8dtF4J1YmeL+B4LtL0fLxBsEmwNUIhs WfEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=9Fj/otFHJ1lq/wiS70TyENe8GaOlV2VyoLhpnBefkZE=; b=tXB577GPZXqFpUqvEwIRNYwpRd9m91BcpWsXTUj+vRdOJ2ib3KBAL9CmH8p0vp9OXT p0VXrEvTniHDDaREXrf79glyo44l182m22ChOml0D0TBLcHbEwv9CiBzoMP+nWfrWq8o /o5eo8ma0qfP0A0x8neDIgN0ZFCvnwEIN7eiqhGz7o3yt7ak0dMsB/Ce4oYklYBnvIkQ MwTlmY8xZGHFfVI3l3xUS0uOCTvPRMtWvIx7uJ1NOhkCA/VksVxSOkO/nc80capVE3Zu zuLuqsVc/V/1hNIoiMKKRUuZj6as3snJ1auQxaqYy2VekrlHvQo/ImekzitCcePeaUl2 KX3Q== X-Gm-Message-State: APt69E0YufqgOLb+TZN60nGJ9QWb6dhmY/aEyJTBpunv32XYLkLDjJ0P 2EBm03MtnhXl4sQsuEyfLEoqkw== X-Google-Smtp-Source: ADUXVKJ6xRe1f825R68F1lnPWANNpQV0HPJf6U/pD61ZgF4rW71rvs18IXBF1w1/Te0qRNgF+YfZnQ== X-Received: by 2002:a17:902:48c8:: with SMTP id u8-v6mr25380046plh.152.1529527888133; Wed, 20 Jun 2018 13:51:28 -0700 (PDT) Received: from [192.168.178.21] ([118.148.121.80]) by smtp.gmail.com with ESMTPSA id u84-v6sm5761545pfg.156.2018.06.20.13.51.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Jun 2018 13:51:27 -0700 (PDT) To: Julian Reschke , Russ Housley , Tools Discussion References: <7C9480FF-B1EC-47C9-9D88-E87ECD6A9493@vigilsec.com> <98a404af-1431-8fc2-96f1-ba3fad80a0e1@gmx.de> From: Brian E Carpenter Message-ID: <32b771d1-4414-6000-66f8-3faa96890956@gmail.com> Date: Thu, 21 Jun 2018 08:51:30 +1200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <98a404af-1431-8fc2-96f1-ba3fad80a0e1@gmx.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Tools-discuss] rfcdiff with inputs that have long lines X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2018 20:51:31 -0000 On 21/06/2018 00:31, Julian Reschke wrote: > On 2018-06-18 22:46, Russ Housley wrote: >> On the tao-discuss mail list, we have been talking about a proposed update to the Tao of the IETF. Since the Tao is now published as a webpage (https://www.ietf.org/tao/), the proposed new text was provided in a file with long lines. >> ... > > It escapes me why we don't produce documents like these with the same > tool set we publish technical documents with... It's a lot harder with the new website's content management system and the new look and feel. For example, http://www6.ietf.org/about/process-docs.html was done with xml2rfc and a little manual tweaking, but that simply wouldn't carry over to https://www.ietf.org/about/participate/get-started/ Brian From nobody Wed Jun 20 18:12:25 2018 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 6348B130DBE for ; Wed, 20 Jun 2018 18:12:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_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 MCH8FtxCNI6Y for ; Wed, 20 Jun 2018 18:12:22 -0700 (PDT) Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (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 53808130EE6 for ; Wed, 20 Jun 2018 18:12:22 -0700 (PDT) Received: by mail-oi0-x22c.google.com with SMTP id c128-v6so1358336oig.11 for ; Wed, 20 Jun 2018 18:12:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Zlok3AVTjNwpyAPs1/sVsxaxbV//1u33doY5BL8lO9k=; b=jpCAg950WTswU4d98AzpEFoSWV0HHKsTtL9c8xjcwGdn9Wzo5ONEsm5SWtv99sEkzD iWNyyxZMg8r0g40ze0s/R7OdkPh4sXdiY59ZWQZWOZWJonOmYysOJNkTbIhRvZuOpePK 5RMVDnIsp6fPpq9/SVRqr7NzdZ5FgyZLdsB2y9dDmSMzglgjpYeINpuxBK02QGaGGc0h FRSXBoMuQu2dQaWqmjA4UYrAt5W3ZM4eH5u2ddj7CJMoCFaF/bjzHNI9ZIsskh4gr4k+ tPC4RoENaJOJQCveZ/KQJI6kQysyAUp59O+bN9ZG4aApWPmxDYF3B3xZDKGHzO2w2KEu eJZw== 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=Zlok3AVTjNwpyAPs1/sVsxaxbV//1u33doY5BL8lO9k=; b=NwtfeRaal/qbJgWLShbGdaUAEqQU+Xi0UoWxs4xqx70qK/Ak+HRxf+rqNy1wooZAZj bTRy+2nOkUjvmVcMSIMLaSQgdAVFqJn4bf7cSDy9yvppRwOyvYRYpFAaNS8raixOVxyC XP1JDz36iAd3wF7rW9gIvYih9JEEqOLfBVE0XMdv8Y2XflN1un7r2Cb8hChcfOpKLMff UNu3oMZog/KBpmVa/ZZgoGJFUzztUDyldvxNpQKtmGS++K785UDdI0G3/SNYv4b0JTJY Nk32kHZUMjWmF3vgAVXLEkT2Jz4T6HTIO1vQwgp9cW0CuoyLwaAS/NWOhbm62R9GHprj FY0g== X-Gm-Message-State: APt69E2pKnvKBL+iAM8ANiOKWkQJJh4Rl7MFHJKWNGP0e9DU1+5yFHRh Xp9/XKI/B7wHujw34gfBW9dSRsRVdQccjCfZaXlq99bD X-Google-Smtp-Source: ADUXVKKYp+T08tYfHpcn8GBnKGxzbYHToCpH2Itee8q+T3BcdnR+pZN2CDFTgTsVM1Wy92l7elRz7NfJpk3Iehuc2ek= X-Received: by 2002:aca:3954:: with SMTP id g81-v6mr14037875oia.215.1529543541236; Wed, 20 Jun 2018 18:12:21 -0700 (PDT) MIME-Version: 1.0 From: Martin Thomson Date: Thu, 21 Jun 2018 11:12:10 +1000 Message-ID: To: "tools-discuss@ietf.org Discussion" Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [Tools-discuss] STD series in bibxml X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2018 01:12:25 -0000 Not all RFCs that are in the STD subseries include the proper label. See for example STD 2/RFC 1700: https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.1700.xml From nobody Wed Jun 20 19:09:13 2018 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 CDC37130FD0 for ; Wed, 20 Jun 2018 19:09:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_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 qGZOfxPPPLis for ; Wed, 20 Jun 2018 19:09:09 -0700 (PDT) Received: from mail-pl0-x22e.google.com (mail-pl0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) (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 A7C8A130E54 for ; Wed, 20 Jun 2018 19:09:09 -0700 (PDT) Received: by mail-pl0-x22e.google.com with SMTP id 6-v6so782426plb.0 for ; Wed, 20 Jun 2018 19:09:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=fzxH4Jeii/asXH8ywHSGuzMBtbm/v6vTdU5ti7Qk53Y=; b=iPPFKl6U6KUK6+Zt2Qzmoy1dZbN/IN/GEiMgmoc6ty2vQLAvoG1QApXjyEZSeYJMSl dUfFAv1ZDup07cAClX2UpCIfmICDUoSBvAo4AsB7S0zNlNppdWFdqDlc9enq9hXrfByz nlkB2avx1lRmbEfjXZ2Y4EE/ybP+6Ccf4eRiTsXp6dfupatbo2wPo8+c8V42hzFv6RiN waVzAXnXskYGupZId4GTLfVHBCSKMnyUk2G6kC32DUF6gecLPc9pW93k9N3dq/3lIGXH eJ1uWvwrLyCjFbsG5tq+bjN7LDuwxIP9Ldmdd8cM4t2IskPdSC7rnNqfkL3pmQFjWs1r NDIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=fzxH4Jeii/asXH8ywHSGuzMBtbm/v6vTdU5ti7Qk53Y=; b=Bx5XKqUykWje9yGEq2boC73/iSvKb/m6rVJXyDu5PuO2DSNpml8deIWLw7dwn3YaeT Xewx5Yw/cZ7IahQmGSYc88CFcr6adT6njSXcQ6n7PBMhNQvD4eMBUruA2j23sJ5RXigq KVosz5mzVSP5/d5sr9ziAKRukgHO3rEI+gw7W6x1j7wVv8BXiHpJwm0J7MrekNRBJmsL MI1lE+QTnyJ/HxW8WtW4AnRxw/rdXIfWozpABlufupGAgKJZ0FiYktIB9jdqNvMTnCtv r6VImISSW+aKvnnvPu5kk7QxTahQJ1d5pxHqCMVIfzsVZzJ8a23t14/xwfq7ikp9y5uX 1XpA== X-Gm-Message-State: APt69E0hLdoufMb+KAtpUNBkEqvJczYp9Qb3nrMv6lo280CLPQZXw+G6 9XJ2vz6cGC1YMcZQv5nTYNSmRQ== X-Google-Smtp-Source: ADUXVKLg2ADdyXqEhy1xdmUdQm12FcnaKgAtlMy4+eHUKxMozdc/2aQdj2IniPM5qtlPmPRyWOOexQ== X-Received: by 2002:a17:902:583:: with SMTP id f3-v6mr22248990plf.115.1529546948976; Wed, 20 Jun 2018 19:09:08 -0700 (PDT) Received: from [192.168.178.21] ([118.148.121.80]) by smtp.gmail.com with ESMTPSA id g66-v6sm9393770pfk.99.2018.06.20.19.09.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Jun 2018 19:09:07 -0700 (PDT) To: Martin Thomson , "tools-discuss@ietf.org Discussion" References: From: Brian E Carpenter Message-ID: Date: Thu, 21 Jun 2018 14:09:11 +1200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Tools-discuss] STD series in bibxml X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2018 02:09:12 -0000 Martin, RFC 1700 is Historic and obsoleted by RFC3232. STD2 no longer exists, is not listed at https://www.rfc-editor.org/standards, so shouldn't appear in any (modern) metadata. It would of course be good if the bibxml metadata included the status. I hope that's planned for v3. Brian On 21/06/2018 13:12, Martin Thomson wrote: > Not all RFCs that are in the STD subseries include the proper > label. See for example STD 2/RFC 1700: > https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.1700.xml > > ___________________________________________________________ > 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 > From nobody Wed Jun 20 20:47:55 2018 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 8807513101B for ; Wed, 20 Jun 2018 20:47:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x-Cuq_tM8sPz for ; Wed, 20 Jun 2018 20:47:53 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81A25130F26 for ; Wed, 20 Jun 2018 20:47:52 -0700 (PDT) Received: from [192.168.178.20] ([93.217.82.242]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MA91t-1fKb5m0c2L-00BNQJ; Thu, 21 Jun 2018 05:47:47 +0200 To: Brian E Carpenter , Martin Thomson , "tools-discuss@ietf.org Discussion" References: From: Julian Reschke Message-ID: <629d6e6a-fbc1-372d-34ce-5556675c3d0c@gmx.de> Date: Thu, 21 Jun 2018 05:47:43 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:ng7q0cKY/hTqdnsklqXH0DDGylzpDHyKA7s/MG5zFsNeuyKhG6K TyCnJ52QM2ssQQnUjBpWZ5XMO0NgJTGqFmnNsYSLOuH0sZ3B8nDqqD1rw8BFC7OE0Q1GioY 7dKQCw8UASJg+epQ5ws8Lwp8T13sP7FGiRXraqzo7maQwixDNw6ivcK9WQRc8hlFGY/5nxH siurh7eOmYjl/8zHT8kyQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:/rvd/rsG/oo=:I/Fw0rsObAAv0TgCj23Uel fWfRul+BNx0QHwRCr00tKAix51Rk6ruxvWR0u62iGJA9Z2HzbvpgXBqifYujaiJ4zdg8vPV8w sNxI0dHcw+ccuoZfmdV/LiQ51ytxOveB+3YJDS4ELyGjwxlQrE1V/dztAlaYBGqamk53JAk8L frnYBK1LmYcyFP7X+G7j6eSih0oOEEL1fWVI7LfIEK//OyUJguxzGwAPG2MLYuMuJYe3hauwC KboK/Rpk7XLlHRsIXvhmLewvcykNmAfXCFagqncHXGe79Tm4aupPIst0VD9MchjhOjmn1o+9I 1G2SxDksvn4BLbITG8F0mLUYB3QXYCsvEc71knhdXZGtqjRLZ+QDOu730pURO8GbOiBTbGD1p lj7MSceR4g8Ak3I9O4OEY3yWmjBugmH3vGS8F7D8G/2fDe1hsDREf/5fHyxZZoDHFj47+Vef/ rkYbA2gLjQ80VfKhXA3SgiJVQJXbYh0MPvHg3QHHwOdehT8yDP6Y4W+tVtaPVlGsj7laEKut3 feaKScXWL2pNX1WR+AcZuRASFOtm3HimuOYFmj1Y+Rwh3Xn5WSqoSg37yDjJzGV2oCO+Y8KuD 68m/FpiY0hCtSbKrOhPe9BzzxmE/9dSxQ7oWisDeQSCSaLy676y4lsm/aAq+X/3uoAgEc/xib bMPZPoF/ti1eeIQld33Uj0EkYH1QyN+os/93kcelBBW9rWc+dOvsGSi9r/7sl7yRb0Phexb29 RKsVPtrgRv6U1X3/kz+MPvdfbGeZXbUM4XYOmkscxdsm7K7Q/UH7CivoBVl1FezJb+Ydzi+Mq FET04l5 Archived-At: Subject: Re: [Tools-discuss] STD series in bibxml X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2018 03:47:55 -0000 On 2018-06-21 04:09, Brian E Carpenter wrote: > Martin, > > RFC 1700 is Historic and obsoleted by RFC3232. STD2 no longer exists, > is not listed at https://www.rfc-editor.org/standards, so shouldn't > appear in any (modern) metadata. > > It would of course be good if the bibxml metadata included the status. > I hope that's planned for v3. I'm not aware of anything related to that. Best regards, Julian From nobody Wed Jun 20 20:59:36 2018 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 8571B131031 for ; Wed, 20 Jun 2018 20:59:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_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 PKhd7S7uBoXb for ; Wed, 20 Jun 2018 20:59:33 -0700 (PDT) Received: from mail-pg0-x22e.google.com (mail-pg0-x22e.google.com [IPv6:2607:f8b0:400e:c05::22e]) (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 CBB05130E12 for ; Wed, 20 Jun 2018 20:59:33 -0700 (PDT) Received: by mail-pg0-x22e.google.com with SMTP id z1-v6so760857pgv.12 for ; Wed, 20 Jun 2018 20:59:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=ju6j209lppJzJG8C63GgjsyYFz1jQFoU1PUoN+w3vbM=; b=oEy4gNgUfRBU1B5XYw2Wg3jbeejm+xLeJT9b38iSqRgc18LiMUkSMbe6hh8MvjtETP wOOCnOtDcavzo5uYx90M1n6iDriUCbB3Q3OYFGLCL0Qq4hbkrOzO3Uol3MJ+mMDa3cxI /sAVQODy/51o/A7eG0ePDj3biKtdzPhDu29VO2pefkNzG0nePsualFXHFu6BQcGMVxtJ N0bwPPPjJ4CBtQiIvXmE20igiXGcCJxoeGanNaP5/vYkIP0DkdvtK1lj4/e0A0qMnU4w EpbyBLYx1nRTxgj2JaTV2+vmLPfUoKALafIgE8NTTHb8ivwT6TXP5HC5y9Vm/GryrmDI 1Vkg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=ju6j209lppJzJG8C63GgjsyYFz1jQFoU1PUoN+w3vbM=; b=XYQMngb8jGQH1S1hm9eWD9sjA6TqIAxUICilgGUs3Fi0PEX3MFDE+oveW2UApAzL9B C+//FvdMmu3wscMfwZO5ZgN+M2Zc4V+E7jaLCNQiuTzJkuTSXBi136jc6JFV2cVCFobO Mrdj+GWZ3xj5QFC3Ms1ZTMUVjM8UdXYwDw079rXtdqRAA3n+YcAdf1rNIQ1p/tPYlnwp e8DQkGqxVxYLnxURY6gsyuNsb2tOVsYzVd8Yt/HpeO0C37PLBi5o1ZtQ25fHXunfb6rt 1kMzrQIzWzXrZWm8pdlDfk0wCgK8h6dGC/BCsnoE2QsmvMd3eyEnVb9Db93gMV2DBGGZ dBfw== X-Gm-Message-State: APt69E1gRRCkuausnpeyDK2OYY6cmOueR7AMbPX+hT5D9bvdvf1OatGM TkxpcdzT5iL+xIVy0VyxLLOF4w== X-Google-Smtp-Source: ADUXVKKUm2W1BpIQCSYmYP+X2yqlKB7HV1ivnuWYtLM+nUxRrLDK9iqpok04YaL8+GDPsRS7pLu2eA== X-Received: by 2002:a63:78c6:: with SMTP id t189-v6mr20899054pgc.239.1529553573147; Wed, 20 Jun 2018 20:59:33 -0700 (PDT) Received: from [192.168.178.21] ([118.148.121.80]) by smtp.gmail.com with ESMTPSA id t13-v6sm4102089pgv.43.2018.06.20.20.59.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Jun 2018 20:59:31 -0700 (PDT) To: Julian Reschke , Martin Thomson , "tools-discuss@ietf.org Discussion" References: <629d6e6a-fbc1-372d-34ce-5556675c3d0c@gmx.de> From: Brian E Carpenter Message-ID: <33c9857c-a70d-4209-01c3-64f84fff428c@gmail.com> Date: Thu, 21 Jun 2018 15:59:35 +1200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <629d6e6a-fbc1-372d-34ce-5556675c3d0c@gmx.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Tools-discuss] STD series in bibxml X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2018 03:59:36 -0000 On 21/06/2018 15:47, Julian Reschke wrote: > On 2018-06-21 04:09, Brian E Carpenter wrote: >> Martin, >> >> RFC 1700 is Historic and obsoleted by RFC3232. STD2 no longer exists, >> is not listed at https://www.rfc-editor.org/standards, so shouldn't >> appear in any (modern) metadata. >> >> It would of course be good if the bibxml metadata included the status. >> I hope that's planned for v3. > > I'm not aware of anything related to that. Ah. I'll continue on the xml2rfc list. Brian From nobody Wed Jun 20 22:29:40 2018 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 D6D4B13103D for ; Wed, 20 Jun 2018 22:29:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_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 N48hwNaAlHBG for ; Wed, 20 Jun 2018 22:29:36 -0700 (PDT) Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (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 1CEEC131027 for ; Wed, 20 Jun 2018 22:29:36 -0700 (PDT) Received: by mail-oi0-x236.google.com with SMTP id h79-v6so1757974oig.13 for ; Wed, 20 Jun 2018 22:29:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wNOsHEYRHDp75QQblDYq85ZuczLBcAzeMunjHNq477E=; b=DVRDfyaYLygfUlgQdDaptG5wbb96qUpIzgb3dgWwcdVut/tLjsQvW3YNAkAFOofPkn 4kOvgs9KHLuSrgMBEN38cB14sJcZ2F2M+uFp9Jzz05i960b/2IXznfaQZE31n8fv+Cjn EnXfvS+33iUg6hdQsik9sy9RhnArLPMZw3XaDKTCCRaf1JZKcwGq0ulcupZ8TLBbLZZP ogPCGEzfTiC4pdKulR8VQu2b7PpR5q3/xXgNUmmkg+G7pgfMOfrRYJRfSYrUBWkGa71j BYKOnSpXsCJbOL662OPJj4mKNzPveTnbTKAZYG2D178+be4Qp9bvgKxVhVzXlC2MMTY2 FpQg== 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=wNOsHEYRHDp75QQblDYq85ZuczLBcAzeMunjHNq477E=; b=J5znZ/rrS6o5oUMdwfsjjNXN6HYRu1wXaIm08shWc5np72eWImrqGynn85SdpyzD8o rtZUAbsHBEOCin8IvOl0jBl5/aV9DGObikvcL0uUt297cJJGKfzJFeyKNzeJXVtEeSxC DWsO8zKVBAiPb6NmNcERum8cVqpJDm6Sfm1OFThq61BM/GHRvdlh1zUKhWXONV7bMQFz p3xBs/HSrHNKUyzvTdt+k2zCcuThhpN5Oxz9UV6vO7JM1rMIk5/+Af3rYddC0JTGP+pM wE4itA2frGDvDrDB0pmTNKdoNr/WPAy3PrAM8wJhpTYttN3OV8SONw4F6goqFw805FO8 5shg== X-Gm-Message-State: APt69E3VLf5s57Me6DLxojDlvCiOMTxs5RT3sxVidNorP2mrCiqm5Qlv 9GRjtd9Q1A3LKYXjnLtHt5VrDyigWU1XKUDk0ss= X-Google-Smtp-Source: ADUXVKK4UIarJtPQycFzNG8E+c0VqDDTWv+9tj9J2BUeUcBbF00I5NOu8CLgQZv+bVC6r8KOGnuJZ2NyP5vQDL0Xe94= X-Received: by 2002:aca:51cb:: with SMTP id f194-v6mr14441239oib.110.1529558975469; Wed, 20 Jun 2018 22:29:35 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Martin Thomson Date: Thu, 21 Jun 2018 15:29:24 +1000 Message-ID: To: Brian E Carpenter Cc: "tools-discuss@ietf.org Discussion" Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Tools-discuss] STD series in bibxml X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2018 05:29:38 -0000 On Thu, Jun 21, 2018 at 12:09 PM Brian E Carpenter wrote: > RFC 1700 is Historic and obsoleted by RFC3232. STD2 no longer exists, > is not listed at https://www.rfc-editor.org/standards, so shouldn't > appear in any (modern) metadata. https://tools.ietf.org/html/std2 shows no indication that it is any different from STD 3. I know that the IESG is interested in improving the metadata situation. From nobody Wed Jun 20 22:57:07 2018 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 82617130F20 for ; Wed, 20 Jun 2018 22:57:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_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 kWiuse3ZPLcO for ; Wed, 20 Jun 2018 22:57:01 -0700 (PDT) Received: from mail-pl0-x22b.google.com (mail-pl0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) (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 88F20130EE8 for ; Wed, 20 Jun 2018 22:57:01 -0700 (PDT) Received: by mail-pl0-x22b.google.com with SMTP id w17-v6so1052427pll.9 for ; Wed, 20 Jun 2018 22:57:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=H4bAvsf+gopsjy4IDTPSE8abk3FUDCT9gI3PHsUgSoE=; b=UYc2jISKzkCcNg8UMhDoOIQlwGvo6QodM482dcnYrgWcA4rC6nh3pIMAZmnJLmfKtk BV0eyJapfp3Sll6ezn/uLmmLjB6UgVADbfLJNkcyuBzJo4p+7PNfhrNLkSblwpG3lPhr mgChzDHit3pAjg3XvFQK1dWYRxDUaZdBd5B3tYSyQxLm9nrQZ8krAaZP2Tzv27FAeOhT Y1ns81vRbPVaaeub8ktei2i2J04NNDZyVSnBk1QOZ2z25N+U0l4TJcIBC/oex/1s8vy+ UxKgk4fwJSlYogfbQLSxfx733EWElD0JML96HEHHco0aQrzmRz1FJ64HJOkRDKg/Khge CYUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=H4bAvsf+gopsjy4IDTPSE8abk3FUDCT9gI3PHsUgSoE=; b=Ho3y+8udTZgskn1z3m0BI7/f1Sr7hH0GCD2I2VSWBJZFpIn70ea7Nl00nMWICNoRPy dPqlz0dC6aCt0HQmZMpVLOXZlVDvoxrbsJaUHHZdQeStv3gyhQOBNuBA+O2eExRBjfR/ aXFMp+Gn7swmIw8LVP3VO0YzFuVME5avJ9bHtdvPcisjK49UYu/u25bcuO7ek8JdO6Kt r71bsohrMs1e+vIQLEL9X/YEJe7yqqz5l+uDt2zq5oCe65cSP1vewFKciU671GIXdQXd Uad7yV/MquRheHB++vN8ZZ1jXGbRa1WMNBHxAeEnnyiNyClT5327SeulEZbp6vP8jAxv tOJw== X-Gm-Message-State: APt69E0o5/p4bHvJJHNC0rpg3GAEPgw4xfUAEmOvWHU0nim7D7bzL84J Q25v1BRCcmLeGzT8LmglXTN7ag== X-Google-Smtp-Source: ADUXVKK9FcxHaBmppEZY7lXUTaG21r8jfDc37lZHbxGAcKC61nTzxwB6xgxh4mhuDvPReTKK8FTYbg== X-Received: by 2002:a17:902:70ca:: with SMTP id l10-v6mr13949939plt.174.1529560620795; Wed, 20 Jun 2018 22:57:00 -0700 (PDT) Received: from [192.168.178.21] ([118.148.121.80]) by smtp.gmail.com with ESMTPSA id t17-v6sm6716036pfj.75.2018.06.20.22.56.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Jun 2018 22:56:59 -0700 (PDT) To: Martin Thomson Cc: "tools-discuss@ietf.org Discussion" References: From: Brian E Carpenter Message-ID: <9e320857-fd81-68de-d7b8-4b8f64baeeaf@gmail.com> Date: Thu, 21 Jun 2018 17:57:04 +1200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Tools-discuss] STD series in bibxml X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2018 05:57:04 -0000 On 21/06/2018 17:29, Martin Thomson wrote: > On Thu, Jun 21, 2018 at 12:09 PM Brian E Carpenter > wrote: >> RFC 1700 is Historic and obsoleted by RFC3232. STD2 no longer exists, >> is not listed at https://www.rfc-editor.org/standards, so shouldn't >> appear in any (modern) metadata. > > https://tools.ietf.org/html/std2 shows no indication that it is any > different from STD 3. That's not good. On this point, things are better on the RFC Editor site. Of course, the RFC Editor is the custodian of RFC status. In this particular case, RFC3232 could have been clearer about the STD number. > I know that the IESG is interested in improving the metadata situation. Full coordination between IETF Tools and the RFC Editor tools would be good. Brian > From nobody Wed Jun 20 23:43:17 2018 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 224B113104C for ; Wed, 20 Jun 2018 23:43:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SL0KXaV8TGpw for ; Wed, 20 Jun 2018 23:42:58 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF49D128BAC for ; Wed, 20 Jun 2018 23:42:57 -0700 (PDT) Received: from [192.168.178.20] ([93.217.82.242]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MBFgr-1fNxLE1nE5-00ADyZ; Thu, 21 Jun 2018 08:42:53 +0200 To: Brian E Carpenter , Martin Thomson Cc: "tools-discuss@ietf.org Discussion" References: <9e320857-fd81-68de-d7b8-4b8f64baeeaf@gmail.com> From: Julian Reschke Message-ID: <857d5ce7-8b75-94fc-e3d4-5ded2d9a7915@gmx.de> Date: Thu, 21 Jun 2018 08:42:50 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <9e320857-fd81-68de-d7b8-4b8f64baeeaf@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:KbMsov24cx//xU/n4pkwxA0TuiysX4fjaOGwnm6OPYn5fvZkSlz L2mvLyCwzkafNfcppwQT9KQDstb1z9mYZRYHEbrJgUi7CtmR6N2pHeyIFr5Kua2LA/asAHA PHAHyEiWlq2d1qJWDvSu2DnPZI31Em6nV1LIjHsbFevXc2ZU9XiYTKVvWbya5ortfdnc8PA mygav1sZ3/ItjCK75tBXg== X-UI-Out-Filterresults: notjunk:1;V01:K0:wo5QJ6ky5kU=:OLTIWfWpKgYzkz53YN+cIf JNW2miZPtjfdLz3hBoco9JSL7Va3Js7jAFLoUz/kSd9vFQ0hA/Dr7iUYB8GxYwOaPAKIAz57V SjAGT1njNAy2cvFZ8oddyLdnaRqxYgTmFlKi7erAgnJ24k8HkFz6QCA5x8Xw8tM4IhWxlq4sM aZdzbdBKip0nnwrAVShz+DjVe+tMULblgUWrhXSU0FTtHnDYgnvlu4zINkUp7pWkMtiHiCM/X 9hOqi487xxd/IKP0Iw7JYdhXGYBbQOan2VfOfbfvK1Eu2UfKSWAm5q87YJ5A+WHWjow8y0apr VDUIRj6A994Z/0QRQu1djpuO/XZBE9NSAGy+f5wAiu3RkpxTirPYHMlR3b54+9x9jIJDLqAbd cD2Mxukw2/8ixKlVI4GDMhVP5ic5jkfGnXTg4N3zoRmyL+tlFbSxhp/1WVEiDprh92mjWxCtk spQHu5FZKtxQZVnGuKbfB2vu8NQfPA2FzPZrkWUY5vIufz5V8A5Gl0k7ORrMsnbA2YC/jYAky jrINYZn1ynUAboBDItb5Wgfu3sx/qW2GIRE9XQRY1sNmV/YurVDkp5BPoLTk7heY3H9Xy0scV B1reuYMNnqz+QJ0dJDYtWlev2qegKbqnXcO8dO9FdXSPgKf5DpObToRM2L5ByFxgglNH58ylu bCW41WjdpeRSN1ix5nVmld7RRWPvjNby2LaZGsIV6i6a1H21+ltkgevDC6pCOn1SYZ4C0cE9a OJC/2wAMK+bRB+b9lXB8vSTIthj5SuMU1qi0mp+E5RjIzXG7z5ECw1aWzRAQXE4kzxViDWSCj xK90G2I Archived-At: Subject: Re: [Tools-discuss] STD series in bibxml X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2018 06:43:02 -0000 On 2018-06-21 07:57, Brian E Carpenter wrote: > On 21/06/2018 17:29, Martin Thomson wrote: >> On Thu, Jun 21, 2018 at 12:09 PM Brian E Carpenter >> wrote: >>> RFC 1700 is Historic and obsoleted by RFC3232. STD2 no longer exists, >>> is not listed at https://www.rfc-editor.org/standards, so shouldn't >>> appear in any (modern) metadata. >> >> https://tools.ietf.org/html/std2 shows no indication that it is any >> different from STD 3. > > That's not good. On this point, things are better on the RFC Editor > site. Of course, the RFC Editor is the custodian of RFC status. > ... Yes, but: Best regards, Julian From nobody Thu Jun 21 13:55:17 2018 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 5F1D5130DC2 for ; Thu, 21 Jun 2018 13:55:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_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 yaznSXIhaiW1 for ; Thu, 21 Jun 2018 13:55:13 -0700 (PDT) Received: from mail-pl0-x22a.google.com (mail-pl0-x22a.google.com [IPv6:2607:f8b0:400e:c01::22a]) (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 3F47A12785F for ; Thu, 21 Jun 2018 13:55:13 -0700 (PDT) Received: by mail-pl0-x22a.google.com with SMTP id w17-v6so2291277pll.9 for ; Thu, 21 Jun 2018 13:55:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Qpr1UFtWYcSNf77hqI97Y9usI8Z8phN3VvFNVJ4QsGs=; b=OrN3v52yW9/n/3Nu9vd9b8/iv8PhAH9K87VJcGY1tU+w7Au3ke8YwGbW49dGgAr7eC 2uaD7/ka5NSC4Ch6exyfyw1zJzLPPEH0He7H6cYY0pF/CgV+gjVd5Yh66dWdhrbtAUs6 u0G/rnJOeM6hQC2bwHlv+0wdAtbkRjL8oAcQi+PiQuD/LR48myPDBqsOgUegFiK+DPi+ gfFxobkTPbeqtTujujQE7N3digVFguw0fk5kY2aJL6Z+qX+1RiWZ2XQGVmAjSyVB8IIO F7TWL4Ju2pxhi+p3eHWigw3j+5gjPkJKTTCjbuLD5q8Ns6nzCbQM52u6H0lF7Lwl4JPT 8oSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Qpr1UFtWYcSNf77hqI97Y9usI8Z8phN3VvFNVJ4QsGs=; b=nehq7vGeib9UnI0+xzO/U1gBf2/NLE3ZeGhQYwUZI4wDebFcgL7pVkFhpj0ofP3sh7 LTWmcmDhH7Eyd8ddagr8T6jLQncNlO2CtAj8CdMIsDm3TLw6bsMouwIV+XTXVU6eK50Y /z1UmpYSjEH0Vig2t1Yq7hdZpEW9dtfv9v0m7U2IYwPucGKDkOJWnjnAyeYChy1L8vhN Wjd55kvWrDRkRKJJNpuNjOXcMj4hJQN3yvDaU9zM+sr4zvGVDch+Vq0AED794bUKlt4Y BQ22W4WxOhrQQaTTdodOdCng8BRJXAUzvX7kxI6Jtx/bftVtvQxyQWrEmEPvCBQdwa0J qmhA== X-Gm-Message-State: APt69E3xS4pigj8/D+Af0jgUZm5app0mieDOKtOhLHymKBMKwDLHKcNy 7CtlNnlfubXvp2YDtyjz4a/wtw== X-Google-Smtp-Source: ADUXVKJ2r1Z0TrxQq2l57ucTavv3Tn8GnEFN8Dt9BnBJZGmdC2O2eEBXWUBc/KOVprd6I5skA9JjEQ== X-Received: by 2002:a17:902:6e01:: with SMTP id u1-v6mr29881514plk.96.1529614512651; Thu, 21 Jun 2018 13:55:12 -0700 (PDT) Received: from [192.168.178.21] ([118.148.121.80]) by smtp.gmail.com with ESMTPSA id d65-v6sm9362405pfj.20.2018.06.21.13.55.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Jun 2018 13:55:11 -0700 (PDT) To: Julian Reschke , Martin Thomson Cc: "tools-discuss@ietf.org Discussion" References: <9e320857-fd81-68de-d7b8-4b8f64baeeaf@gmail.com> <857d5ce7-8b75-94fc-e3d4-5ded2d9a7915@gmx.de> From: Brian E Carpenter Message-ID: Date: Fri, 22 Jun 2018 08:55:16 +1200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <857d5ce7-8b75-94fc-e3d4-5ded2d9a7915@gmx.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Tools-discuss] STD series in bibxml X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2018 20:55:16 -0000 On 21/06/2018 18:42, Julian Reschke wrote: > On 2018-06-21 07:57, Brian E Carpenter wrote: >> On 21/06/2018 17:29, Martin Thomson wrote: >>> On Thu, Jun 21, 2018 at 12:09 PM Brian E Carpenter >>> wrote: >>>> RFC 1700 is Historic and obsoleted by RFC3232. STD2 no longer exists, >>>> is not listed at https://www.rfc-editor.org/standards, so shouldn't >>>> appear in any (modern) metadata. >>> >>> https://tools.ietf.org/html/std2 shows no indication that it is any >>> different from STD 3. >> >> That's not good. On this point, things are better on the RFC Editor >> site. Of course, the RFC Editor is the custodian of RFC status. >> ... > > Yes, but: I have already opened a ticket about that with the RFC Editor. Brian From nobody Fri Jun 22 03:13:43 2018 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 57D23130E19 for ; Fri, 22 Jun 2018 03:13:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.091 X-Spam-Level: X-Spam-Status: No, score=-4.091 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=netapp.onmicrosoft.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 Ag8MOmxaLoms for ; Fri, 22 Jun 2018 03:13:40 -0700 (PDT) Received: from mx144.netapp.com (mx144.netapp.com [IPv6:2620:10a:4005:8000:2306::d]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BC521274D0 for ; Fri, 22 Jun 2018 03:13:40 -0700 (PDT) X-IronPort-AV: E=Sophos;i="5.51,256,1526367600"; d="asc'?scan'208";a="264719824" Received: from vmwexchts02-prd.hq.netapp.com ([10.122.105.23]) by mx144-out.netapp.com with ESMTP; 22 Jun 2018 03:13:39 -0700 Received: from VMWEXCCAS02-PRD.hq.netapp.com (10.122.105.18) by VMWEXCHTS02-PRD.hq.netapp.com (10.122.105.23) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Fri, 22 Jun 2018 03:13:39 -0700 Received: from NAM05-DM3-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS02-PRD.hq.netapp.com (10.122.105.18) with Microsoft SMTP Server (TLS) id 15.0.1367.3 via Frontend Transport; Fri, 22 Jun 2018 03:13:39 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=dT/n6JniM1//H3NS30k7i+ceduR0s8CWyev1naQUZRA=; b=eJqOtgvzJHXDpVwWPPI64SPvPrDEDpBfOdYN+Z9RxPNvQqR/KsPTYnRO2pQpvYewzOzsNhtohKPuB3hzNAsXs2RRz+A0G+8aA+0zzWogGt9UAJCbsamzK4n7z3HTVdoIGZae/oZfobiaauZo2uwMLN/6J7db6x0JW38O2ajY4a4= Received: from BY2PR06MB1765.namprd06.prod.outlook.com (10.163.33.19) by BY2PR06MB091.namprd06.prod.outlook.com (10.242.43.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.884.20; Fri, 22 Jun 2018 10:13:37 +0000 Received: from BY2PR06MB1765.namprd06.prod.outlook.com ([fe80::cd6b:eda5:7c66:d309]) by BY2PR06MB1765.namprd06.prod.outlook.com ([fe80::cd6b:eda5:7c66:d309%3]) with mapi id 15.20.0863.016; Fri, 22 Jun 2018 10:13:37 +0000 From: "Eggert, Lars" To: "tools-discuss@ietf.org Discussion" Thread-Topic: rfcmarkup bug Thread-Index: AQHUChGvKfikUSnMxU6tj766V9la1w== Date: Fri, 22 Jun 2018 10:13:36 +0000 Message-ID: <224AE4A3-36E8-4F0B-9AD5-929E84972F05@netapp.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-mailer: Apple Mail (2.3445.8.2) authentication-results: spf=none (sender IP is ) smtp.mailfrom=lars@netapp.com; x-originating-ip: [217.70.211.15] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; BY2PR06MB091; 7:SSfpCzZjNDiW/d0JUv6y2i4p69cj4hDkdgvW4Zuyu1yd5RKiXBdOBH8jthjHZy9AXYXD5QHmdPLaXIL8uVm1fIWmMNqR1mWeuHK6VLCzIvZt/6uX262i2crctjjy8sUW5N68FDfsCdrC9ZMmDTa26rPQZg/0Vvle0Lt9AfVF8gYUf0zMAt4z3IsXrBg5YERTmnRwz0PIqmah/xn79IeGwO9+EaXekYoLdjqhJazOB1pt8yUcudMjL/k00Zy/X2u4 x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: 425a1e9f-b36a-4d05-ed4f-08d5d828d1a4 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989114)(4534165)(4627221)(201703031133081)(201702281549075)(8990104)(5600026)(711020)(2017052603328)(49563074)(7193020); SRVR:BY2PR06MB091; x-ms-traffictypediagnostic: BY2PR06MB091: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(102415395)(6040522)(2401047)(5005006)(8121501046)(10201501046)(3231254)(944501410)(52105095)(3002001)(93006095)(93001095)(6055026)(149027)(150027)(6041310)(20161123562045)(20161123558120)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(6072148)(201708071742011)(7699016); SRVR:BY2PR06MB091; BCL:0; PCL:0; RULEID:; SRVR:BY2PR06MB091; x-forefront-prvs: 071156160B x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(396003)(346002)(376002)(39380400002)(39860400002)(189003)(199004)(558084003)(6116002)(486006)(3846002)(25786009)(82746002)(6506007)(478600001)(53936002)(99286004)(105586002)(106356001)(7116003)(26005)(8936002)(316002)(57306001)(3480700004)(50226002)(186003)(5250100002)(97736004)(14454004)(5660300001)(102836004)(86362001)(68736007)(6512007)(83716003)(66066001)(6306002)(6916009)(81156014)(81166006)(8676002)(6486002)(6436002)(221733001)(305945005)(33656002)(3660700001)(99936001)(36756003)(7736002)(966005)(2616005)(476003)(3280700002)(2900100001)(2906002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR06MB091; H:BY2PR06MB1765.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: netapp.com does not designate permitted sender hosts) x-microsoft-antispam-message-info: KirevLcQMUj1XvgL00BNzoaO+Cry9TFvBLwtDqNhOWcYFdSp8TZ8LOygI8RC39faz+/8jwKvR2a37cYlATggY6VtOajWSS2WzMglXHT6SRNjTlc3V53eIxxPsebMnmWg2H1s3+zMwQPKPuKAtoQLGxw0wAOLqCi0qB6EL2u+wE+1+DRukNaFZyj6QLR6WOLXO2EXEUH0VDHAzlAtZHCFbIsG4Tj0ma7FFfQk3dkjVP5WGqj2undkfYDMdmmowyHBcqZkmB5LvwU1tHJ0lpaDlsuV76tdfjyrWKuu/3avCvLfFJJJFJgEe+Q/NZNGn9T8WAzEUxOY7hBUnCE8tD4y2Q== spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/signed; boundary="Apple-Mail=_11D1DC77-4CBC-4ADC-B06F-C8585A009BFB"; protocol="application/pgp-signature"; micalg=pgp-sha512 MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: 425a1e9f-b36a-4d05-ed4f-08d5d828d1a4 X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jun 2018 10:13:36.8768 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR06MB091 X-OriginatorOrg: netapp.com Archived-At: Subject: [Tools-discuss] rfcmarkup bug X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2018 10:13:42 -0000 --Apple-Mail=_11D1DC77-4CBC-4ADC-B06F-C8585A009BFB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, the list of versions in the header of = https://tools.ietf.org/html/draft-ietf-quic-transport-12 is missing = versions 10 and 11. Clicking through the versions, the header of various version pages is = either complete (e.g., = https://tools.ietf.org/html/draft-ietf-quic-transport-03) or incomplete. Lars --Apple-Mail=_11D1DC77-4CBC-4ADC-B06F-C8585A009BFB 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----- iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAlssy9AACgkQVLXDCb9w wVeQIRAAp4TJaSpjnk+ntEpHu6TDVCQq1iIweNjme1nPTaINhG+QVDCOfBo7ftcK 5mctaX+Ywc47OU5BGD37JhbsWSAWYQY83VlGy7MvdtejeIlD46WePrYedYt85lXO FdawiUdZhG/2Z9uAKl1ywMMejRk60pZWXUD86epECsEM+AJ41juwKCvSBB4LjtzQ dr/JfmAge7VkKs0Sz5nmweB2EojcfkjN0EiOeo5I6tv8RWlU9kAfJWKqyLjLvsir GRgLGy/OuMZF9ytCzDAV1M7PUauv5wmRzYCnZrvYCHG524c9GCe00Cpt8nM9O6gu bjS5bSt40YwswPgkN6jbEOiHK36U4LOgxq+EfsE9MiRXuyGBIj+KuXxrRE/Qikd2 yxIKC4Em0/3Vny7G4M3qFFFgrqnOr6O6YXm8vOWsoHq1aFAUxjkJMbae5vzh40T2 HIh6OYBx60pX9fbNrASZggGcmPJsIeb3Ch9IVhuM2n1wTQHXAA2aDh19PnfdZbiS Iorsqs+vPXS3187Xjm5pJOien+PB2YPlW5Ykest8Dot6FegMi/KF4z7bizMVU3Ot d7eld4l4WtNdQX6A2cIaAd3eRF5Q/Dm3ERkkAYg2SDTuzu8AIBI4EEkqKaAFUcHU XcQqoLk606mwXXzc659tLYAYsVW3OLsyawG7Gg/WPygIwD+sasc= =QFoy -----END PGP SIGNATURE----- --Apple-Mail=_11D1DC77-4CBC-4ADC-B06F-C8585A009BFB-- From nobody Fri Jun 22 11:24:02 2018 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 68D23130EC4 for ; Fri, 22 Jun 2018 11:23:59 -0700 (PDT) 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, HTML_MESSAGE=0.001, 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 V9qmTdHoKDDj for ; Fri, 22 Jun 2018 11:23:55 -0700 (PDT) Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 2DAD1130EC0 for ; Fri, 22 Jun 2018 11:23:55 -0700 (PDT) Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id B2DE62ABD98A7 for ; Fri, 22 Jun 2018 19:23:48 +0100 (IST) Received: from SJCEML703-CHM.china.huawei.com (10.208.112.39) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.382.0; Fri, 22 Jun 2018 19:23:50 +0100 Received: from SJCEML521-MBS.china.huawei.com ([169.254.2.90]) by SJCEML703-CHM.china.huawei.com ([169.254.5.167]) with mapi id 14.03.0382.000; Fri, 22 Jun 2018 11:23:45 -0700 From: Linda Dunbar To: "tools-discuss@ietf.org" Thread-Topic: Need IETF to maintain the tool to convert .PRN to *.txt Thread-Index: AdQKVgPj2uAIxITURVenC/8qbS0qXQ== Date: Fri, 22 Jun 2018 18:23:44 +0000 Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66B072AF4@sjceml521-mbs.china.huawei.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.218.137.155] Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F66B072AF4sjceml521mbschi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: Subject: [Tools-discuss] Need IETF to maintain the tool to convert .PRN to *.txt X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2018 18:24:00 -0000 --_000_4A95BA014132FF49AE685FAB4B9F17F66B072AF4sjceml521mbschi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I've been using Joe Touch's tool to convert .prn to *.txt for many years fo= r IETF drafts. But his website recently being forwarded to https://www.strayalpha.com/tools/ that no longer has the link. Can you help to find a tool for people using *.doc for ID? Word document is so easy for multiple authors to work together. Thank you so much. Linda Dunbar --_000_4A95BA014132FF49AE685FAB4B9F17F66B072AF4sjceml521mbschi_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I’ve been using Joe Touch’s tool to conv= ert .prn to *.txt for many years for IETF drafts.

  But his website recently being forwarded= to

  https://www.strayalpha.com/tools/ that no longer has the link.

 

  Can you help to find a tool for people using = *.doc for ID?

 

Word document is so easy for multiple authors to wor= k together.

 

  Thank you so much.

 

  Linda Dunbar

 

 

--_000_4A95BA014132FF49AE685FAB4B9F17F66B072AF4sjceml521mbschi_-- From nobody Fri Jun 22 11:35:54 2018 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 43296130EE8 for ; Fri, 22 Jun 2018 11:35:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.778 X-Spam-Level: X-Spam-Status: No, score=-1.778 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, T_DKIM_INVALID=0.01, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (body has been altered)" header.d=strayalpha.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 B7-kCYpPWj0V for ; Fri, 22 Jun 2018 11:35:40 -0700 (PDT) Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (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 7E575130EE9 for ; Fri, 22 Jun 2018 11:35:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=jb1glvtxijPDmtC2FIaXEMyjf58VOLpxCmhFATHxVuI=; b=BFiDz9J7o73PwWiSep6+bJdcy yhVmdwsayucePDKuk1R/qUOVmA645o95CXsD26QjNlCPhlBA4Y5/EeLWwO5P8MKHR55b/amIB+Jxg D7XNCQ/9h9Dv8AbGICPvA7k4R4ASpjVVhnyd2LwtK7j/n2ao0NXqMROS+bZ2lbbZx9IWhEuaUsCqC PP/hq+D0Tw08p5L++UnFIxcskpoDzAzm8Mc0Calt3ohCbPnUFPubPx13eBnIL7DiSaWwl+KWLMoH6 eoVymVkHAVvKJ9k1eVeQifSte1g2Vc1n0akwfv8zxdEcvmZ1lqFPLW41Ng+uEAGZFXcCITh6y5udR HvZYO0vcg==; Received: from [172.58.21.109] (port=42759 helo=[IPv6:2607:fb90:5a37:9abd:74a2:e556:9588:441c]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1fWQuI-001pPR-5w; Fri, 22 Jun 2018 14:35:39 -0400 Content-Type: multipart/alternative; boundary=Apple-Mail-44C557E3-4C39-4234-812C-8382E14656DE Mime-Version: 1.0 (1.0) From: Joe Touch X-Mailer: iPhone Mail (15F79) In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F66B072AF4@sjceml521-mbs.china.huawei.com> Date: Fri, 22 Jun 2018 11:35:37 -0700 Cc: "tools-discuss@ietf.org" Content-Transfer-Encoding: 7bit Message-Id: <623791B3-7A5E-4EBB-8E39-CDFDEDD701EB@strayalpha.com> References: <4A95BA014132FF49AE685FAB4B9F17F66B072AF4@sjceml521-mbs.china.huawei.com> To: Linda Dunbar X-OutGoing-Spam-Status: No, score=-1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server217.web-hosting.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - strayalpha.com X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com X-Source: X-Source-Args: X-Source-Dir: X-From-Rewrite: unmodified, already matched Archived-At: Subject: Re: [Tools-discuss] Need IETF to maintain the tool to convert .PRN to *.txt X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2018 18:35:51 -0000 --Apple-Mail-44C557E3-4C39-4234-812C-8382E14656DE Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi all.=20 I will pat the code to the new website today. The Perl code needs to be run a= s well - there are a variety of ways to do that in every OS. I do not expect= to support online running of just that simple Perl script.=20 Joe > On Jun 22, 2018, at 11:23 AM, Linda Dunbar wrote= : >=20 > I=E2=80=99ve been using Joe Touch=E2=80=99s tool to convert .prn to *.txt f= or many years for IETF drafts. > But his website recently being forwarded to > https://www.strayalpha.com/tools/ that no longer has the link. > =20 > Can you help to find a tool for people using *.doc for ID? > =20 > Word document is so easy for multiple authors to work together. > =20 > Thank you so much. > =20 > Linda Dunbar > =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 --Apple-Mail-44C557E3-4C39-4234-812C-8382E14656DE Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi all. 
I will pat the code to the new website today. The Perl code need= s to be run as well - there are a variety of ways to do that in every OS. I d= o not expect to support online running of just that simple Perl script. = ;

Joe

On Jun 22, 2018, at 11:23 AM, L= inda Dunbar <linda.dunbar@huaw= ei.com> wrote:

=

I=E2=80=99ve been using Joe Touch=E2=80=99s tool to c= onvert .prn to *.txt for many years for IETF drafts.

  But his website recently being forwarded t= o

  = https://www.strayalpha.com/tools/ that no longer has the link.

 

  Can you help to find a tool for people using *= .doc for ID?

 

Word document is so easy for multiple authors to work= together.

 

  Thank you so much.

 

  Linda Dunbar

 

 

____________________= _______________________________________
Tools-discuss mailin= g list
Tools-discu= ss@ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss<= /span>

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

Please report tools.ietf.org bugs at
http://tools.ietf.org/tools/issue= s
or send email to webmaster@tools.ietf.org
= --Apple-Mail-44C557E3-4C39-4234-812C-8382E14656DE-- From nobody Fri Jun 22 11:39:57 2018 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 8F8CE130EC2 for ; Fri, 22 Jun 2018 11:39:55 -0700 (PDT) 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, HTML_MESSAGE=0.001, 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 6l_mGkvgx4VL for ; Fri, 22 Jun 2018 11:39:53 -0700 (PDT) Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 3ABBF130EAF for ; Fri, 22 Jun 2018 11:39:53 -0700 (PDT) Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 2C1D7E624375E for ; Fri, 22 Jun 2018 19:39:49 +0100 (IST) Received: from SJCEML703-CHM.china.huawei.com (10.208.112.39) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.382.0; Fri, 22 Jun 2018 19:39:50 +0100 Received: from SJCEML521-MBS.china.huawei.com ([169.254.2.90]) by SJCEML703-CHM.china.huawei.com ([169.254.5.167]) with mapi id 14.03.0382.000; Fri, 22 Jun 2018 11:39:48 -0700 From: Linda Dunbar To: Joe Touch CC: "tools-discuss@ietf.org" Thread-Topic: [Tools-discuss] Need IETF to maintain the tool to convert .PRN to *.txt Thread-Index: AQHUClfficagKkhnDUO9mQaB/Ih1uKRsm0+g Date: Fri, 22 Jun 2018 18:39:48 +0000 Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66B072B13@sjceml521-mbs.china.huawei.com> References: <4A95BA014132FF49AE685FAB4B9F17F66B072AF4@sjceml521-mbs.china.huawei.com> <623791B3-7A5E-4EBB-8E39-CDFDEDD701EB@strayalpha.com> In-Reply-To: <623791B3-7A5E-4EBB-8E39-CDFDEDD701EB@strayalpha.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.218.137.155] Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F66B072B13sjceml521mbschi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: Subject: Re: [Tools-discuss] Need IETF to maintain the tool to convert .PRN to *.txt X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2018 18:39:56 -0000 --_000_4A95BA014132FF49AE685FAB4B9F17F66B072B13sjceml521mbschi_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 DQpKb2UsDQoNCllvdXIgcHJldmlvdXMgbWV0aG9kIG9mIHdlYiBjb252ZXJ0aW5nIGhhZCB3b3Jr ZWQgc28gd2VsbCBmb3IgbGFzdCAxMCB5ZWFycy4NCg0KQnV0IEkgYWx3YXlzIGdldCBlcnJvciB3 aGVuIHVzaW5nIGNvbW1hbmQgbGluZSAod2l0aCBDeWd3aW4gaW5zdGFsbGVkKSwgbm9yIGNhbiBJ IGdldCB0aGUgUGVybCB3b3JraW5nIG9uIG15IERlbGwgbGFwdG9wLg0KDQpUaGFuayB5b3Ugc28g bXVjaCBmb3IgcHJvdmlkaW5nIHRoZSBjb252ZW5pZW5jZSBmb3IgYWxsIHRob3NlIHllYXJzLg0K DQpMaW5kYQ0KDQpGcm9tOiBKb2UgVG91Y2ggW21haWx0bzp0b3VjaEBzdHJheWFscGhhLmNvbV0N ClNlbnQ6IEZyaWRheSwgSnVuZSAyMiwgMjAxOCAxOjM2IFBNDQpUbzogTGluZGEgRHVuYmFyIDxs aW5kYS5kdW5iYXJAaHVhd2VpLmNvbT4NCkNjOiB0b29scy1kaXNjdXNzQGlldGYub3JnDQpTdWJq ZWN0OiBSZTogW1Rvb2xzLWRpc2N1c3NdIE5lZWQgSUVURiB0byBtYWludGFpbiB0aGUgdG9vbCB0 byBjb252ZXJ0IC5QUk4gdG8gKi50eHQNCg0KSGkgYWxsLg0KDQpJIHdpbGwgcGF0IHRoZSBjb2Rl IHRvIHRoZSBuZXcgd2Vic2l0ZSB0b2RheS4gVGhlIFBlcmwgY29kZSBuZWVkcyB0byBiZSBydW4g YXMgd2VsbCAtIHRoZXJlIGFyZSBhIHZhcmlldHkgb2Ygd2F5cyB0byBkbyB0aGF0IGluIGV2ZXJ5 IE9TLiBJIGRvIG5vdCBleHBlY3QgdG8gc3VwcG9ydCBvbmxpbmUgcnVubmluZyBvZiBqdXN0IHRo YXQgc2ltcGxlIFBlcmwgc2NyaXB0Lg0KDQpKb2UNCg0KT24gSnVuIDIyLCAyMDE4LCBhdCAxMToy MyBBTSwgTGluZGEgRHVuYmFyIDxsaW5kYS5kdW5iYXJAaHVhd2VpLmNvbTxtYWlsdG86bGluZGEu ZHVuYmFyQGh1YXdlaS5jb20+PiB3cm90ZToNCknigJl2ZSBiZWVuIHVzaW5nIEpvZSBUb3VjaOKA mXMgdG9vbCB0byBjb252ZXJ0IC5wcm4gdG8gKi50eHQgZm9yIG1hbnkgeWVhcnMgZm9yIElFVEYg ZHJhZnRzLg0KICBCdXQgaGlzIHdlYnNpdGUgcmVjZW50bHkgYmVpbmcgZm9yd2FyZGVkIHRvDQog IGh0dHBzOi8vd3d3LnN0cmF5YWxwaGEuY29tL3Rvb2xzLyB0aGF0IG5vIGxvbmdlciBoYXMgdGhl IGxpbmsuDQoNCiAgQ2FuIHlvdSBoZWxwIHRvIGZpbmQgYSB0b29sIGZvciBwZW9wbGUgdXNpbmcg Ki5kb2MgZm9yIElEPw0KDQpXb3JkIGRvY3VtZW50IGlzIHNvIGVhc3kgZm9yIG11bHRpcGxlIGF1 dGhvcnMgdG8gd29yayB0b2dldGhlci4NCg0KICBUaGFuayB5b3Ugc28gbXVjaC4NCg0KICBMaW5k YSBEdW5iYXINCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXw0KVG9vbHMtZGlzY3VzcyBtYWlsaW5nIGxpc3QNClRvb2xzLWRpc2N1 c3NAaWV0Zi5vcmc8bWFpbHRvOlRvb2xzLWRpc2N1c3NAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5p ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Rvb2xzLWRpc2N1c3MNCg0KUGxlYXNlIHJlcG9ydCBk YXRhdHJhY2tlci5pZXRmLm9yZzxodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmc+IGFuZCBtYWls YXJjaGl2ZS5pZXRmLm9yZzxodHRwOi8vbWFpbGFyY2hpdmUuaWV0Zi5vcmc+DQpidWdzIGF0IGh0 dHA6Ly90b29scy5pZXRmLm9yZy90b29scy9pZXRmZGINCm9yIHNlbmQgZW1haWwgdG8gZGF0YXRy YWNrZXItcHJvamVjdEBpZXRmLm9yZzxtYWlsdG86ZGF0YXRyYWNrZXItcHJvamVjdEBpZXRmLm9y Zz4NCg0KUGxlYXNlIHJlcG9ydCB0b29scy5pZXRmLm9yZzxodHRwOi8vdG9vbHMuaWV0Zi5vcmc+ IGJ1Z3MgYXQNCmh0dHA6Ly90b29scy5pZXRmLm9yZy90b29scy9pc3N1ZXMNCm9yIHNlbmQgZW1h aWwgdG8gd2VibWFzdGVyQHRvb2xzLmlldGYub3JnPG1haWx0bzp3ZWJtYXN0ZXJAdG9vbHMuaWV0 Zi5vcmc+DQo= --_000_4A95BA014132FF49AE685FAB4B9F17F66B072B13sjceml521mbschi_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6 U2ltU3VuOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0 O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQFNpbVN1biI7DQoJ cGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0K cC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0K CW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5 OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNv LXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVu ZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0 eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVy bGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglm b250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCnNw YW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQt ZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERl ZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9 DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGlu IDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlv bjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVs dHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0t W2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlk bWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2Vu ZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9IiMwNTYzQzEiIHZsaW5r PSIjOTU0RjcyIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9y bWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+ PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGEgbmFtZT0iX01haWxFbmRDb21wb3NlIj48c3Bh biBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Sm9lLCA8bzpwPg0KPC9vOnA+PC9zcGFuPjwvYT48L3A+ DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4m bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9 ImNvbG9yOiMxRjQ5N0QiPllvdXIgcHJldmlvdXMgbWV0aG9kIG9mIHdlYiBjb252ZXJ0aW5nIGhh ZCB3b3JrZWQgc28gd2VsbCBmb3IgbGFzdCAxMCB5ZWFycy4NCjxvOnA+PC9vOnA+PC9zcGFuPjwv cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpw PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls ZT0iY29sb3I6IzFGNDk3RCI+QnV0IEkgYWx3YXlzIGdldCBlcnJvciB3aGVuIHVzaW5nIGNvbW1h bmQgbGluZSAod2l0aCBDeWd3aW4gaW5zdGFsbGVkKSwgbm9yIGNhbiBJIGdldCB0aGUgUGVybCB3 b3JraW5nIG9uIG15IERlbGwgbGFwdG9wLg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9v OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjoj MUY0OTdEIj5UaGFuayB5b3Ugc28gbXVjaCBmb3IgcHJvdmlkaW5nIHRoZSBjb252ZW5pZW5jZSBm b3IgYWxsIHRob3NlIHllYXJzLg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z b05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdE Ij5MaW5kYTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu IHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2 Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0 O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+RnJv bTo8L2I+IEpvZSBUb3VjaCBbbWFpbHRvOnRvdWNoQHN0cmF5YWxwaGEuY29tXSA8YnI+DQo8Yj5T ZW50OjwvYj4gRnJpZGF5LCBKdW5lIDIyLCAyMDE4IDE6MzYgUE08YnI+DQo8Yj5Ubzo8L2I+IExp bmRhIER1bmJhciAmbHQ7bGluZGEuZHVuYmFyQGh1YXdlaS5jb20mZ3Q7PGJyPg0KPGI+Q2M6PC9i PiB0b29scy1kaXNjdXNzQGlldGYub3JnPGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbVG9vbHMt ZGlzY3Vzc10gTmVlZCBJRVRGIHRvIG1haW50YWluIHRoZSB0b29sIHRvIGNvbnZlcnQgLlBSTiB0 byAqLnR4dDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhp IGFsbC4mbmJzcDs8c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdCI+PG86cD48L286cD48L3Nw YW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8 L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIHdpbGwgcGF0 IHRoZSBjb2RlIHRvIHRoZSBuZXcgd2Vic2l0ZSB0b2RheS4gVGhlIFBlcmwgY29kZSBuZWVkcyB0 byBiZSBydW4gYXMgd2VsbCAtIHRoZXJlIGFyZSBhIHZhcmlldHkgb2Ygd2F5cyB0byBkbyB0aGF0 IGluIGV2ZXJ5IE9TLiBJIGRvIG5vdCBleHBlY3QgdG8gc3VwcG9ydCBvbmxpbmUgcnVubmluZyBv ZiBqdXN0IHRoYXQgc2ltcGxlIFBlcmwgc2NyaXB0LiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9k aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8 L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Kb2U8bzpwPjwvbzpwPjwvcD4NCjwv ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEy LjBwdCI+PGJyPg0KT24gSnVuIDIyLCAyMDE4LCBhdCAxMToyMyBBTSwgTGluZGEgRHVuYmFyICZs dDs8YSBocmVmPSJtYWlsdG86bGluZGEuZHVuYmFyQGh1YXdlaS5jb20iPmxpbmRhLmR1bmJhckBo dWF3ZWkuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1 b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4N CjxwIGNsYXNzPSJNc29Ob3JtYWwiPknigJl2ZSBiZWVuIHVzaW5nIEpvZSBUb3VjaOKAmXMgdG9v bCB0byBjb252ZXJ0IC5wcm4gdG8gKi50eHQgZm9yIG1hbnkgeWVhcnMgZm9yIElFVEYgZHJhZnRz Lg0KPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsmbmJzcDtCdXQg aGlzIHdlYnNpdGUgcmVjZW50bHkgYmVpbmcgZm9yd2FyZGVkIHRvPG86cD48L286cD48L3A+DQo8 cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsgPGEgaHJlZj0iaHR0cHM6Ly93d3cuc3RyYXlhbHBo YS5jb20vdG9vbHMvIj5odHRwczovL3d3dy5zdHJheWFscGhhLmNvbS90b29scy88L2E+IHRoYXQg bm8gbG9uZ2VyIGhhcyB0aGUgbGluay48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt YWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7IENh biB5b3UgaGVscCB0byBmaW5kIGEgdG9vbCBmb3IgcGVvcGxlIHVzaW5nICouZG9jIGZvciBJRD8N CjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48 L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Xb3JkIGRvY3VtZW50IGlzIHNvIGVhc3kgZm9yIG11 bHRpcGxlIGF1dGhvcnMgdG8gd29yayB0b2dldGhlci48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz PSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+ Jm5ic3A7IFRoYW5rIHlvdSBzbyBtdWNoLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v cm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsg TGluZGEgRHVuYmFyPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8 bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9w Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1 LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48 c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcg Um9tYW4mcXVvdDssc2VyaWYiPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fPGJyPg0KVG9vbHMtZGlzY3VzcyBtYWlsaW5nIGxpc3Q8YnI+ DQo8YSBocmVmPSJtYWlsdG86VG9vbHMtZGlzY3Vzc0BpZXRmLm9yZyI+VG9vbHMtZGlzY3Vzc0Bp ZXRmLm9yZzwvYT48YnI+DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp c3RpbmZvL3Rvb2xzLWRpc2N1c3MiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGlu Zm8vdG9vbHMtZGlzY3VzczwvYT48YnI+DQo8YnI+DQpQbGVhc2UgcmVwb3J0IDxhIGhyZWY9Imh0 dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZyI+ZGF0YXRyYWNrZXIuaWV0Zi5vcmc8L2E+IGFuZCA8 YSBocmVmPSJodHRwOi8vbWFpbGFyY2hpdmUuaWV0Zi5vcmciPg0KbWFpbGFyY2hpdmUuaWV0Zi5v cmc8L2E+PGJyPg0KYnVncyBhdCA8YSBocmVmPSJodHRwOi8vdG9vbHMuaWV0Zi5vcmcvdG9vbHMv aWV0ZmRiIj5odHRwOi8vdG9vbHMuaWV0Zi5vcmcvdG9vbHMvaWV0ZmRiPC9hPjxicj4NCm9yIHNl bmQgZW1haWwgdG8gPGEgaHJlZj0ibWFpbHRvOmRhdGF0cmFja2VyLXByb2plY3RAaWV0Zi5vcmci PmRhdGF0cmFja2VyLXByb2plY3RAaWV0Zi5vcmc8L2E+PGJyPg0KPGJyPg0KUGxlYXNlIHJlcG9y dCA8YSBocmVmPSJodHRwOi8vdG9vbHMuaWV0Zi5vcmciPnRvb2xzLmlldGYub3JnPC9hPiBidWdz IGF0PGJyPg0KPGEgaHJlZj0iaHR0cDovL3Rvb2xzLmlldGYub3JnL3Rvb2xzL2lzc3VlcyI+aHR0 cDovL3Rvb2xzLmlldGYub3JnL3Rvb2xzL2lzc3VlczwvYT48YnI+DQpvciBzZW5kIGVtYWlsIHRv IDxhIGhyZWY9Im1haWx0bzp3ZWJtYXN0ZXJAdG9vbHMuaWV0Zi5vcmciPndlYm1hc3RlckB0b29s cy5pZXRmLm9yZzwvYT48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvYmxvY2txdW90 ZT4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K --_000_4A95BA014132FF49AE685FAB4B9F17F66B072B13sjceml521mbschi_-- From nobody Fri Jun 22 14:00:57 2018 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 03E12130EF2 for ; Fri, 22 Jun 2018 14:00:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vviCM-Yiy5GW for ; Fri, 22 Jun 2018 14:00:52 -0700 (PDT) Received: from oj.bangj.com (amt0.gin.ntt.net [129.250.11.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E60C7130EEB for ; Fri, 22 Jun 2018 14:00:51 -0700 (PDT) Received: from [10.46.144.157] (unknown [209.59.114.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id 4C2143E6; Fri, 22 Jun 2018 17:00:39 -0400 (EDT) From: Tom Pusateri Message-Id: <4701F12C-B3D1-4595-9FE5-9F652571D9E1@bangj.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_CE6424F7-BB0F-420B-AB93-9CB68EBA0CF7" Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Date: Fri, 22 Jun 2018 17:00:48 -0400 In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F66B072AF4@sjceml521-mbs.china.huawei.com> Cc: "tools-discuss@ietf.org" To: Linda Dunbar References: <4A95BA014132FF49AE685FAB4B9F17F66B072AF4@sjceml521-mbs.china.huawei.com> X-Mailer: Apple Mail (2.3445.8.2) Archived-At: Subject: Re: [Tools-discuss] Need IETF to maintain the tool to convert .PRN to *.txt X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2018 21:00:56 -0000 --Apple-Mail=_CE6424F7-BB0F-420B-AB93-9CB68EBA0CF7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 It=E2=80=99s pretty popular now to use markdown formatted documents for = internet drafts. These text files can easily be edited in shared editors = and don=E2=80=99t require proprietary tools like Word but possibly Word = could still be used (I don=E2=80=99t know how Word treats text files). = Then a markdown to XML converter and subsequently TXT, HTML, PDF, etc = formats can be generated. A popular one is kramdown-rfc2629 https://github.com/cabo/kramdown-rfc2629 It might be time to modernize your workflow. Tom > On Jun 22, 2018, at 2:23 PM, Linda Dunbar = wrote: >=20 > I=E2=80=99ve been using Joe Touch=E2=80=99s tool to convert .prn to = *.txt for many years for IETF drafts. > But his website recently being forwarded to > https://www.strayalpha.com/tools/ = that no longer has the link. > =20 > Can you help to find a tool for people using *.doc for ID? > =20 > Word document is so easy for multiple authors to work together. > =20 > Thank you so much. > =20 > Linda Dunbar > =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 = --Apple-Mail=_CE6424F7-BB0F-420B-AB93-9CB68EBA0CF7 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 It=E2=80=99s pretty popular now to use markdown formatted = documents for internet drafts. These text files can easily be edited in = shared editors and don=E2=80=99t require proprietary tools like Word but = possibly Word could still be used (I don=E2=80=99t know how Word treats = text files). Then a markdown to XML converter and subsequently TXT, = HTML, PDF, etc formats can be generated.

A popular one is = kramdown-rfc2629

https://github.com/cabo/kramdown-rfc2629

It might be time to modernize = your workflow.

Tom


On Jun 22, 2018, at 2:23 PM, Linda Dunbar = <linda.dunbar@huawei.com> wrote:

I=E2=80=99v= e been using Joe Touch=E2=80=99s tool to convert .prn to *.txt for many = years for IETF drafts.
  But his website recently being forwarded to
  https://www.strayalpha.com/tools/ that no longer has the = link.
 
  = Can you help to find a tool for people using *.doc for ID?
 
Word = document is so easy for multiple authors to work together.
 
  = Thank you so much.
 
  Linda Dunbar
 
 
___________________________________________________________
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

= --Apple-Mail=_CE6424F7-BB0F-420B-AB93-9CB68EBA0CF7-- From nobody Fri Jun 22 14:03:27 2018 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 3ABAA130EF1 for ; Fri, 22 Jun 2018 14:03:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JoQOXz8fsBL4 for ; Fri, 22 Jun 2018 14:03:23 -0700 (PDT) Received: from oj.bangj.com (amt0.gin.ntt.net [129.250.11.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AC26130EEB for ; Fri, 22 Jun 2018 14:03:22 -0700 (PDT) Received: from [10.46.144.157] (unknown [209.59.114.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id F1ADD3E9; Fri, 22 Jun 2018 17:03:10 -0400 (EDT) From: Tom Pusateri Message-Id: <59E653C0-0A12-4D0E-BE85-BE9408FDEE7B@bangj.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_68E59B4A-04C4-4214-9894-17E2C58FB809" Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Date: Fri, 22 Jun 2018 17:03:19 -0400 In-Reply-To: <4701F12C-B3D1-4595-9FE5-9F652571D9E1@bangj.com> Cc: "tools-discuss@ietf.org" To: Linda Dunbar References: <4A95BA014132FF49AE685FAB4B9F17F66B072AF4@sjceml521-mbs.china.huawei.com> <4701F12C-B3D1-4595-9FE5-9F652571D9E1@bangj.com> X-Mailer: Apple Mail (2.3445.8.2) Archived-At: Subject: Re: [Tools-discuss] Need IETF to maintain the tool to convert .PRN to *.txt X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2018 21:03:26 -0000 --Apple-Mail=_68E59B4A-04C4-4214-9894-17E2C58FB809 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I should also mention, it=E2=80=99s popular to put the source for = internet drafts on a shared repository like github. Then all = participants can see changes through commits and discuss changes with = issues and pull requests. Tom > On Jun 22, 2018, at 5:00 PM, Tom Pusateri wrote: >=20 > It=E2=80=99s pretty popular now to use markdown formatted documents = for internet drafts. These text files can easily be edited in shared = editors and don=E2=80=99t require proprietary tools like Word but = possibly Word could still be used (I don=E2=80=99t know how Word treats = text files). Then a markdown to XML converter and subsequently TXT, = HTML, PDF, etc formats can be generated. >=20 > A popular one is kramdown-rfc2629 >=20 > https://github.com/cabo/kramdown-rfc2629 = >=20 > It might be time to modernize your workflow. >=20 > Tom >=20 >=20 >> On Jun 22, 2018, at 2:23 PM, Linda Dunbar = wrote: >>=20 >> I=E2=80=99ve been using Joe Touch=E2=80=99s tool to convert .prn to = *.txt for many years for IETF drafts. >> But his website recently being forwarded to >> https://www.strayalpha.com/tools/ = that no longer has the link. >> =20 >> Can you help to find a tool for people using *.doc for ID? >> =20 >> Word document is so easy for multiple authors to work together. >> =20 >> Thank you so much. >> =20 >> Linda Dunbar >> =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 --Apple-Mail=_68E59B4A-04C4-4214-9894-17E2C58FB809 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 I = should also mention, it=E2=80=99s popular to put the source for internet = drafts on a shared repository like github. Then all participants can see = changes through commits and discuss changes with issues and pull = requests.

Tom


On Jun = 22, 2018, at 5:00 PM, Tom Pusateri <pusateri@bangj.com> = wrote:

It=E2=80=99s pretty = popular now to use markdown formatted documents for internet drafts. = These text files can easily be edited in shared editors and don=E2=80=99t = require proprietary tools like Word but possibly Word could still be = used (I don=E2=80=99t know how Word treats text files). Then a markdown = to XML converter and subsequently TXT, HTML, PDF, etc formats can be = generated.

A popular = one is kramdown-rfc2629

https://github.com/cabo/kramdown-rfc2629

It might be time to = modernize your workflow.

Tom


On Jun 22, 2018, at 2:23 PM, Linda Dunbar <linda.dunbar@huawei.com> wrote:

I=E2=80=99v= e been using Joe Touch=E2=80=99s tool to convert .prn to *.txt for many = years for IETF drafts.
  But his website recently being forwarded to
  https://www.strayalpha.com/tools/ that no longer has the = link.
 
  = Can you help to find a tool for people using *.doc for ID?
 
Word = document is so easy for multiple authors to work together.
 
  = Thank you so much.
 
  Linda Dunbar
 
 
___________________________________________________________
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

___________________________________________________= ________
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/issuesor send email to webmaster@tools.ietf.org

= --Apple-Mail=_68E59B4A-04C4-4214-9894-17E2C58FB809-- From nobody Tue Jun 26 23:25:49 2018 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 13F69130F3E for ; Tue, 26 Jun 2018 23:25:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z_BH3en9JuOY for ; Tue, 26 Jun 2018 23:25:46 -0700 (PDT) Received: from mail-ot0-x22c.google.com (mail-ot0-x22c.google.com [IPv6:2607:f8b0:4003:c0f::22c]) (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 3237D130E80 for ; Tue, 26 Jun 2018 23:25:46 -0700 (PDT) Received: by mail-ot0-x22c.google.com with SMTP id i19-v6so977221otk.10 for ; Tue, 26 Jun 2018 23:25:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=8t/YGMF/28kqgXNZ9cH7GfDVUKGSQKviAfRfTt3G/6c=; b=Ir1UFI5e36X60J4vNgKrKu9Uims0fLsFhG+0CUma4Awe/2std2eptmQa8n31OgaqtB akXvZ0JvtMkkcxOwIrtlSdfnCcIwBbpNVDlKkiH4U8p6dCJQeTy8sS8I3c2SdwLFaKtJ b9kQUHOI6HAqK6r2pncRdSxPnTXm3F/hd5Iy9rPUQLFoLQ/+vraUOmNqGEgC4BKySCGB cuNCDS+1jeAirY2k2AsWtpZXEkX1u8Y5MMeqcb905zWJ2FlKxpmvCigNOkBnBbmYA83b CIj1n5U+4vpmCpKw4zxgLUrfEAGy8q82dzDn8dJPS9PaZcz3AFx0pJAzHah+VaNCENIy nFxA== 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=8t/YGMF/28kqgXNZ9cH7GfDVUKGSQKviAfRfTt3G/6c=; b=OVv9aI2zSeCi5JRpPN4DqttRAwXv0TvLV/4PSWasIm4rP42XSg9wgQHM/Mfm3FiPZv QKbfxQApvMdH86e9yjT6x1+WjT2cGmxK9tA1hDTBOggGkwovn53i5X0/oyeuMfCjj+Wm 3Ual8GZ+xjj0nZ1uN4F8baHPtAbIFDJ3eTB5MB+46wlZF3afx1gIEa2bAb5GBjNcqKKX zYEobthxlYlBMu5o2lNv0UZ4jP5ObT+hcYPVdnK8//aY+bdxkWgZtA1S25Itih2TXsYm 5GqT0Ow1QTXZKj5b80kZUj2w9NERZ362aqBidbtCKQsQBv8Fzkai2Ws4pvh8X2oRih8r kHHQ== X-Gm-Message-State: APt69E3KhFgUGB7t6KAkc6LQQQOfU4vv//r/fhxB2AK8MzspgRkUvkD2 TqeX9Z4U0i28CQRAdJzWMOvayMJ/+n2gxDuoCQdkc4F+ X-Google-Smtp-Source: AAOMgpdCoWq5ybFTlSevAYcKh605IMuswd1K5IKxI8w6whtblmuAH3xEsSBj7CesAOJfHvLseCka3sx0IGX196jJAVc= X-Received: by 2002:a9d:2330:: with SMTP id j45-v6mr2793145otb.241.1530080745270; Tue, 26 Jun 2018 23:25:45 -0700 (PDT) MIME-Version: 1.0 From: Martin Thomson Date: Wed, 27 Jun 2018 16:25:35 +1000 Message-ID: To: "tools-discuss@ietf.org Discussion" Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [Tools-discuss] Error with NIST DOIs X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2018 06:25:48 -0000 I've been relying on the bibxml7 service (which is great) for citations the NIST SHA-2 and AES specs. This just stopped working. It's not all DOIs, because we have other citations that load properly. https://xml2rfc.tools.ietf.org/public/rfc/bibxml7/reference.DOI.10.6028/NIST.FIPS.180-4.xml now returns an HTTP 404 saying "invalid DOI or type". Earlier today it was returning XML: Secure Hash Standard https://doi.org/10.6028/NIST.FIPS.180-4 redirects to the specification. From nobody Tue Jun 26 23:41:36 2018 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 03BD212F1AC for ; Tue, 26 Jun 2018 23:41:34 -0700 (PDT) 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 6qV-BEWs3sLM for ; Tue, 26 Jun 2018 23:41:32 -0700 (PDT) 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 2C4D3129385 for ; Tue, 26 Jun 2018 23:41:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id w5R6fREC024029; Wed, 27 Jun 2018 08:41:27 +0200 (CEST) Received: from client-0109.vpn.uni-bremen.de (client-0109.vpn.uni-bremen.de [134.102.107.109]) (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 41Ftbp5kfpzDWpm; Wed, 27 Jun 2018 08:41:26 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) From: Carsten Bormann In-Reply-To: Date: Wed, 27 Jun 2018 08:41:26 +0200 Cc: "tools-discuss@ietf.org Discussion" , webmaster@tools.ietf.org X-Mao-Original-Outgoing-Id: 551774484.595181-a4a4ab2d16dbb66060402911430463b0 Content-Transfer-Encoding: quoted-printable Message-Id: <83979E0A-53EC-4A28-B55A-95C146370E2B@tzi.org> References: To: Martin Thomson X-Mailer: Apple Mail (2.3445.8.2) Archived-At: Subject: Re: [Tools-discuss] Error with NIST DOIs X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2018 06:41:34 -0000 On Jun 27, 2018, at 08:25, Martin Thomson = wrote: >=20 > https://doi.org/10.6028/NIST.FIPS.180-4 redirects to the = specification. The command line tool seems to work for this DOI: $ doilit 10.6028/NIST.FIPS.180-4 a: seriesinfo: National Institute of Standards and Technology: report DOI: 10.6028/nist.fips.180-4 title: Secure Hash Standard author: - name: Quynh H. Dang ins: Q. Dang date: 2015-07 So this looks like a bad cache copy to me. Maybe the generator behind this should not be so happy caching errors? (We are in the process of chasing down a weirdly broken cache copy in = the bibxml3 directory, so I=E2=80=99m having a deja vu here.) Gr=C3=BC=C3=9Fe, Carsten From nobody Wed Jun 27 05:11:08 2018 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 21A951277C8 for ; Wed, 27 Jun 2018 05:11:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 FITGD9zdsDTP for ; Wed, 27 Jun 2018 05:11:05 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45B74127598 for ; Wed, 27 Jun 2018 05:11:05 -0700 (PDT) Received: from h-99-61.a357.priv.bahnhof.se ([82.196.99.61]:64459 helo=[192.168.1.120]) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1fY9Hs-00027K-63; Wed, 27 Jun 2018 05:11:04 -0700 To: Martin Thomson , "tools-discuss@ietf.org Discussion" References: From: Henrik Levkowetz Message-ID: Date: Wed, 27 Jun 2018 14:10:57 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 82.196.99.61 X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, martin.thomson@gmail.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org) X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [Tools-discuss] Error with NIST DOIs X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2018 12:11:08 -0000 Hi Martin, This seems to be an issue with ruby on the server (for running doilit). I'm currently installing ruby 2.5.1, and will re-install rubygems, and verify that doilit runs properly again. Henrik On 2018-06-27 08:25, Martin Thomson wrote: > I've been relying on the bibxml7 service (which is great) for > citations the NIST SHA-2 and AES specs. > > This just stopped working. It's not all DOIs, because we have other > citations that load properly. > > https://xml2rfc.tools.ietf.org/public/rfc/bibxml7/reference.DOI.10.6028/NIST.FIPS.180-4.xml > now returns an HTTP 404 saying "invalid DOI or type". > > Earlier today it was returning XML: > > > > Secure Hash Standard > > > > > > value="report"/> > > > > https://doi.org/10.6028/NIST.FIPS.180-4 redirects to the specification. > > ___________________________________________________________ > 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 > From nobody Wed Jun 27 05:24:55 2018 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 E4F62127598 for ; Wed, 27 Jun 2018 05:24:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 ZV7NyoKE9H89 for ; Wed, 27 Jun 2018 05:24:51 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 254B41277C8 for ; Wed, 27 Jun 2018 05:24:51 -0700 (PDT) Received: from h-99-61.a357.priv.bahnhof.se ([82.196.99.61]:64493 helo=[192.168.1.120]) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1fY9VC-0002d2-Gh; Wed, 27 Jun 2018 05:24:50 -0700 To: Martin Thomson , "tools-discuss@ietf.org Discussion" References: From: Henrik Levkowetz Message-ID: <1abd2465-8e7f-c53b-845c-0af1ee23ed2c@levkowetz.com> Date: Wed, 27 Jun 2018 14:24:43 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 82.196.99.61 X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, martin.thomson@gmail.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org) X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [Tools-discuss] Error with NIST DOIs X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2018 12:24:54 -0000 Fixed. Henrik On 2018-06-27 14:10, Henrik Levkowetz wrote: > Hi Martin, > > This seems to be an issue with ruby on the server (for running doilit). > > I'm currently installing ruby 2.5.1, and will re-install rubygems, and > verify that doilit runs properly again. > > Henrik > > On 2018-06-27 08:25, Martin Thomson wrote: >> I've been relying on the bibxml7 service (which is great) for >> citations the NIST SHA-2 and AES specs. >> >> This just stopped working. It's not all DOIs, because we have other >> citations that load properly. >> >> https://xml2rfc.tools.ietf.org/public/rfc/bibxml7/reference.DOI.10.6028/NIST.FIPS.180-4.xml >> now returns an HTTP 404 saying "invalid DOI or type". >> >> Earlier today it was returning XML: >> >> >> >> Secure Hash Standard >> >> >> >> >> >> > value="report"/> >> >> >> >> https://doi.org/10.6028/NIST.FIPS.180-4 redirects to the specification. >> >> ___________________________________________________________ >> 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 >> > From nobody Wed Jun 27 15:08:01 2018 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 93AD5130E2C for ; Wed, 27 Jun 2018 15:07:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6GEy7NQ-ZN8Y for ; Wed, 27 Jun 2018 15:07:55 -0700 (PDT) Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (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 4BB48124BE5 for ; Wed, 27 Jun 2018 15:07:55 -0700 (PDT) Received: by mail-oi0-x22c.google.com with SMTP id x18-v6so3306526oie.10 for ; Wed, 27 Jun 2018 15:07:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6Ptb6F6oqewDdUvNF9xO5hsnuj6FHFRRo85szVW6d4k=; b=Rirz89OWngkAsDRcyQtWlhqz9tqnsZRsHedbDRI0R89d0key0E/kqOdDuovXNZ5e2t MrBVwopN4TXIEBoJRRHBdrtd5Sn+PgJGtnNl69kL5apS1Nq+nlLU00LExYxnIESIovmj 5g/FuAg68VNIlcayh/GB3UmZ21LYUIuEFjmbjPPYLn+zk7HjPm3tg6avdQO+k31yqYBb 4/h89295oj88KNi1K/6WamCgruaLsSL4fH3LPSVmlqeUOYAIGfcymMR1Yesu5rcyx4eg ACDU+gj0nNzCckzykSeVUWgmSRsCtnoL8iVp3PxfJDJrTTVYVzxFIZQ2czHiJIggeqnZ mRIg== 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=6Ptb6F6oqewDdUvNF9xO5hsnuj6FHFRRo85szVW6d4k=; b=MVDxlXjsSVaAFg1mgMIqJoQ35dTIPKITdy6DVyIr7rSPz4LfVm8AaoOxqQ2wfMs+sY XLtd+1LLzg4TiT/ufqi/cFoR2Pa8D8XH+vvJHx+FZBn6i0EoiYKEKgjBlUD39x85u2TI vm1yp80F2Ky1/wa1Xv+lBw+Bmb2/VV9MJ2awR/WeYcd4ERfIU7GpIl6uX46IKy/UzHwP tByAti1NIfdSvVC+GQUGQKKrLo3r5wqmg4TN57pGdl2NrcSxoODEGr9JBZkn9P5gCek9 3neQFq8CSeE5iODDgnPFVXDiiL36BGNPvWGgDIxlQSsMoRuMs9+cjcyw7qRZ8gppcJYB qYNA== X-Gm-Message-State: APt69E0GMEM/1Wf9oDiboqONUV6sEGJ1L36ufRpRSBxm+9dkV/+ilLkz DmPQuLBK8EuTEJJi2tWhsxcj715h82muM/iPGsg= X-Google-Smtp-Source: AAOMgpcoTh9m3dM9RNp+UOvkI14TISNnCAfz//vwe2StlO4Hlg5iuSy/ssFuiV4ovOWazes5JZ9xFXIUkKMn0wbS/tY= X-Received: by 2002:aca:745:: with SMTP id 66-v6mr4091943oih.295.1530137274586; Wed, 27 Jun 2018 15:07:54 -0700 (PDT) MIME-Version: 1.0 References: <1abd2465-8e7f-c53b-845c-0af1ee23ed2c@levkowetz.com> In-Reply-To: <1abd2465-8e7f-c53b-845c-0af1ee23ed2c@levkowetz.com> From: Martin Thomson Date: Thu, 28 Jun 2018 08:07:47 +1000 Message-ID: To: Henrik Levkowetz Cc: "tools-discuss@ietf.org Discussion" Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Tools-discuss] Error with NIST DOIs X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2018 22:07:58 -0000 Thanks Henrik! All working again. On Wed, Jun 27, 2018 at 10:24 PM Henrik Levkowetz wrote: > > Fixed. > > Henrik > > On 2018-06-27 14:10, Henrik Levkowetz wrote: > > Hi Martin, > > > > This seems to be an issue with ruby on the server (for running doilit). > > > > I'm currently installing ruby 2.5.1, and will re-install rubygems, and > > verify that doilit runs properly again. > > > > Henrik > > > > On 2018-06-27 08:25, Martin Thomson wrote: > >> I've been relying on the bibxml7 service (which is great) for > >> citations the NIST SHA-2 and AES specs. > >> > >> This just stopped working. It's not all DOIs, because we have other > >> citations that load properly. > >> > >> https://xml2rfc.tools.ietf.org/public/rfc/bibxml7/reference.DOI.10.6028/NIST.FIPS.180-4.xml > >> now returns an HTTP 404 saying "invalid DOI or type". > >> > >> Earlier today it was returning XML: > >> > >> > >> > >> Secure Hash Standard > >> > >> > >> > >> > >> > >> >> value="report"/> > >> > >> > >> > >> https://doi.org/10.6028/NIST.FIPS.180-4 redirects to the specification. > >> > >> ___________________________________________________________ > >> 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 > >> > > From nobody Wed Jun 27 15:20:47 2018 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 32BE8130E2E for ; Wed, 27 Jun 2018 15:20:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rY6d5x3MEboE for ; Wed, 27 Jun 2018 15:20:44 -0700 (PDT) Received: from mail-ot0-x235.google.com (mail-ot0-x235.google.com [IPv6:2607:f8b0:4003:c0f::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 E61FA130E2C for ; Wed, 27 Jun 2018 15:20:43 -0700 (PDT) Received: by mail-ot0-x235.google.com with SMTP id h6-v6so3945133otj.0 for ; Wed, 27 Jun 2018 15:20:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=BkuXmfCsxcRnXMApW1WzqhRaL4h/Cny/bBSZoQQSumY=; b=M9isL4vELogBzFbo2xNtMu8DsOTI3F4sE6k6AxTWhf52nwsH+QIKSWpkpiqqdg9//a DKF20J7W261Jh2S7R/IqSPxrYne/KlilKeja4C1E+jfiJ2SFvL06CNkQYwptHHgefJ0S LDRMHr/CYyFdbF4//Py7oGblZG+L6oDhA0M7JyA6dv9uVVgq06EnnWGV8Vpr9UElgTOV ZZ71MvD/+l6y5FjupoG2N3c4tZTnQfCA1JTdGiHFz4wC5rc+P8CdCX8JUZ+3Fj4Vj5u2 yo+EMTn+RFgDttMHn/eMic3OfiY6B0GXlqC87XfoB7IVhloTmNEsc7FqfpUp81jMJaSj 4ldA== 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=BkuXmfCsxcRnXMApW1WzqhRaL4h/Cny/bBSZoQQSumY=; b=sYToBy+X5inGmHyqgSf/ssBdKbkMOjwW/HKcxMuW9BobDlfblrKrIwCsKn1wR+5sgI Ry+TfwNKlyy2rDCePIx9xDSVHH30NM3gYxCBkLc7VnKRg2HDcktvbiUuT3rtVIkp4Yh+ 2gHSCFSV86NMzdk9UT7iqmIZmermyQU7Vc0XOmLDyyW2kEN7K2lLgxkN8ftdeb8YaULN t5Sqk5DFIGJ0R5KQ2lIcLr5ZYKUgAzrvPZZmK9jBxZfORnd6QeQbkSDnNgdr1CRrtdk1 T6oiLEdQSQs+hO03wiG4gW0MbsinsC27KRpWuMssvK8Pmst3C9aCkNyCYhYP9DCoznqj LdeA== X-Gm-Message-State: APt69E1p/SkObQt8BLsxEhsV7eSc38TN1Her35jENQjzfDFUiHNfsTP5 Xx0IrW325b4XoM/AZ7Znq1IgiJlh0KS6R4NGZWSadDmn X-Google-Smtp-Source: AAOMgpfowvYRHpfxQHk4SEiRxAvnsypHp3WFjBCP6ezAlrfb3XSjoqClxl9jy1S79grWPegyIIlFCm23sI3VSFD1n9w= X-Received: by 2002:a9d:5211:: with SMTP id e17-v6mr592716oth.396.1530138043110; Wed, 27 Jun 2018 15:20:43 -0700 (PDT) MIME-Version: 1.0 From: Martin Thomson Date: Thu, 28 Jun 2018 08:20:36 +1000 Message-ID: To: "tools-discuss@ietf.org Discussion" Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [Tools-discuss] Enable reply-all for draft announcements X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2018 22:20:46 -0000 (this might be the wrong venue, but it's what I came up with) I am probably not the only one doing this, but I tend to reply-all to draft announcements, especially for working group drafts to provide a bit of a summary of changes. Because i-d-announce@ietf.org (or internet-drafts@ietf.org) is on the CC, this results in me opening a ticket. I never want to do that. Sometimes I remember to trim the list of recipients, but I forget more often than not. Is there some mail hackery (Reply-To with a blackhole address, for instance) that can be used to avoid this happening? Do both of the mail aliases need to be on the CC? From nobody Thu Jun 28 08:17:04 2018 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 4BCE1130E27 for ; Thu, 28 Jun 2018 08:17:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.909 X-Spam-Level: X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.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 yrMS0077uU2b for ; Thu, 28 Jun 2018 08:16:57 -0700 (PDT) Received: from mail-wr0-x231.google.com (mail-wr0-x231.google.com [IPv6:2a00:1450:400c:c0c::231]) (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 15292130E71 for ; Thu, 28 Jun 2018 08:16:56 -0700 (PDT) Received: by mail-wr0-x231.google.com with SMTP id t6-v6so5894070wrq.13 for ; Thu, 28 Jun 2018 08:16:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4CFsRGdVgYlJPYQMWdJ+o6UMkQZIQ1UzWBp1Too340E=; b=tuAGefIPMpoQDMohYORza67zfsKZL9C1uVDYFn5Y3LtDDjGvjZ0YKgWkf3s9Zkk3qt fouxC5uVP7PPTIHPSFaS9FErjTt/n9jy6bNLKlaP3/iiYLxlBiUysfKzlEa++stzNvIA OOrI1CbhxQeJ5Q0PTKbvykZvwJkIILwal0aGInA9geUs/nSqFcxFRJgp7AdH7V8LP22e av39mwE2WVQxobvgRNsRZ5nRuzz6jI+1WEJD0rLpuK7ZtMebOPhwwikhvKHLZHpjNSI/ tcHUlF0CO8Ek3ZSjMdJci7RIUVd1FwCSnephZYTpV2uB6FM5m/LiXrv3lWf/0wX/31NS 6XeQ== 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=4CFsRGdVgYlJPYQMWdJ+o6UMkQZIQ1UzWBp1Too340E=; b=ZV3CVw+LF1smj+blbyNgFjHjPgEV/mS+aFqiz7kLC0QJudOp/3Wp4NhPWCWi7t6YCh dKjGtnL3hBUnNy/T35p/VRcnyHWY+cY6xMxkebgiDxKFRf/RdDAUsiVIV6CH/k9Mof6p Fpbe64e7onwT8MXK8QQaytClRIVjgGrwEseomQ2ShX5DrgyT3641cFSbsS4VNoU4LJMo 4cqzT4PltE+ta/jMoXpYDfFq0CoUihV/0riE4e8bkjmpazhceU1QD6fy3pp5Z10DcNB+ WU6Hgi9O4pgAnrYo2MFpXU6wlwnaosmQzN6njr7HfsGuLZXl0ZfUiG82Bf3kIDGa2gyR Mnuw== X-Gm-Message-State: APt69E2oCtTmwqApIizxwOQo0UQdNF+FZMlItlYbGzFPmgeviLG8ZgSN gj8C8z/daGQE//4ZWLNdYa+05S7X6tfYLgd1DgG3KTJA X-Google-Smtp-Source: AAOMgpdYfri2xsMtQ8QyNIPQNq6YZIbxnJCZvqrlaAyOh6Av6N+PkCIAAsZ06FKP5tU2rBV3+3PYdmKpxZE8nktXOCY= X-Received: by 2002:adf:ba01:: with SMTP id o1-v6mr9559993wrg.249.1530199015196; Thu, 28 Jun 2018 08:16:55 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Warren Kumari Date: Thu, 28 Jun 2018 10:16:18 -0500 Message-ID: To: Martin Thomson Cc: Tools Discussion Content-Type: multipart/alternative; boundary="000000000000bca146056fb53846" Archived-At: Subject: Re: [Tools-discuss] Enable reply-all for draft announcements X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2018 15:17:03 -0000 --000000000000bca146056fb53846 Content-Type: text/plain; charset="UTF-8" On Wed, Jun 27, 2018 at 5:20 PM Martin Thomson wrote: > (this might be the wrong venue, but it's what I came up with) > > I am probably not the only one doing this, but I tend to reply-all to > draft announcements, especially for working group drafts to provide a > bit of a summary of changes. Because i-d-announce@ietf.org (or > internet-drafts@ietf.org) is on the CC, this results in me opening a > ticket. > > I never want to do that. Sometimes I remember to trim the list of > recipients, but I forget more often than not. > > Wow, you sometimes remember? I always mean to, but basically never manage. This sounds like a great suggestion -- why are those there? It must get super annoying to keep closing those tickets. W > Is there some mail hackery (Reply-To with a blackhole address, for > instance) that can be used to avoid this happening? > > Do both of the mail aliases need to be on the CC? > > ___________________________________________________________ > 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 > -- I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf --000000000000bca146056fb53846 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On We= d, Jun 27, 2018 at 5:20 PM Martin Thomson <martin.thomson@gmail.com> wrote:
(this might be the wrong venue, but it's what I cam= e up with)

I am probably not the only one doing this, but I tend to reply-all to
draft announcements, especially for working group drafts to provide a
bit of a summary of changes.=C2=A0 Because i-d-announce@ietf.org (or
internet-draf= ts@ietf.org) is on the CC, this results in me opening a
ticket.

I never want to do that.=C2=A0 Sometimes I remember to trim the list of
recipients, but I forget more often than not.


Wow, you sometimes remember? I always mean = to, but basically never manage.

This sounds like a great suggest= ion -- why are those there? It must get super annoying to keep closing thos= e tickets.

W
=C2=A0
Is there some mail hackery (Reply-To with a blackhole address, for
instance) that can be used to avoid this happening?

Do both of the mail aliases need to be on the CC?

___________________________________________________________
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


--
I don't t= hink the execution is relevant when it was obviously a bad idea in the firs= t place.
This is like putting rabid weasels in your pants, and later exp= ressing regret at having chosen those particular rabid weasels and that pai= r of pants.
=C2=A0 =C2=A0---maf
--000000000000bca146056fb53846-- From nobody Fri Jun 29 10:16:38 2018 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 50A91130DDD for ; Fri, 29 Jun 2018 10:16:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.879 X-Spam-Level: X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 b_pl-T6HKiEM for ; Fri, 29 Jun 2018 10:16:34 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56D88130DDB for ; Fri, 29 Jun 2018 10:16:34 -0700 (PDT) Received: from unescapeable.local ([47.186.17.148]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w5THGWn3008964 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 29 Jun 2018 12:16:32 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host [47.186.17.148] claimed to be unescapeable.local To: tools-discuss@ietf.org References: From: Robert Sparks Message-ID: <2dad6a3e-ed2e-f00f-7b89-ddbb113cfd21@nostrum.com> Date: Fri, 29 Jun 2018 12:16:32 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------4A2AC769CCD2B0006B0D8E1F" Content-Language: en-US Archived-At: Subject: Re: [Tools-discuss] Enable reply-all for draft announcements X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jun 2018 17:16:36 -0000 This is a multi-part message in MIME format. --------------4A2AC769CCD2B0006B0D8E1F Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit This should be straightforward to implement - see . Should be an easy sprint task. I've created ticket RjS On 6/28/18 10:16 AM, Warren Kumari wrote: > > > On Wed, Jun 27, 2018 at 5:20 PM Martin Thomson > > wrote: > > (this might be the wrong venue, but it's what I came up with) > > I am probably not the only one doing this, but I tend to reply-all to > draft announcements, especially for working group drafts to provide a > bit of a summary of changes.  Because i-d-announce@ietf.org > (or > internet-drafts@ietf.org ) is on > the CC, this results in me opening a > ticket. > > I never want to do that.  Sometimes I remember to trim the list of > recipients, but I forget more often than not. > > > Wow, you sometimes remember? I always mean to, but basically never manage. > > This sounds like a great suggestion -- why are those there? It must > get super annoying to keep closing those tickets. > > W > > Is there some mail hackery (Reply-To with a blackhole address, for > instance) that can be used to avoid this happening? > > Do both of the mail aliases need to be on the CC? > > ___________________________________________________________ > 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 > > > > > -- > I don't think the execution is relevant when it was obviously a bad > idea in the first place. > This is like putting rabid weasels in your pants, and later expressing > regret at having chosen those particular rabid weasels and that pair > of pants. >    ---maf > > > ___________________________________________________________ > 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 --------------4A2AC769CCD2B0006B0D8E1F Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

This should be straightforward to implement - see <https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/ietf/submit/mail.py#L97>. Should be an easy sprint task.

I've created ticket <https://trac.tools.ietf.org/tools/ietfdb/ticket/2530>

RjS


On 6/28/18 10:16 AM, Warren Kumari wrote:


On Wed, Jun 27, 2018 at 5:20 PM Martin Thomson <martin.thomson@gmail.com> wrote:
(this might be the wrong venue, but it's what I came up with)

I am probably not the only one doing this, but I tend to reply-all to
draft announcements, especially for working group drafts to provide a
bit of a summary of changes.  Because i-d-announce@ietf.org (or
internet-drafts@ietf.org) is on the CC, this results in me opening a
ticket.

I never want to do that.  Sometimes I remember to trim the list of
recipients, but I forget more often than not.


Wow, you sometimes remember? I always mean to, but basically never manage.

This sounds like a great suggestion -- why are those there? It must get super annoying to keep closing those tickets.

W
 
Is there some mail hackery (Reply-To with a blackhole address, for
instance) that can be used to avoid this happening?

Do both of the mail aliases need to be on the CC?

___________________________________________________________
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


--
I don't think the execution is relevant when it was obviously a bad idea in the first place.
This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants.
   ---maf


___________________________________________________________
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

--------------4A2AC769CCD2B0006B0D8E1F-- From nobody Fri Jun 29 11:16:38 2018 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 D9344130E19 for ; Fri, 29 Jun 2018 11:16:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] 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 Msz8JpeLZCDY for ; Fri, 29 Jun 2018 11:16:34 -0700 (PDT) Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF372130DEB for ; Fri, 29 Jun 2018 11:16:33 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id D7D06300A2A for ; Fri, 29 Jun 2018 14:16:31 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail.smeinc.net Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id rIH4tp0iUmhk for ; Fri, 29 Jun 2018 14:16:29 -0400 (EDT) Received: from a860b60074bd.home (pool-71-127-50-4.washdc.fios.verizon.net [71.127.50.4]) by mail.smeinc.net (Postfix) with ESMTPSA id C63A930025C; Fri, 29 Jun 2018 14:16:29 -0400 (EDT) From: Russ Housley Message-Id: <1C59282D-5EE6-4191-9426-E2A55B598B75@vigilsec.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_7B568507-6CAD-4D82-A26A-BB71867D1921" Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Date: Fri, 29 Jun 2018 14:16:30 -0400 In-Reply-To: <2dad6a3e-ed2e-f00f-7b89-ddbb113cfd21@nostrum.com> Cc: tools-discuss@ietf.org To: Robert Sparks References: <2dad6a3e-ed2e-f00f-7b89-ddbb113cfd21@nostrum.com> X-Mailer: Apple Mail (2.3445.8.2) Archived-At: Subject: Re: [Tools-discuss] Enable reply-all for draft announcements X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jun 2018 18:16:37 -0000 --Apple-Mail=_7B568507-6CAD-4D82-A26A-BB71867D1921 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii That one is too easy to let wait for the code sprint. I just offered a = commit. Russ > On Jun 29, 2018, at 1:16 PM, Robert Sparks = wrote: >=20 > This should be straightforward to implement - see = = . Should be an easy sprint task. >=20 > I've created ticket = = > RjS >=20 > On 6/28/18 10:16 AM, Warren Kumari wrote: >>=20 >>=20 >> On Wed, Jun 27, 2018 at 5:20 PM Martin Thomson = > wrote: >> (this might be the wrong venue, but it's what I came up with) >>=20 >> I am probably not the only one doing this, but I tend to reply-all to >> draft announcements, especially for working group drafts to provide a >> bit of a summary of changes. Because i-d-announce@ietf.org = (or >> internet-drafts@ietf.org ) is on the = CC, this results in me opening a >> ticket. >>=20 >> I never want to do that. Sometimes I remember to trim the list of >> recipients, but I forget more often than not. >>=20 >>=20 >> Wow, you sometimes remember? I always mean to, but basically never = manage. >>=20 >> This sounds like a great suggestion -- why are those there? It must = get super annoying to keep closing those tickets. >>=20 >> W >> =20 >> Is there some mail hackery (Reply-To with a blackhole address, for >> instance) that can be used to avoid this happening? >>=20 >> Do both of the mail aliases need to be on the CC? >>=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 >>=20 >> --=20 >> I don't think the execution is relevant when it was obviously a bad = idea in the first place. >> This is like putting rabid weasels in your pants, and later = expressing regret at having chosen those particular rabid weasels and = that pair of pants. >> ---maf >>=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 > ___________________________________________________________ > 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 --Apple-Mail=_7B568507-6CAD-4D82-A26A-BB71867D1921 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii That one is too easy to let wait for the code sprint.  I just offered a commit.

Russ

On Jun 29, 2018, at 1:16 PM, Robert Sparks <rjsparks@nostrum.com> wrote:

This should be straightforward to implement - see <https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/ietf/submit/mail.py#L97>. Should be an easy sprint task.

I've created ticket <https://trac.tools.ietf.org/tools/ietfdb/ticket/2530>

RjS


On 6/28/18 10:16 AM, Warren Kumari wrote:


On Wed, Jun 27, 2018 at 5:20 PM Martin Thomson <martin.thomson@gmail.com> wrote:
(this might be the wrong venue, but it's what I came up with)

I am probably not the only one doing this, but I tend to reply-all to
draft announcements, especially for working group drafts to provide a
bit of a summary of changes.  Because i-d-announce@ietf.org (or
internet-drafts@ietf.org) is on the CC, this results in me opening a
ticket.

I never want to do that.  Sometimes I remember to trim the list of
recipients, but I forget more often than not.


Wow, you sometimes remember? I always mean to, but basically never manage.

This sounds like a great suggestion -- why are those there? It must get super annoying to keep closing those tickets.

W
 
Is there some mail hackery (Reply-To with a blackhole address, for
instance) that can be used to avoid this happening?

Do both of the mail aliases need to be on the CC?

___________________________________________________________
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


--
I don't think the execution is relevant when it was obviously a bad idea in the first place.
This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants.
   ---maf


___________________________________________________________
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

___________________________________________________________
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

--Apple-Mail=_7B568507-6CAD-4D82-A26A-BB71867D1921--