From nobody Mon Mar 4 02:38:39 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CFDD13111C for ; Mon, 4 Mar 2019 02:38:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, TVD_SPACE_RATIO=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 fxTYGN_YvsPb for ; Mon, 4 Mar 2019 02:38:36 -0800 (PST) Received: from mail-it1-x129.google.com (mail-it1-x129.google.com [IPv6:2607:f8b0:4864:20::129]) (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 2A8B4131116 for ; Mon, 4 Mar 2019 02:38:36 -0800 (PST) Received: by mail-it1-x129.google.com with SMTP id e24so6573544itl.1 for ; Mon, 04 Mar 2019 02:38:36 -0800 (PST) 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=w+CQZYBPsZ2vncvmnxY6QjFd3B/pOsmrKUxTpgXrtzg=; b=CVtlBpejhYKrLGoKhFmpHLg200+AroAP+YnVeZFCpQDWASJ2U55u6OIF8LwPhVnYxI WUcT5kD8nf54zEJz4sXq4jKFFZzYsu2wRkhp8kdFFbLBRNQjwfhaXzbmaj/6/I3rSZJN VURXXG2pAr5it/C37KIO7VvxXq8/HUJSUr3YOBx/x6iVDA3B1rMl70L3VVJpkL4LUl0z nSUsI3A5XWPXvvY18owGbAUyYBmIfIH+FOQUfFs+0G+t2q5rcPK8xFW5wnBuPC8oCStg otY7YYA49UT2F331lhR7xMvbdQd/zeRdXkbsF6HjEPFv0wLZ0vl5M1btvUKpvAeUMnTP 5NgA== 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=w+CQZYBPsZ2vncvmnxY6QjFd3B/pOsmrKUxTpgXrtzg=; b=hc+IKF0OZVMnm1U8f0Ld3MdKtdvBJ/hJMVO2sOjgmdy+nqKLJ1qnyppBGbdoR1weqx QzVW9a5ol9hcI2XV5UxYZfAtHxz6e+AUd/pCjKGoIKCZ7RJSVE2A2uw4WNJQxb60behZ mGUMTK59qYArrFYUmnP9JPQByYHZpBmLDBOY9kexOUrAQZfGOPcfA/tA73D3/ADvvmez lPheiiV6oUKYLulHTEL2B57FfoUQI6+pF5JN3Z75bkjccX2x4aRbxJgWd90VyjOJTzqq n3njqFLfhXwlPRtlzEAHXAF5EvgpqieAi4DuCmeWf4zHBGuhweKgGiWMDqpwqhn4eToe zpWQ== X-Gm-Message-State: APjAAAXBZAZkNpVtJmnVjw8DJUSEyFDP2YP5JQYR437ifOLmjakNx9iF JfB4Ohft4/6yMFv+yDvs57g+ECEfIvlkQxQ+Rc4ZvTStXOw= X-Google-Smtp-Source: APXvYqzEFPE+tj+KRuZKwwBybGnZexB3TFsTSdqNmqVe19mu04BgReDifMWghQz3JP8fSyuudWliu1W+2z6cAVKlfYc= X-Received: by 2002:a24:16d4:: with SMTP id a203mr8438228ita.52.1551695915152; Mon, 04 Mar 2019 02:38:35 -0800 (PST) MIME-Version: 1.0 From: "start.default. page" Date: Mon, 4 Mar 2019 18:38:22 +0800 Message-ID: To: tools-discuss@ietf.org Content-Type: multipart/alternative; boundary="000000000000d2817c0583425be7" Archived-At: Subject: [Tools-discuss] Rfcmarkup-1.129 feedback X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Mar 2019 10:38:37 -0000 --000000000000d2817c0583425be7 Content-Type: text/plain; charset="UTF-8" Example.com --000000000000d2817c0583425be7 Content-Type: text/html; charset="UTF-8"
Example.com
--000000000000d2817c0583425be7-- From nobody Mon Mar 4 02:40:04 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FB68131123 for ; Mon, 4 Mar 2019 02:40:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, TVD_SPACE_RATIO=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 XRCJIHiDI4uM for ; Mon, 4 Mar 2019 02:40:01 -0800 (PST) Received: from mail-it1-x131.google.com (mail-it1-x131.google.com [IPv6:2607:f8b0:4864:20::131]) (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 3BAF7131122 for ; Mon, 4 Mar 2019 02:40:01 -0800 (PST) Received: by mail-it1-x131.google.com with SMTP id z124so6831174itc.2 for ; Mon, 04 Mar 2019 02:40:01 -0800 (PST) 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=MPoO31bf52QmAo8M8DPo/3K/1F61kFiN0Jto6ph2wcQ=; b=GCbC1peEzfj7j0N3HkM2K6wO/ZB2Batq4yu/ypOs9mrOVauXhsN4kxI54hKaAZfPwv sMTvTBbnGBL0+5OfOvEWo61SkGU2OU/GHYjAEumMe+xXLthv+6EQ0vzPVw2kqGRQsgAN QaBRZoSmkkZWhcg+9eC1WwJ74qKrN4dBQNerdAV3kXitzwE/nrI5XgWwZ87q3qXKUcgb 75sbjtkDuqpKpAp+17PQrzcCNeidnOD03863GY7QH9SHBBO9hs4Q5bmHIAQnigxRwyk3 JEYaPvRVOd2aoaJXSAuH/W8SY+ouahuPx6oMWWeBVezbNwqm1FTu6yPnVLZaJnq5E1Ia C/ug== 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=MPoO31bf52QmAo8M8DPo/3K/1F61kFiN0Jto6ph2wcQ=; b=Inn/Yvls841BzD7sztlZTasm1O5IvQFrF2ZCe/Djf4lzQtHipbk3l1CkYTT2zLvolM Xwhm9x5xqHHqnHhWsHJALpmaI1mY0pY70SqFdBusSK23Ar5sh1ZKoMv8UIRi9R0/kEWC yu7Gc98TIOZjun3lmbLzEo8Dluqb1DwBOilOb/M8kjMpclM5tZlrXoriGnqEUx3pP0MX 3ivZcEWNAip28/MfzYDU/1mu7E2dSQ/rUB2Ay7y2s5cBPdQTzP6hK0Nig1pVYjDQMGJ4 HieaV8QBErXcUXedE4bOu7hGN8NPALjV/gIh15UZWXGKhVrdCo8jq2JnB9re+2ffi059 IQlQ== X-Gm-Message-State: APjAAAXTL86WEAOfM8tTPKhuiZKj00bQ3lgVSCqK58oah8QOEDMJkaiV 6e8Vnra5Q/0v1d0UVPdvUkn60MiCOv/OCSB8kg6kAYP0fzI= X-Google-Smtp-Source: APXvYqy5J5qyj5OoLTBTny1e//5vWP7rABtbTxKyLiPUU777N8eUaQ51+Ss8eiBMYnLeX4mAVXl9MdjwEGPpSzIFXBA= X-Received: by 2002:a24:16d4:: with SMTP id a203mr8440104ita.52.1551696000295; Mon, 04 Mar 2019 02:40:00 -0800 (PST) MIME-Version: 1.0 From: "start.default. page" Date: Mon, 4 Mar 2019 18:39:48 +0800 Message-ID: To: tools-discuss@ietf.org Content-Type: multipart/alternative; boundary="000000000000e5aadc058342605d" Archived-At: Subject: [Tools-discuss] Rfcmarkup-1.129 feedback X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Mar 2019 10:40:02 -0000 --000000000000e5aadc058342605d Content-Type: text/plain; charset="UTF-8" --000000000000e5aadc058342605d Content-Type: text/html; charset="UTF-8"
--000000000000e5aadc058342605d-- From nobody Mon Mar 4 02:55:45 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A20DC131147 for ; Mon, 4 Mar 2019 02:55:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, TVD_SPACE_RATIO=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 XG5NIxaDJgLw for ; Mon, 4 Mar 2019 02:55:41 -0800 (PST) Received: from mail-it1-x134.google.com (mail-it1-x134.google.com [IPv6:2607:f8b0:4864:20::134]) (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 8D823131146 for ; Mon, 4 Mar 2019 02:55:41 -0800 (PST) Received: by mail-it1-x134.google.com with SMTP id m137so6631744ita.0 for ; Mon, 04 Mar 2019 02:55:41 -0800 (PST) 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=3otWDDzE1zPWXdOA+uiyZRQTx0CsWYlVnC7u+VN/boE=; b=Wx75KHvIFiZsQoJuzOpcjCble1ejBUEWw/DTQahr2M99Zo72X9BAsQDPuWKNQ+w1pl 4Uv8XFYZCCDn4fs6wEweqY0ipnUYT324dpe82eXucTuvjdwJN7/9sXnNQOrHBWFey5z+ MyC4BJvFcOlMSdQGjxWo0QPPAVmF8Dr2mtRoinVALFVMNBPs2IZQrjz3cTPrsoi/h2gx PbxzR8ocYt/8RHL0prq/vL2ohBcBceOjGjx1F9funODY9dc0zSTDruoEOgUCIGYvASd3 XpjEVAOPNRzMblnCnfqNOku0cxI+zvrswcv1lCRJfvINg6YvTk0ytujBctjPjxd29eLY fUaQ== 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=3otWDDzE1zPWXdOA+uiyZRQTx0CsWYlVnC7u+VN/boE=; b=mZlzQ72COnXuSrAimvzbvgWoxC+iQmFuz/11dp7fuE3UJRRyPclAKxbMuQt696HkFI FrKrJl2PgsULysTQlchNy/89DEOG8ZQC4GSGTNitcsOmXp9bkTARiZau6EM43nyh9y1R 3wSEGcGBPzW5+leajfMMKLcH0lyHipnTn0s/4BaegM15SHIYq5oyJKcu6xtJsfzFCAlx NKcZFdOP1wGSd11D0bKFaXNWLY1vUPSKnAJE8MOEm+FoMRt70NqIWDcR7PKOgqF67IXF eA5ObC25A5MWRCaqjgdshHfB4iSkZlR08e83jIkxZJkT7ykSsinVQQ09K6vCk0EZrgM0 g+gw== X-Gm-Message-State: APjAAAWQum8BuYJQ06vKsdphZb0kfJnhLoYONMTK1tUZBDZEj9dXBDNk TTPL+92tCbBKJ4MLyC2KBC6wW17vRzhmFuO3JL3x0S4grnI= X-Google-Smtp-Source: APXvYqwJ3RKbm3Vajq1IjVpKbCt+rDHCXVrtzJV+7aIay/xFTKG7Lmkx/rqTG5/XPY0GcReRUXFM9GbLtERhwwts+UM= X-Received: by 2002:a24:16d4:: with SMTP id a203mr8460684ita.52.1551696940467; Mon, 04 Mar 2019 02:55:40 -0800 (PST) MIME-Version: 1.0 From: "start.default. page" Date: Mon, 4 Mar 2019 18:55:26 +0800 Message-ID: To: tools-discuss@ietf.org Content-Type: multipart/alternative; boundary="000000000000ef8eb905834298d1" Archived-At: Subject: [Tools-discuss] Feedback X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Mar 2019 10:55:43 -0000 --000000000000ef8eb905834298d1 Content-Type: text/plain; charset="UTF-8" #Tags --000000000000ef8eb905834298d1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable



#Tags=
=C2=A0=C2=A0=C2=A0
--000000000000ef8eb905834298d1-- From nobody Mon Mar 4 15:36:41 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D8571311FC for ; Mon, 4 Mar 2019 15:36:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 BltXm-nPzaYg for ; Mon, 4 Mar 2019 15:36:37 -0800 (PST) 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 DB00F13120A for ; Mon, 4 Mar 2019 15:36:36 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id D775F3004AA for ; Mon, 4 Mar 2019 18:18:18 -0500 (EST) 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 J9nA_fWzRPlw for ; Mon, 4 Mar 2019 18:18:17 -0500 (EST) Received: from a860b60074bd.fios-router.home (unknown [138.88.156.37]) by mail.smeinc.net (Postfix) with ESMTPSA id 0319D300250 for ; Mon, 4 Mar 2019 18:18:16 -0500 (EST) From: Russ Housley Content-Type: multipart/signed; boundary="Apple-Mail=_55E8D243-C4E9-4FD4-9445-3289422823B6"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Message-Id: References: To: Tools Discussion Date: Mon, 4 Mar 2019 18:36:32 -0500 X-Mailer: Apple Mail (2.3445.102.3) Archived-At: Subject: [Tools-discuss] New tool: Using Emacs Org Mode for writing RFCs X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Mar 2019 23:36:40 -0000 --Apple-Mail=_55E8D243-C4E9-4FD4-9445-3289422823B6 Content-Type: multipart/alternative; boundary="Apple-Mail=_263FE772-8D83-4BF6-BFA2-B3A7E80FCFF6" --Apple-Mail=_263FE772-8D83-4BF6-BFA2-B3A7E80FCFF6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii FYI > From: Christian Hopps > Subject: New tool: Using Emacs Org Mode for writing RFCs > Date: March 4, 2019 at 6:19:20 PM EST > To: "ietf\@ietf.org" >=20 >=20 > Check it out: https://github.com/choppsv1/org-rfc-export >=20 > If you are an Emacs user, especially one who is familiar with/uses Org = Mode, I think you'll like this. >=20 > I've been working on an org mode exporter for writing RFCs. As it's = now in MELPA (package: ox-rfc) I figured it was a good time to announce = it's availability. Basically you write your RFC in Org Mode and export = it to XML. The back-end supports exporting to XML (for manual xml2rfc), = but also supports exporting to text, HTML, or PDF, including directly = into a buffer for easy previewing. >=20 > Highlights: > - Powerful Org Mode > - Simple Citations/References. > - Lists (Numbered, Unnumbered) > - Definition Lists (term + definition) > - Tables > - Embedded Code (Literate Programming e.g., embed yang model, trees, = examples) >=20 > In particular YANG embedding is pretty neat. There's no need for = separate files and tree generation (and example validation) can be = automated from the embedded text. >=20 > Check out the README and the examples (currently in the ert-tests = directory). >=20 > Thanks, > Chris. --Apple-Mail=_263FE772-8D83-4BF6-BFA2-B3A7E80FCFF6 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii FYI

From: Christian Hopps <chopps@chopps.org>
Subject: New tool: Using Emacs Org Mode for writing RFCs
Date: = March 4, 2019 at 6:19:20 PM = EST
To: = "ietf\@ietf.org" <ietf@ietf.org>

Check it out: https://github.com/choppsv1/org-rfc-export

If you are an Emacs user, especially one who = is familiar with/uses Org Mode, I think you'll like this.

I've been working on an org mode exporter for = writing RFCs. As it's now in MELPA (package: ox-rfc) I figured it was a = good time to announce it's availability. Basically you write your RFC in = Org Mode and export it to XML. The back-end supports exporting to XML = (for manual xml2rfc), but also supports exporting to text, HTML, or PDF, = including directly into a buffer for easy previewing.

Highlights:
- Powerful Org Mode
- = Simple Citations/References.
- Lists (Numbered, = Unnumbered)
- Definition Lists (term + definition)
- Tables
- Embedded Code (Literate Programming = e.g., embed yang model, trees, examples)

In = particular YANG embedding is pretty neat. There's no need for separate = files and tree generation (and example validation) can be automated from = the embedded text.

Check out the README and = the examples (currently in the ert-tests directory).

Thanks,
Chris.

= --Apple-Mail=_263FE772-8D83-4BF6-BFA2-B3A7E80FCFF6-- --Apple-Mail=_55E8D243-C4E9-4FD4-9445-3289422823B6 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iF0EARECAB0WIQRJuTEKFXbtfFQz5huK5O7Q9ZwRywUCXH22gAAKCRCK5O7Q9ZwR y7pDAJ9W0vddC0jgm91lGey18m8FHv4yXwCeLG6v4agjnaDQ9ZOXJ7BuobKetPE= =1WEU -----END PGP SIGNATURE----- --Apple-Mail=_55E8D243-C4E9-4FD4-9445-3289422823B6-- From nobody Mon Mar 4 19:25:00 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A99B2130EE0 for ; Mon, 4 Mar 2019 19:24:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LfcVHJ3cOxgB for ; Mon, 4 Mar 2019 19:24:48 -0800 (PST) Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (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 52725130EBB for ; Mon, 4 Mar 2019 19:24:48 -0800 (PST) Received: by mail-qt1-x82a.google.com with SMTP id a48so7592694qtb.4 for ; Mon, 04 Mar 2019 19:24:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=J5Dd4ovyL6vXxoKSnYmKP3rY5vhT/yoo2v9FrEdjUPA=; b=aMuHvRMxmT5kXGmtPjDrZGDCSwIO8GCaKT4n+32Y+6/Knil1vYHxUmrBDtCakm0V0V ssLY0pnL3PzV+UfCt5ZizR5uvZDFOSYOS8peJcU0U+9mWRYkytGxGsEtG0OXklIuTl9Y sQQcmqHxjEF7IWaNX3euSvBnnM3GV6qjJ+QXTpKGzTKxFniqqSTZcX30y3qFI2J1ALTY WDxqtkYeiT+nFBcNcrzF90uszNG71HYK/wzRBF64pD/Of8xloPVKeqXQqNJ8xAIVr7FW tEBR7fGcA1241qcqoqLeqSEAX1+brwbD6RBsor2sm57V2N1neNB53Ju5xi3c2GswOGnP SGTw== 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=J5Dd4ovyL6vXxoKSnYmKP3rY5vhT/yoo2v9FrEdjUPA=; b=VMlRImfyi/Tg5YiikGO/gWLCMgxVB5fD8D9vEVLDG5qC+edKxp0fPDRCp67xjtp2jw rGcy2osNjDmQ+hCeZM15+TI8bqUnmNeOJfNwfa7kZgVV7a+ahCWoAOdRa/P+d2MzeXHL fMnTPVbunDD8DtUK+vT+BPSlCU3IuA5gR66cBM2NNX94cAlUiQ1cqxCD+BnDcBnjMXu4 HzMTpLDZ7W5ctiJnDQQ4APOXHa2ZzCAKUrwB0I1K5pVPALGrHMzXarRUamw8LpltYXKu JivWFQLlI30buH2RoXiKaVqiKGU67hQ4PVir1LBid3oywI3diF3BsRPf5QcXNB5KJZh9 AUvw== X-Gm-Message-State: APjAAAVT7s11UzMp43+xtCbVeTgxe9rjk8eZUykA7+CwvnG3BOWc0l4G 1pYornZ3ZRyLkpCgIan6J1JVBGf4RbnLzVkH+D0hV6q6 X-Google-Smtp-Source: APXvYqzQf8IoHOH45g8xOXj4jzwEvZjnybr34Cp1IUlNvJBmzgiJMQaHvhQ6s+5J3TQMXCw2pgVTAFYv4WpkvnPPItM= X-Received: by 2002:ac8:2a82:: with SMTP id b2mr17245981qta.375.1551756286997; Mon, 04 Mar 2019 19:24:46 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Richard Barnes Date: Mon, 4 Mar 2019 22:24:24 -0500 Message-ID: To: Russ Housley Cc: Tools Discussion Content-Type: multipart/alternative; boundary="00000000000043b85f0583506a3c" Archived-At: Subject: Re: [Tools-discuss] New tool: Using Emacs Org Mode for writing RFCs X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Mar 2019 03:24:58 -0000 --00000000000043b85f0583506a3c Content-Type: text/plain; charset="UTF-8" Is there a brief answer to the question of what advantage this has over Markdown, which has its own Emacs mode? https://jblevins.org/projects/markdown-mode/ On Mon, Mar 4, 2019 at 6:36 PM Russ Housley wrote: > FYI > > *From: *Christian Hopps > *Subject: **New tool: Using Emacs Org Mode for writing RFCs* > *Date: *March 4, 2019 at 6:19:20 PM EST > *To: *"ietf\@ietf.org" > > > Check it out: https://github.com/choppsv1/org-rfc-export > > If you are an Emacs user, especially one who is familiar with/uses Org > Mode, I think you'll like this. > > I've been working on an org mode exporter for writing RFCs. As it's now in > MELPA (package: ox-rfc) I figured it was a good time to announce it's > availability. Basically you write your RFC in Org Mode and export it to > XML. The back-end supports exporting to XML (for manual xml2rfc), but also > supports exporting to text, HTML, or PDF, including directly into a buffer > for easy previewing. > > Highlights: > - Powerful Org Mode > - Simple Citations/References. > - Lists (Numbered, Unnumbered) > - Definition Lists (term + definition) > - Tables > - Embedded Code (Literate Programming e.g., embed yang model, trees, > examples) > > In particular YANG embedding is pretty neat. There's no need for separate > files and tree generation (and example validation) can be automated from > the embedded text. > > Check out the README and the examples (currently in the ert-tests > directory). > > Thanks, > Chris. > > > ___________________________________________________________ > 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 > --00000000000043b85f0583506a3c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Is there a brief answer to the question o= f what advantage this has over Markdown, which has its own Emacs mode?
=

On Mon, Mar 4,= 2019 at 6:36 PM Russ Housley <h= ousley@vigilsec.com> wrote:
FYI
From: <= span style=3D"font-family:-webkit-system-font,"Helvetica Neue",He= lvetica,sans-serif">Christian Hopps <chopps@chopps.org>
Subject: New tool: Using Emacs Org Mode for writing RFCs
<= /span>
Date: March 4, 2019 at 6:19:20 PM EST
To: "ietf\@ietf.org" <ietf@ietf.org>


Check it out: https://github.com/choppsv1/org-rfc-export

If= you are an Emacs user, especially one who is familiar with/uses Org Mode, = I think you'll like this.

I've been working on an org mode e= xporter for writing RFCs. As it's now in MELPA (package: ox-rfc) I figu= red it was a good time to announce it's availability. Basically you wri= te your RFC in Org Mode and export it to XML. The back-end supports exporti= ng to XML (for manual xml2rfc), but also supports exporting to text, HTML, = or PDF, including directly into a buffer for easy previewing.

Highli= ghts:
- Powerful Org Mode
- Simple Citations/References.
- Lists (= Numbered, Unnumbered)
- Definition Lists (term + definition)
- Tables=
- Embedded Code (Literate Programming e.g., embed yang model, trees, ex= amples)

In particular YANG embedding is pretty neat. There's no = need for separate files and tree generation (and example validation) can be= automated from the embedded text.

Check out the README and the exam= ples (currently in the ert-tests directory).

Thanks,
Chris.

____________________________________= _______________________
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
--00000000000043b85f0583506a3c-- From nobody Tue Mar 12 15:45:35 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95C4C131167 for ; Tue, 12 Mar 2019 15:45:28 -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 aOmG6utB-uFC for ; Tue, 12 Mar 2019 15:45:27 -0700 (PDT) Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (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 C95E5131262 for ; Tue, 12 Mar 2019 15:45:26 -0700 (PDT) Received: by mail-pg1-x535.google.com with SMTP id l11so2374pgq.10 for ; Tue, 12 Mar 2019 15:45:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:organization:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=YqUALadMiP1BY+AXAUoK9deJRea1v7QuWD9UUJO6NVs=; b=CsRcDcw2R5+mwq+BjlzyijI7SsShxPuG/NYLyKNsjNkcsc2dnKEKL9lby2FM3KU40E 8GDe3kQL+o7HUE0Cbc9U9hGRYPPLw+69z6VfJCmYOgY03aMuUzniNfSBBrNBQU1U+7/J VtPsMqdN8wrvccdNFYHeP4pn9OnBRhsXJSotnTuq7/jXFPJtTA2vTiGGI77xJLdFvXul ZbHfFYb/ylLZaBTZMY0Ad3C8ihCrrlBFacbJP+dvIYe5gsPGq86iT1OLRuEzQZ7L7Lej CVUxrFa1y1KPyXiPZwixYBPPupMy5SQIfUtt98u6fWPqGhj0Rxm57zap4oKtdZxZBLoO ZdFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:organization:message-id:date :user-agent:mime-version:content-language:content-transfer-encoding; bh=YqUALadMiP1BY+AXAUoK9deJRea1v7QuWD9UUJO6NVs=; b=iYz1Y+vWH7bzYAo8+NetjQmp42c6wpqZTGvTs17PPwvlP4X6FzbB+8MFjrUZ7oTU4Q 38xB1YAabaN6JjdmYYRO9vNcDKa2fgLkTELZQl+Gz+4yfFTKipCiSurp3ZpsDx6THDZE jIQt4NMYHyj/WWOvULDBleRr0+f9d3vAJVMux3asAVMxBU0B0nknfyQMSR1I8WgPIPh4 PhVchhPvHShJWefz4NXXoD76hixi0u1uXaD3Q61mh3tBjvizQfCRgt3eArOcFX3M2mLh D1xPKn+RBSGLBbwd0wvFqNEXDqU5Glc8JfzLvT3ipXbdAkof0cPEjHzFmUcN1jFGP5Bv w8Tg== X-Gm-Message-State: APjAAAUcKvwN/S+eZSjIRhiYxs4kj/Oo76o+o+daNokjbIdo1hEj3r+R bFPzhE8AMttN1mTaUfEc2N4VuiNZ X-Google-Smtp-Source: APXvYqxLYQxdi1Kdx3SirybTI1R4LprxJ7nTJVVuo7N4z4d4t8t0iCj/exQBilMFDqZNqaHRr1zO7w== X-Received: by 2002:a62:64d1:: with SMTP id y200mr40846593pfb.161.1552430725783; Tue, 12 Mar 2019 15:45:25 -0700 (PDT) Received: from [130.216.36.127] (sc-cs-567-laptop.uoa.auckland.ac.nz. [130.216.36.127]) by smtp.gmail.com with ESMTPSA id y37sm17603409pgk.78.2019.03.12.15.45.24 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Mar 2019 15:45:25 -0700 (PDT) To: tools-discuss@ietf.org From: Brian E Carpenter Organization: University of Auckland Message-ID: <186f4ff4-e31e-80c6-600f-9521694734f0@gmail.com> Date: Wed, 13 Mar 2019 11:45:23 +1300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: [Tools-discuss] Step backwards: X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2019 22:45:34 -0000 I noticed that in the last few days, messages such as Gen-ART reviews generated by the tracker have From: fields like "John Doe via Datatracker ". This means that Reply won't work at all and Reply All will not include a direct copy to the reviewer (or other message originator). This change wasn't announced, as far as I know. It's a bug as far as I'm concerned. If the reason for this is that some mail systems treat the genuine sender's address as a forgery, OK, but then please generate a Cc: field for the original sender's address, so that at least Reply All will do the right thing. If that isn't the reason, I believe this change should be reversed. Regards Brian Carpenter From nobody Tue Mar 12 16:19:46 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59B60124BA8 for ; Tue, 12 Mar 2019 16:19:44 -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, 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 JiCdaLu7-Mkj for ; Tue, 12 Mar 2019 16:19:42 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFF261200D7 for ; Tue, 12 Mar 2019 16:19:42 -0700 (PDT) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:61044 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1h3qgP-0002ph-LT; Tue, 12 Mar 2019 16:19:42 -0700 To: Brian E Carpenter , tools-discuss@ietf.org References: <186f4ff4-e31e-80c6-600f-9521694734f0@gmail.com> From: Henrik Levkowetz Message-ID: <656168f7-ed79-e19e-ea73-433cd9b49994@levkowetz.com> Date: Wed, 13 Mar 2019 00:19:34 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <186f4ff4-e31e-80c6-600f-9521694734f0@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="JOGBAWJB2R7ta7XqrXD3vcOdckfMTGLhg" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, brian.e.carpenter@gmail.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org) X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [Tools-discuss] Step backwards: X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2019 23:19:45 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --JOGBAWJB2R7ta7XqrXD3vcOdckfMTGLhg Content-Type: multipart/mixed; boundary="sBc4w7NT9a2sO0DKoq0QnDnlwnGxBTQEN"; protected-headers="v1" From: Henrik Levkowetz To: Brian E Carpenter , tools-discuss@ietf.org Message-ID: <656168f7-ed79-e19e-ea73-433cd9b49994@levkowetz.com> Subject: Re: [Tools-discuss] Step backwards: References: <186f4ff4-e31e-80c6-600f-9521694734f0@gmail.com> In-Reply-To: <186f4ff4-e31e-80c6-600f-9521694734f0@gmail.com> --sBc4w7NT9a2sO0DKoq0QnDnlwnGxBTQEN Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Brian, On 2019-03-12 23:45, Brian E Carpenter wrote: > I noticed that in the last few days, messages such as Gen-ART reviews > generated by the tracker have From: fields like "John Doe via > Datatracker ". >=20 > This means that Reply won't work at all and Reply All will not > include a direct copy to the reviewer (or other message originator). >=20 > This change wasn't announced, as far as I know. It's a bug as far as > I'm concerned. >=20 > If the reason for this is that some mail systems treat the genuine > sender's address as a forgery, OK, but then please generate a Cc: > field for the original sender's address, so that at least Reply All > will do the right thing. The next datatracker release, which I hope to make tomorrow, will have the Reply-To: header field set appropriately, using the reviewer or AD email address which previously was used for the From: field. =20 I believe this will make Reply and Reply All work as before, while still avoiding the troubles we've seen from using a From: address that may look like a forgery. > If that isn't the reason, I believe this change should be reversed. Understood. Yes, this was the reason for the original change. I hope inclusion of the Reply-To: field will make this work better. Regards, Henrik --sBc4w7NT9a2sO0DKoq0QnDnlwnGxBTQEN-- --JOGBAWJB2R7ta7XqrXD3vcOdckfMTGLhg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAlyIPoYACgkQTptXS4+7 FxrULRAAqN1ENhPGEJkgEXVM9rp1uVjupPxha3erHwKpDIHA8Q/GhQxJD1R24t6B fdibPutdf23kVzM+Ot8RzeLi+x0YQTwJRuHKGendAMu1PCwEAZhWPyOOOjuB9QWo P1CjWvogNPAqn+GFUS5xrtx+OECuOOLj0r4xof1cBvYu89NdFr+FOxBT0TXxaJ3V wg31rSHk2x5rxaJV/E08pTdfohLAEgdXOfwWOvfHLyYX8Nyx7WIyCHNiEsn0YNUN 0DMgBbmCGiHIAe4k3QtUGCEhvAmDoW8yboDzKvG4rAeIXKiO5X2YdSGqv/wcICSy 88zZ+jeDo/hPhOO+yK+4NGjOoke0bViiTZcc9P1AZinhb3DmdA84eoWjV6W7vHWk GeANpTDwE2XmKcMeLEth+tnP1aSmRSRsHfBJY2aT2xAl4J8fgtaNMQK6K4XqQwaw kwjfJ9Ku8422Nd/8X905RlQfppVg+V1anMudtNV/p7OAH0evUthHGaw/lhKjayes sgBZWSJMpVzMPmIGky0DBy6sMwDIHWzUfSGKl6I40mJr8MOpXQfQYWlGmJWo71CI hYtXsAq9jW+x/bAabemVhefi+MoMeaY4rYqpOlVVvnlOWEQvH07SCol/v239zRtX 8I0JK4SD4ZfLM372YEduzqBOnyTNObgmGCe1zccfif+oLQir7A8= =tJfK -----END PGP SIGNATURE----- --JOGBAWJB2R7ta7XqrXD3vcOdckfMTGLhg-- From nobody Tue Mar 12 16:26:05 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B190D124B16 for ; Tue, 12 Mar 2019 16:26:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.721 X-Spam-Level: X-Spam-Status: No, score=-1.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FROM_EXCESS_BASE64=0.979, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=frobbit.se 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 lrlQbNo78Xwz for ; Tue, 12 Mar 2019 16:26:02 -0700 (PDT) Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.185]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E27911228B7 for ; Tue, 12 Mar 2019 16:26:01 -0700 (PDT) Received: from [10.196.207.153] (unknown [IPv6:2620:f:8000:210:ad38:edcf:432:c8e9]) by mail.frobbit.se (Postfix) with ESMTPSA id 6506F23634; Wed, 13 Mar 2019 00:25:58 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=frobbit.se; s=mail; t=1552433159; bh=r8kiSUlGZe/TELuzwQgLUOwjT0auRhUApwqYvMc2YVI=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=eT9Z3a0UbYeaz7Bbavw8fvzhgbAsoeoiIvMUtJ/v0q1Ozs1aEP5SexxrQfRc17XXa 8iOshnVATzwtqwdOm1zzETpDbar63n5kkxpB3nl8zwh7ejNVcDSJEfT0t5PS62+wVN TuqlQSbxlPgyXAEAzEq5sKL+eohVHSps8vS+E4sM= From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" To: "Henrik Levkowetz" Cc: "Brian E Carpenter" , tools-discuss@ietf.org Date: Wed, 13 Mar 2019 08:25:54 +0900 X-Mailer: MailMate (1.12.4r5597) Message-ID: In-Reply-To: <656168f7-ed79-e19e-ea73-433cd9b49994@levkowetz.com> References: <186f4ff4-e31e-80c6-600f-9521694734f0@gmail.com> <656168f7-ed79-e19e-ea73-433cd9b49994@levkowetz.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_MailMate_CD954CFA-2C38-4AE2-8B16-1EA8119EADCF_="; micalg=pgp-sha1; protocol="application/pgp-signature" Archived-At: Subject: Re: [Tools-discuss] Step backwards: X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2019 23:26:04 -0000 This is an OpenPGP/MIME signed message (RFC 3156 and 4880). --=_MailMate_CD954CFA-2C38-4AE2-8B16-1EA8119EADCF_= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On 13 Mar 2019, at 8:19, Henrik Levkowetz wrote: > I believe this will make Reply and Reply All work as before, while stil= l avoiding the troubles we've seen from using a From: address that may lo= ok like a forgery. May I suggest stopping changing the body of the email messages (by adding= a footer). That way DKIM signatures will work, and the email will indeed= not be defined being forgery which in fact they are as long as the body = is changed. Patrik --=_MailMate_CD954CFA-2C38-4AE2-8B16-1EA8119EADCF_= Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iG0EARECAC0WIQRUH/cJI8i4DDUU3qWsxpsaC4jXzQUCXIhAAw8ccGFmQGZyb2Ji aXQuc2UACgkQrMabGguI180a7ACgmZxOfncIuUGES1mrsRKQwv8GeoYAn3OdzYkM AVCRGmsN9MVw3NSfdHcu =0/jm -----END PGP SIGNATURE----- --=_MailMate_CD954CFA-2C38-4AE2-8B16-1EA8119EADCF_=-- From nobody Tue Mar 12 16:31:47 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C23F127287 for ; Tue, 12 Mar 2019 16:31:45 -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 0arxxWvpf6CJ for ; Tue, 12 Mar 2019 16:31:43 -0700 (PDT) Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) (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 B09DB124B16 for ; Tue, 12 Mar 2019 16:31:43 -0700 (PDT) Received: by mail-pg1-x52c.google.com with SMTP id h34so74364pgh.11 for ; Tue, 12 Mar 2019 16:31:43 -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=asSbrmM3TJyduWxaCUqKztOw9hTbTXgyoJtvuYZCjgw=; b=rBriMV91zurOvZk8rSybiwARJ0JreYcV5jL4Hg9RlVq4E912+2uU9WHOeX/G+EuekH 9guvltPIZvk+cr8Lw/KNA3BTZGobQ7QA5l1kKSbTiyhwVKDtCS96e2SHziZM7RR58V9Y tickFms4RPHVxd/lbOjTjsthXwIdnAxagDWQwymAVllpYdAMwmWahwwk5AglVxY6k5b2 0bMGjXF6nl4FtqoPP9VBaguwjfyNFOzrX8+CdMgsfOMHmBrpMwD80KGWRUSUcMqVTsjs uWQR5GleZTwYMw+7zDGgKIvwta3QpWt+pxyh9+xV01aY74hEC0ldtUv1xVQax2ANxbnP 1N6g== 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=asSbrmM3TJyduWxaCUqKztOw9hTbTXgyoJtvuYZCjgw=; b=KkUr1g/ERMaemNBc+uj8a4JVpGGzFxJg+AI9vKqbxSpy2EsdBxgbm/w4G8aaWAH8js z76mBjB0rbbjHb/bn+PgbekXQymv0GawGXZWC1UZT+55oOXm/Js4n8cy56NPuOwokI6w LL1iTbCp5KE9/ms0YDSyTX4xbwVzPGO6A5PttPcKf6/UwyQr2/kW80K6I7HF5Pl38opm HUdNEcemZ5OQp3lZADbuEaOLJrbh98OO0msH+gGuAZZoAc10FSSC9nWFlE8XdFrSBRH+ Wh3kyOxuvHBNNvUgy0oXw3vy8ft8NAU0+BIFTYt5jI7JrkRhxbZUjjGGdzGLnoMcaL5U 1P0Q== X-Gm-Message-State: APjAAAXxwsJgq3SDEbfRsivLsDkOS3O3vzXjpGZEZ81uOgsXZzh0xwQh lDFz8aTW5tXPmQr1Vfm52l7vzr9F X-Google-Smtp-Source: APXvYqwojtoZ/VCO0r3ft1Ug5CtEjzv3rkm3S9E9M6/mh/84AFJTbq/A8Bq6frnFcz0emTTrckm8HA== X-Received: by 2002:a63:7503:: with SMTP id q3mr35048714pgc.98.1552433502818; Tue, 12 Mar 2019 16:31:42 -0700 (PDT) Received: from [172.24.3.101] ([202.36.244.176]) by smtp.gmail.com with ESMTPSA id u192sm7646698pgu.12.2019.03.12.16.31.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Mar 2019 16:31:42 -0700 (PDT) To: Henrik Levkowetz , tools-discuss@ietf.org References: <186f4ff4-e31e-80c6-600f-9521694734f0@gmail.com> <656168f7-ed79-e19e-ea73-433cd9b49994@levkowetz.com> From: Brian E Carpenter Message-ID: <91b49deb-2500-2500-35c2-1d7b0dbd4074@gmail.com> Date: Wed, 13 Mar 2019 12:31:39 +1300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3 MIME-Version: 1.0 In-Reply-To: <656168f7-ed79-e19e-ea73-433cd9b49994@levkowetz.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Tools-discuss] Step backwards: X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2019 23:31:45 -0000 Thanks Henrik! Regards Brian On 13-Mar-19 12:19, Henrik Levkowetz wrote: > Hi Brian, > > On 2019-03-12 23:45, Brian E Carpenter wrote: >> I noticed that in the last few days, messages such as Gen-ART reviews >> generated by the tracker have From: fields like "John Doe via >> Datatracker ". >> >> This means that Reply won't work at all and Reply All will not >> include a direct copy to the reviewer (or other message originator). >> >> This change wasn't announced, as far as I know. It's a bug as far as >> I'm concerned. >> >> If the reason for this is that some mail systems treat the genuine >> sender's address as a forgery, OK, but then please generate a Cc: >> field for the original sender's address, so that at least Reply All >> will do the right thing. > > The next datatracker release, which I hope to make tomorrow, will have > the Reply-To: header field set appropriately, using the reviewer or > AD email address which previously was used for the From: field. > > I believe this will make Reply and Reply All work as before, while still > avoiding the troubles we've seen from using a From: address that may > look like a forgery. > >> If that isn't the reason, I believe this change should be reversed. > > Understood. Yes, this was the reason for the original change. I hope > inclusion of the Reply-To: field will make this work better. > > > Regards, > > Henrik > From nobody Tue Mar 12 20:57:39 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EAE3127970 for ; Tue, 12 Mar 2019 20:57:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iabHLHL-KWir for ; Tue, 12 Mar 2019 20:57:36 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 731EA12788D for ; Tue, 12 Mar 2019 20:57:36 -0700 (PDT) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:62970 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1h3v1L-0004dE-Mj; Tue, 12 Mar 2019 20:57:36 -0700 To: =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= References: <186f4ff4-e31e-80c6-600f-9521694734f0@gmail.com> <656168f7-ed79-e19e-ea73-433cd9b49994@levkowetz.com> Cc: tools-discuss@ietf.org From: Henrik Levkowetz Message-ID: <5eee9abc-4919-d3f3-9d5c-ec05823cf479@levkowetz.com> Date: Wed, 13 Mar 2019 04:57:27 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="OBkn2U2mCf7AhclHohUM1x2hlEFud31jH" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, paf=40frobbit.se@dmarc.ietf.org X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org) X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [Tools-discuss] Step backwards: X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2019 03:57:38 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --OBkn2U2mCf7AhclHohUM1x2hlEFud31jH Content-Type: multipart/mixed; boundary="dXErUVmSMIA4RsSqb2pSjuScKQM1Me7b2"; protected-headers="v1" From: Henrik Levkowetz To: =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= Cc: tools-discuss@ietf.org Message-ID: <5eee9abc-4919-d3f3-9d5c-ec05823cf479@levkowetz.com> Subject: Re: [Tools-discuss] Step backwards: References: <186f4ff4-e31e-80c6-600f-9521694734f0@gmail.com> <656168f7-ed79-e19e-ea73-433cd9b49994@levkowetz.com> In-Reply-To: --dXErUVmSMIA4RsSqb2pSjuScKQM1Me7b2 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Patrik, On 2019-03-13 00:25, Patrik F=C3=A4ltstr=C3=B6m wrote: > On 13 Mar 2019, at 8:19, Henrik Levkowetz wrote: >=20 >> I believe this will make Reply and Reply All work as before, while >> still avoiding the troubles we've seen from using a From: address >> that may look like a forgery. >=20 > May I suggest stopping changing the body of the email messages (by > adding a footer). That way DKIM signatures will work, and the email > will indeed not be defined being forgery which in fact they are as > long as the body is changed. That is a different issue (that will hopefully be solved by ARC, which we hope to deploy soon). Brian is talking about a recent change away from a practice where when a reviewer would enter his review into the datatracker, it would originate a mail purporting to be from , and send that out from the server mail.ietf.org, which is not mentioned in the SPF record of reviewers.domain. Since this was becoming increasingly troublesome, as more and more domains were adopting stricter SPF settings, we've stopped sending mail purporting to be sent by , and are now sending from , but we missed adding a Reply-To: header field that would make replies work as before. Regards, Henrik --dXErUVmSMIA4RsSqb2pSjuScKQM1Me7b2-- --OBkn2U2mCf7AhclHohUM1x2hlEFud31jH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAlyIf6cACgkQTptXS4+7 Fxraew//Q7dKycWu8BUjh90POAgVwoCMlgf6bDr0HAWtdF0s+kREKmNGiXeYzPR1 PqedyVUFdQPd7bVYDhqznNTcyHp9dg35CpqOQ+AKT2v/syaErvtRIf+zIXcppbNk wXqqDV7hiwBkx2+WwYFiY8eePTMvpGNUv3Gu1wa+sc/3NU9f5AkoKkSbPlDluHiL JajKyZDF8fmN7atgUe5QxtveJqjMMcoI8T4EYITaWIF5AjYHEV99p43TI7UhoqZP ksiEfs7yfkaaAv4s/DwIgW2fXNbQvoiDkNH+zO/AxBGtKUXgaRLIpneV9E1kbb1O 4oscc5b4xIvMG0t8pIcL9N4OxtKA+y1BGoyC9bFUaI+h8wPPE+gRK9oRKam147nw 6G3c+hz2vTOi8j8eBjPlfCHKSakQD5Vc7Idze9k7jBf73iQEyw32etzukPEhoU/N REB7InlLaAObeIK6kLQXDxuGGKx0bPgKp1bWnJGfuS3qnAnTyrDmUGw3JSB5B8wy d9ZHeAhwVCpE5Cszce/hbm3/QOX6dwWO/fKZ2dyuZWOe/dYD9BuzS1AssNQmIGbr xtwVI8VJqh/LREoxens7YsqUEvNu59C8SHNBR2n6jwc0eildw9tOWCiBhw8PREsZ a1/UTQSXGFbkQU62KAoyov4cYstEXKkIB5ZDFaF+0oHrLIWQA80= =6vV5 -----END PGP SIGNATURE----- --OBkn2U2mCf7AhclHohUM1x2hlEFud31jH-- From nobody Tue Mar 12 22:27:29 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 436F6130E7F for ; Tue, 12 Mar 2019 22:27:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.679 X-Spam-Level: X-Spam-Status: No, score=-1.679 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iAK7boI_TkvJ for ; Tue, 12 Mar 2019 22:27:27 -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 71E12130E7D for ; Tue, 12 Mar 2019 22:27:27 -0700 (PDT) Received: from MacBook-Pro.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x2D5ROsG007459 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 13 Mar 2019 00:27:25 -0500 (CDT) (envelope-from adam@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1552454845; bh=5tmbwqrQCQEPuo8iKAAJl7RqEz1pnLgvIIbdgRs1Hf8=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=VUd7/srOe5oCOXH46lIdEpMbaCBK5/seR+DjoaFJ0LLF2yzqN12EnAGLZJyNRmevP A+JTRyeTQbkVoTo++EQS5/F8nQ5YQxb0aAXNUZHIFAj36SDB4OOSA07kjOvg7vE6k9 lnZ9eJV35nqYLTGkiUfrVXdTBLzGlRhafCadmC9I= X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be MacBook-Pro.roach.at To: Henrik Levkowetz , =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= Cc: tools-discuss@ietf.org References: <186f4ff4-e31e-80c6-600f-9521694734f0@gmail.com> <656168f7-ed79-e19e-ea73-433cd9b49994@levkowetz.com> <5eee9abc-4919-d3f3-9d5c-ec05823cf479@levkowetz.com> From: Adam Roach Message-ID: Date: Wed, 13 Mar 2019 00:27:18 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.5.3 MIME-Version: 1.0 In-Reply-To: <5eee9abc-4919-d3f3-9d5c-ec05823cf479@levkowetz.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: Re: [Tools-discuss] Step backwards: X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2019 05:27:28 -0000 On 3/12/19 10:57 PM, Henrik Levkowetz wrote: > > Since this was becoming increasingly troublesome, as more and more > domains were adopting stricter SPF settings, we've stopped sending > mail purporting to be sent by , and are > now sending from , but we missed adding a Reply-To: > header field that would make replies work as before. By the way, this dovetails well into a conversation we had earlier about responses to IESG ballots being attached to the ballots, so that the entire conversation ends up in the ballot. This would greatly simplify the task of IESG members attempting to validate whether review comments received responses (and what those responses were). Please consider changing to instead be , and make mail sent to turn into a comment which is then appended to whatever data structure originated the initial email. /a From nobody Tue Mar 12 22:31:13 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D7FC1277DB for ; Tue, 12 Mar 2019 22:31: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, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 k9unx26TIVN3 for ; Tue, 12 Mar 2019 22:31:09 -0700 (PDT) Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (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 DB0C512867A for ; Tue, 12 Mar 2019 22:31:08 -0700 (PDT) Received: by mail-qk1-x72d.google.com with SMTP id z3so373217qkf.5 for ; Tue, 12 Mar 2019 22:31:08 -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=ck4y1ciGCN1EskvvQiYdcfQ4PBL/g2PIZsuAUMmRek8=; b=We6lm6d8U9dctHg6/VaKAYprVX8ZN0vf3ioz+tCiCXXh/VDYvMcYnHfkTdoqpUw1E2 Xb27zDwvFzUP6E0u+x8RnH4gIBoojqc9601CCKjmw6uwd06gF0kI1yqePjWaQ+XC1VaE 1d67a9rz1+TCtNzQNBtUInVM1uWORB6t2LNKZNuiDl7i7mLDzKir0JsXIY0TNP41CIm5 CbdM900o7vqBgcylmDw/lDmVxt4hOXlxdhh9hcBlBqRWo1sAPK/HKoJlupm1nvykE4y+ aCevDyToy2Kb2S3S809FcyKXm0a4nl2rqRZEq6Fmetulen5Y/V1Yo0imC4VUhwj8bwe5 ZKOw== 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=ck4y1ciGCN1EskvvQiYdcfQ4PBL/g2PIZsuAUMmRek8=; b=qFEh4yk4POLx+vvX8HD+PdXvzNxzuDSm90+PlZZPtxuiZxzOUhGQjJBPpEnBCGkC8a j05Lw5WZd1VpZcI1q98dmLWPdPdgC6BDfui69WOC+cIJ1I5Cxx6ZWMmDTygaDMVQQhGX FjG27fbwlnfjXCfM7aZY1Q1h6mrKqQIIO5WyGNdqU4yBsvuwxnWDPA/4H5y7vFmnJnEC VFxbYlbOtU3uY1rkx/cFjshZQ1Y8ZjQSlzy7Rss9gAtJJ3oDwEMpUWoST0MJx7xrQJMs oqDkgSHCxS/sPRQalgT+jCdIlVa9ZPY5uOCwNwRQvTo5WNyWCS1TNFxTC3yvz+syzvo/ m+tg== X-Gm-Message-State: APjAAAXXlajMTIjW9jlhxFeDbWcDBFDVe6wOYtDvbxX2fqiXwmJIGMDl uKiPnZCDs168SKMkAYdqHTzkLn8QAVXp9WRzsmv2JA== X-Google-Smtp-Source: APXvYqwmjlb5RYiUh3ICUCzw0fF9ufvMsQsNpsW1XztOe5KJoSS+geGWoPQBKkJ3dkFcr8VTLFhrnGLmBxMnVSOAMV0= X-Received: by 2002:a37:c50f:: with SMTP id p15mr11524433qki.278.1552455067706; Tue, 12 Mar 2019 22:31:07 -0700 (PDT) MIME-Version: 1.0 References: <186f4ff4-e31e-80c6-600f-9521694734f0@gmail.com> <656168f7-ed79-e19e-ea73-433cd9b49994@levkowetz.com> <5eee9abc-4919-d3f3-9d5c-ec05823cf479@levkowetz.com> In-Reply-To: From: Warren Kumari Date: Wed, 13 Mar 2019 14:30:29 +0900 Message-ID: To: Adam Roach Cc: Henrik Levkowetz , =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= , Tools Discussion Content-Type: multipart/alternative; boundary="000000000000d7398c0583f31c2d" Archived-At: Subject: Re: [Tools-discuss] Step backwards: X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2019 05:31:11 -0000 --000000000000d7398c0583f31c2d Content-Type: text/plain; charset="UTF-8" On Wed, Mar 13, 2019 at 2:27 PM Adam Roach wrote: > On 3/12/19 10:57 PM, Henrik Levkowetz wrote: > > > > Since this was becoming increasingly troublesome, as more and more > > domains were adopting stricter SPF settings, we've stopped sending > > mail purporting to be sent by , and are > > now sending from , but we missed adding a Reply-To: > > header field that would make replies work as before. > > > By the way, this dovetails well into a conversation we had earlier about > responses to IESG ballots being attached to the ballots, so that the > entire conversation ends up in the ballot. This would greatly simplify > the task of IESG members attempting to validate whether review comments > received responses (and what those responses were). Please consider > changing to instead be , and > make mail sent to turn into a comment which is > then appended to whatever data structure originated the initial email. > > Wow, that would be incredibly awesome. W > /a > > ___________________________________________________________ > 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 --000000000000d7398c0583f31c2d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, Mar 13, 2019 at 2:27 PM Adam= Roach <adam@nostrum.com> wro= te:
On 3/12/19 1= 0:57 PM, Henrik Levkowetz wrote:
>
> Since this was becoming increasingly troublesome, as more and more
> domains were adopting stricter SPF settings, we've stopped sending=
> mail purporting to be sent by <reviewer@reviewers.domain>, and a= re
> now sending from <noreply@ietf.org>, but we missed adding a Reply-To:
> header field that would make replies work as before.


By the way, this dovetails well into a conversation we had earlier about responses to IESG ballots being attached to the ballots, so that the
entire conversation ends up in the ballot. This would greatly simplify
the task of IESG members attempting to validate whether review comments received responses (and what those responses were). Please consider
changing <noreply@= ietf.org> to instead be <unique-token@ietf.org>, and
make mail sent to <unique-token@ietf.org> turn into a comment which is
then appended to whatever data structure originated the initial email.


Wow, that would be incredibly awesome.
W


=C2=A0
/a

___________________________________________________________
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 when= it was obviously a bad idea in the first place.
This is like putting ra= bid weasels in your pants, and later expressing regret at having chosen tho= se particular rabid weasels and that pair of pants.
=C2=A0 =C2=A0---maf<= /div>
--000000000000d7398c0583f31c2d-- From nobody Wed Mar 13 01:41:26 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08AF1130ECE for ; Wed, 13 Mar 2019 01:41:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.721 X-Spam-Level: X-Spam-Status: No, score=-1.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FROM_EXCESS_BASE64=0.979, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=frobbit.se 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 93Yeh2VD9jAK for ; Wed, 13 Mar 2019 01:41:22 -0700 (PDT) Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5FD4130EC6 for ; Wed, 13 Mar 2019 01:41:21 -0700 (PDT) Received: from [169.254.126.190] (unknown [IPv6:2620:f:8000:210:f0e3:3b9d:c477:243d]) by mail.frobbit.se (Postfix) with ESMTPSA id 3512221A6C; Wed, 13 Mar 2019 09:41:16 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=frobbit.se; s=mail; t=1552466478; bh=W6UaKe3hLeT597c/tIAnYR/JpyaCLk1UMykAEb4j5TA=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=mSScEGr8vX1+q0uPSxa/UMRsYOVw+sPKwtOBwX3a1VL0jt5C/anCq759LjDIVUC04 fHfdImhEpW+17NwYrVpAazycR/c4XI5FyW1/tT2IZQU+ThwvSWR2FeUSRPYQOp/pBF SVOQxsEOgxLn4Gs2IgNvd75vwN7ZgpQU7DZgTAnE= From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" To: "Henrik Levkowetz" Cc: tools-discuss@ietf.org Date: Wed, 13 Mar 2019 17:41:13 +0900 X-Mailer: MailMate (1.12.4r5597) Message-ID: In-Reply-To: <5eee9abc-4919-d3f3-9d5c-ec05823cf479@levkowetz.com> References: <186f4ff4-e31e-80c6-600f-9521694734f0@gmail.com> <656168f7-ed79-e19e-ea73-433cd9b49994@levkowetz.com> <5eee9abc-4919-d3f3-9d5c-ec05823cf479@levkowetz.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_MailMate_17EE1467-0279-4AE9-AF53-66A2605BE0F2_="; micalg=pgp-sha1; protocol="application/pgp-signature" Archived-At: Subject: Re: [Tools-discuss] Step backwards: X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2019 08:41:24 -0000 This is an OpenPGP/MIME signed message (RFC 3156 and 4880). --=_MailMate_17EE1467-0279-4AE9-AF53-66A2605BE0F2_= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On 13 Mar 2019, at 12:57, Henrik Levkowetz wrote: > Brian is talking about a recent change away from a practice where when = a reviewer would enter his review into the datatracker, it would originat= e a mail purporting to be from , and send that= out from the server mail.ietf.org, which is not mentioned in the SPF rec= ord of reviewers.domain. > > Since this was becoming increasingly troublesome, as more and more doma= ins were adopting stricter SPF settings, we've stopped sending mail purpo= rting to be sent by , and are now sending from= , but we missed adding a Reply-To: > header field that would make replies work as before. Fun fun fun, multiple interacting interesting bits in the tussle! Thanks for untangling the bits! paf --=_MailMate_17EE1467-0279-4AE9-AF53-66A2605BE0F2_= Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iG0EARECAC0WIQRUH/cJI8i4DDUU3qWsxpsaC4jXzQUCXIjCKQ8ccGFmQGZyb2Ji aXQuc2UACgkQrMabGguI183KuwCdFaYR1XwjXo8G2eN3l7BeWbY9TVUAnR5TkZ8b ynYGG1dP4JrAaoRM4gAd =uJmG -----END PGP SIGNATURE----- --=_MailMate_17EE1467-0279-4AE9-AF53-66A2605BE0F2_=-- From nobody Wed Mar 13 16:47:48 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 872BA131244 for ; Wed, 13 Mar 2019 16:47:47 -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, 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 K1Zt4Tj6SNVr for ; Wed, 13 Mar 2019 16:47:45 -0700 (PDT) Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03FA1131236 for ; Wed, 13 Mar 2019 16:47:44 -0700 (PDT) Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id F335E38263; Wed, 13 Mar 2019 19:47:24 -0400 (EDT) Received: by sandelman.ca (Postfix, from userid 179) id E973D2D19; Wed, 13 Mar 2019 19:47:42 -0400 (EDT) Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id E4DF0BBD; Wed, 13 Mar 2019 19:47:42 -0400 (EDT) From: Michael Richardson To: Henrik Levkowetz cc: =?us-ascii?Q?=3D=3FUTF-8=3FB=3FUGF0cmlrIEbDpGx0c3Ryw7Zt=3F=3D?= , tools-discuss@ietf.org In-Reply-To: <5eee9abc-4919-d3f3-9d5c-ec05823cf479@levkowetz.com> References: <186f4ff4-e31e-80c6-600f-9521694734f0@gmail.com> <656168f7-ed79-e19e-ea73-433cd9b49994@levkowetz.com> <5eee9abc-4919-d3f3-9d5c-ec05823cf479@levkowetz.com> X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Archived-At: Subject: Re: [Tools-discuss] Step backwards: X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2019 23:47:48 -0000 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Henrik Levkowetz wrote: > On 2019-03-13 00:25, Patrik F=C3=A4ltstr=C3=B6m wrote: >> On 13 Mar 2019, at 8:19, Henrik Levkowetz wrote: >> >>> I believe this will make Reply and Reply All work as before, while >>> still avoiding the troubles we've seen from using a From: address >>> that may look like a forgery. >> >> May I suggest stopping changing the body of the email messages (by >> adding a footer). That way DKIM signatures will work, and the email >> will indeed not be defined being forgery which in fact they are as >> long as the body is changed. > That is a different issue (that will hopefully be solved by ARC, which > we hope to deploy soon). > Brian is talking about a recent change away from a practice where > when a reviewer would enter his review into the datatracker, it would > originate a mail purporting to be from , > and send that out from the server mail.ietf.org, which is not mention= ed > in the SPF record of reviewers.domain. > Since this was becoming increasingly troublesome, as more and more > domains were adopting stricter SPF settings, we've stopped sending > mail purporting to be sent by , and are > now sending from , but we missed adding a Reply-To: > header field that would make replies work as before. Wouldn't the @dmarc.ietf.org mangling have also been an option? =2D- Michael Richardson , Sandelman Software Works -=3D IPv6 IoT consulting =3D- --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlyJlp4ACgkQgItw+93Q 3WUlDQf/YdRZ2Z47phdWeRlW6a/dIBA2p6uFoJQPozocVDcy4A0xQRTiDcl6AQwh Siu1YerntWfBaH3MZHYHAe+ShzilE3vsolVV4aeDsEYHRf3F8NOUtyV1u1D7IPYA BvKfVPdP/5rHOTCJVjhIiY0TzyElsgqO0Vwr46YuCPaU7KxPS7QMTeYHtcupdMNf nx3CbkbYXP+uzc7MzoRIhDxq6oipVCXcStCnusRSvVUzRzLXlU+fgu423db9Poyh MLVo+xQeL/hoN+m8iAh0Zd3QqDgQsBSN8WUwkc7nb+33tWXHuTumAI8Qqewd+Xag 0AYqfqRkHfPMLRHuMJ56bRJz8A0yBQ== =/Lxb -----END PGP SIGNATURE----- --=-=-=-- From nobody Tue Mar 19 09:38:28 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38EB51200B3 for ; Tue, 19 Mar 2019 09:38:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 puQkFaX-EhJm for ; Tue, 19 Mar 2019 09:38:24 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B724C12D7F8 for ; Tue, 19 Mar 2019 09:38:24 -0700 (PDT) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:56887 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1h6Hks-000071-Sy; Tue, 19 Mar 2019 09:38:23 -0700 To: Michael Richardson References: <186f4ff4-e31e-80c6-600f-9521694734f0@gmail.com> <656168f7-ed79-e19e-ea73-433cd9b49994@levkowetz.com> <5eee9abc-4919-d3f3-9d5c-ec05823cf479@levkowetz.com> <24441.1552520862@localhost> Cc: =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= , tools-discuss@ietf.org From: Henrik Levkowetz Message-ID: Date: Tue, 19 Mar 2019 17:38:15 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <24441.1552520862@localhost> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="qnIaocmo2QqdwXcwuIkVwLTRgKTJVnK5g" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, paf=40frobbit.se@dmarc.ietf.org, mcr+ietf@sandelman.ca X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org) X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [Tools-discuss] Step backwards: X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Mar 2019 16:38:27 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --qnIaocmo2QqdwXcwuIkVwLTRgKTJVnK5g Content-Type: multipart/mixed; boundary="4W54Xh5nR2XXOp6Ur62gDXbtKQaCqQeDg"; protected-headers="v1" From: Henrik Levkowetz To: Michael Richardson Cc: =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= , tools-discuss@ietf.org Message-ID: Subject: Re: [Tools-discuss] Step backwards: References: <186f4ff4-e31e-80c6-600f-9521694734f0@gmail.com> <656168f7-ed79-e19e-ea73-433cd9b49994@levkowetz.com> <5eee9abc-4919-d3f3-9d5c-ec05823cf479@levkowetz.com> <24441.1552520862@localhost> In-Reply-To: <24441.1552520862@localhost> --4W54Xh5nR2XXOp6Ur62gDXbtKQaCqQeDg Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Michael, On 2019-03-14 00:47, Michael Richardson wrote: >=20 > Henrik Levkowetz wrote: > > On 2019-03-13 00:25, Patrik F=C3=A4ltstr=C3=B6m wrote: > >> On 13 Mar 2019, at 8:19, Henrik Levkowetz wrote: > >> > >>> I believe this will make Reply and Reply All work as before, wh= ile > >>> still avoiding the troubles we've seen from using a From: addre= ss > >>> that may look like a forgery. > >> > >> May I suggest stopping changing the body of the email messages (= by > >> adding a footer). That way DKIM signatures will work, and the em= ail > >> will indeed not be defined being forgery which in fact they are = as > >> long as the body is changed. >=20 > > That is a different issue (that will hopefully be solved by ARC, = which > > we hope to deploy soon). >=20 > > Brian is talking about a recent change away from a practice where= > > when a reviewer would enter his review into the datatracker, it w= ould > > originate a mail purporting to be from , > > and send that out from the server mail.ietf.org, which is not men= tioned > > in the SPF record of reviewers.domain. >=20 > > Since this was becoming increasingly troublesome, as more and mor= e > > domains were adopting stricter SPF settings, we've stopped sendin= g > > mail purporting to be sent by , and ar= e > > now sending from , but we missed adding a Reply= -To: > > header field that would make replies work as before. >=20 > Wouldn't the @dmarc.ietf.org mangling have also been an option? Yees, but much more complex, and with a forced return through the ietf server, which all seems against KISS. Henrik --4W54Xh5nR2XXOp6Ur62gDXbtKQaCqQeDg-- --qnIaocmo2QqdwXcwuIkVwLTRgKTJVnK5g Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAlyRGvcACgkQTptXS4+7 FxrK9RAAtwg3OZqdkT7Gvcgx6VAhvXqRC/P/jBQbtufT3yVNe8PgFo1G5MrVytTX OsO1tB5lfDhU+3/ZN+OJNkWlgZKrG9mTvdV6zKUYgzTv6taVtGTCh5i4v8JSXfTQ bZ8bh6L+dg4kGA0RoPlBzZ6y5S6xjdhUre+0blTRzazMt5GdtEOek6G1CNkVh6SB 9h2gH60jpnWUo2eAQqo2m/h+TZEtMoHnmvWvTqptBjwCfMRGCdUT3vYDlzqwetZq PLlFYmygC7L+2mJenZT3x22BCuBxagThRRwfTlDcoLvBUq0Z8kGLPpqwumU64805 CvSRb4Rq1/PlukxiIPv9kwXhpYjMpN8phHK7yFIR3ZUWdroh18ywcv817Ku8oTe7 rIPhcYiUwiY31NNN4b4VWaBs2doT66pQvegitfgGMJDckVGzSipS00nH0YmOCKZ5 hhoLnThBe96ulFy38Wn4tAcITtH74qaTfCcD/ZTi38WsBhzmw9wnrJmS63+jhlkt NQCau316Jyh4zH6E2L2x5SK0XPNdu1ewDC5D/X8rIzbBaF693sGkHYDZP5fhTxtQ 5F6rp+MUzrRyrKeQ67TMTtGnnTPoloBNqZ21cF3n32l+o1kXuQdUbRx9fpgaYPIB NiFpT8qBI1F94ZtbFlYVVHzITaWg57QbQZ/o3IfBQCra0Vs519A= =0ruv -----END PGP SIGNATURE----- --qnIaocmo2QqdwXcwuIkVwLTRgKTJVnK5g-- From nobody Sun Mar 31 09:50:17 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22ED01201A1 for ; Sun, 31 Mar 2019 09:50:15 -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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=opendkim.org header.b=wOO74D7t; dkim=pass (1024-bit key) header.d=elandsys.com header.b=Zkcc/a4u 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 6HXKTANu595x for ; Sun, 31 Mar 2019 09:50:13 -0700 (PDT) Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id ACEBE120199 for ; Sun, 31 Mar 2019 09:50:13 -0700 (PDT) Received: from DESKTOP-K6V9C2L.elandsys.com ([197.224.146.192]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x2VGo1PV013408 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 31 Mar 2019 09:50:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1554051011; x=1554137411; bh=qoqI2rdWOInasybncyxYG2sPpVk41BGuvJoRW5eoJE4=; h=Date:To:From:Subject; b=wOO74D7t4QnG4P0VNELcygUl/9SgbSvkMgPM1/6gMCdxj7IRfw0T/X80E2FZ0zMsF P4cYggd98rkciVqDEh2HHTifQnqKoOEym3ovpsbOC8mPCcmxWlatX5EgGpBYZFSbrA otVKFeeYNjm6nTAgzrUEPMPTgIrrgHBvVPGrZU2g= DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1554051011; x=1554137411; i=@elandsys.com; bh=qoqI2rdWOInasybncyxYG2sPpVk41BGuvJoRW5eoJE4=; h=Date:To:From:Subject; b=Zkcc/a4u+vPpb/1N7vJtnhC3+XvlzGUnOSXhaO0RUcLtkpnoF/YMVB7L7WM/9/sdE yvkAOb/dLuJtQm+Tlp4jK0xgsi4OKNRgYcbuhoPnL4l7lvt7CnopCuGsz9PplU+aDN 7nuYnlYTUICu4MEHtHS2FtSzwRIUykn2IVxo/EBo= Message-Id: <6.2.5.6.2.20190331092923.0c953848@elandnews.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6 Date: Sun, 31 Mar 2019 09:49:42 -0700 To: tools-discuss@ietf.org From: S Moonesamy Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Archived-At: Subject: [Tools-discuss] Replacement status set during I-D submission X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Mar 2019 16:50:15 -0000 Hello, I tried to set a "Replaces" during I-D submission [1]. The datatracker sent a notification with the following message: "This document now replaces None instead of None". That message is confusing given that the datatracker displayed the name of the I-D which the new I-D attempted to replace. Regards, S. Moonesamy 1. https://datatracker.ietf.org/doc/draft-moonesamy-recall-rev From nobody Sun Mar 31 09:58:04 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FDD2120199 for ; Sun, 31 Mar 2019 09:58: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, 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 AbOYm-dAkTgG for ; Sun, 31 Mar 2019 09:58:00 -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 711E012011C for ; Sun, 31 Mar 2019 09:58:00 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 31F90300227 for ; Sun, 31 Mar 2019 12:39:42 -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 Nvsv2d5hjYCg for ; Sun, 31 Mar 2019 12:39:36 -0400 (EDT) Received: from a860b60074bd.fios-router.home (unknown [138.88.156.37]) by mail.smeinc.net (Postfix) with ESMTPSA id BDBA13001A5; Sun, 31 Mar 2019 12:39:36 -0400 (EDT) From: Russ Housley Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_9B7E6EE4-CEF4-428B-B2BB-6214387C9EF7" Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Date: Sun, 31 Mar 2019 12:57:53 -0400 In-Reply-To: <6.2.5.6.2.20190331092923.0c953848@elandnews.com> Cc: Tools Discussion To: S Moonesamy References: <6.2.5.6.2.20190331092923.0c953848@elandnews.com> X-Mailer: Apple Mail (2.3445.102.3) Archived-At: Subject: Re: [Tools-discuss] Replacement status set during I-D submission X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Mar 2019 16:58:03 -0000 --Apple-Mail=_9B7E6EE4-CEF4-428B-B2BB-6214387C9EF7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii SM: If only the rev number is changing, the "replaces" should not be used. = The "replaces" is used to indicate an older file name, and it is most = commonly used to indicate that an individual draft has been adopted by a = WG. =20 For example, look at = https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc4071bis/ = Russ > On Mar 31, 2019, at 12:49 PM, S Moonesamy = wrote: >=20 > Hello, >=20 > I tried to set a "Replaces" during I-D submission [1]. The = datatracker sent a notification with the following message: "This = document now replaces None instead of None". That message is confusing = given that the datatracker displayed the name of the I-D which the new = I-D attempted to replace. >=20 > Regards, > S. Moonesamy >=20 > 1. https://datatracker.ietf.org/doc/draft-moonesamy-recall-rev --Apple-Mail=_9B7E6EE4-CEF4-428B-B2BB-6214387C9EF7 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii SM:

If = only the rev number is changing, the "replaces" should not be used. =  The "replaces" is used to indicate an older file name, and it is = most commonly used to indicate that an individual draft has been adopted = by a WG.  

For example, look at https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc4071bis/

Russ


On Mar = 31, 2019, at 12:49 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:

Hello,

I tried to set a = "Replaces" during I-D submission [1].  The datatracker sent a = notification with the following message: "This document now replaces = None instead of None".  That message is confusing given that the = datatracker displayed the name of the I-D which the new I-D attempted to = replace.

Regards,
S. = Moonesamy

1. https://datatracker.ietf.org/doc/draft-moonesamy-recall-rev=

= --Apple-Mail=_9B7E6EE4-CEF4-428B-B2BB-6214387C9EF7-- From nobody Sun Mar 31 10:13:22 2019 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 582E3120188 for ; Sun, 31 Mar 2019 10:13:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.7 X-Spam-Level: X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=gqaQnxF1; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=xJOkZZ2H 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 dHdnwiGQJUtj for ; Sun, 31 Mar 2019 10:13:19 -0700 (PDT) Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7611F12011C for ; Sun, 31 Mar 2019 10:13:19 -0700 (PDT) Received: from DESKTOP-K6V9C2L.elandsys.com ([197.224.146.192]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x2VHD6Xo004279 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 31 Mar 2019 10:13:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1554052397; x=1554138797; bh=v8RAZQy89FiRTbuOjqLmqya/IUw7y/vZOsxzdIg/cCE=; h=Date:To:From:Subject:In-Reply-To:References; b=gqaQnxF1gwNnOBg8kQB22dbxCce5HiBFlxgC8aaxCj317boMUBxw6bHgELFcpAopr hWuPs5x8/YOcuLIvphQoef1mexjLfOjsNMbn5yN4t3DQvsDzJmPTHr7bLmO37BUikH CwiZfPYDMk8kHL7YGrtbgw2UYdVlPMFVKz4LpQUo= DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1554052397; x=1554138797; i=@elandsys.com; bh=v8RAZQy89FiRTbuOjqLmqya/IUw7y/vZOsxzdIg/cCE=; h=Date:To:From:Subject:In-Reply-To:References; b=xJOkZZ2HtRCUoBU2bKWsU9DMenf0JNRkigUni5inof+E7dI5czuAL98FVNYg3S+d6 XpoMJw0u3dwYq0gmuvPRMkNlZC3ucfQLQHgrBh1I9EemvBycjGycQ3agjh0yQbHkez fC/FZn7416rP91V8O8UdJVbmHn6OvM+Hdzc2PFY0= Message-Id: <6.2.5.6.2.20190331100437.0ba594b0@elandnews.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6 Date: Sun, 31 Mar 2019 10:12:51 -0700 To: Russ Housley , tools-discuss@ietf.org From: S Moonesamy In-Reply-To: References: <6.2.5.6.2.20190331092923.0c953848@elandnews.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Archived-At: Subject: Re: [Tools-discuss] Replacement status set during I-D submission X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Mar 2019 17:13:20 -0000 Hi Russ, At 09:57 AM 31-03-2019, Russ Housley wrote: >If only the rev number is changing, the "replaces" should not be >used. The "replaces" is used to indicate an older file name, and it >is most commonly used to indicate that an individual draft has been >adopted by a WG. Thanks for the explanation. I attempted a "Replaces" for draft-klensin-recall-rev-00. Does the datatracker cater for that given that the two drafts are not WG documents? Regards, S. Moonesamy