From nobody Mon Feb 3 07:50:35 2020 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 4E3C11209E8 for ; Mon, 3 Feb 2020 07:50:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.3 X-Spam-Level: X-Spam-Status: No, score=-4.3 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_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=fifthhorseman.net header.b=F5hZ9r0F; dkim=pass (2048-bit key) header.d=fifthhorseman.net header.b=p8YIdj/M 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 GqDat9ClFGW1 for ; Mon, 3 Feb 2020 07:50:32 -0800 (PST) Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13E931209B9 for ; Mon, 3 Feb 2020 07:50:32 -0800 (PST) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019; t=1580745028; h=from : to : subject : date : message-id : mime-version : content-type : from; bh=ROIY+kbVkmN1+GVFL1YktEswHmCyJsBWxL5sRr1EprU=; b=F5hZ9r0FLQcKQ3v8zMxqlJjZEtmKuIk3Aq6tR5qllKGvH4Q+mXMWIj/m fY4b8qAbigGI/1knmh/+7wH+OHTPCg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019rsa; t=1580745028; h=from : to : subject : date : message-id : mime-version : content-type : from; bh=ROIY+kbVkmN1+GVFL1YktEswHmCyJsBWxL5sRr1EprU=; b=p8YIdj/MXngOCAg08ETwad9A5skzpLe6laRWna0esHaeR6mOvNGVqqgh YdAHa6m3ncS8P/ayeABU9LkZTbmgJ6DrLWBr+3KOpfjDbEPM6/mgQ2i20+ rVvzyKJd0eNDDWuZIO/TLChgO2PLdChNTSDLcgAr6vK0YkzutPUpR1sADK O4eps/QygrlhCCIYTfMOjCZv2dgVgJ+dlDKpuvr+ENwVsrDyV+kPsH8dRo Qn6OnwEmXM6VX27HpMlqpViqHydjNzCX0sQhBGjfvZOldkC3WHSm6a7P32 Xay7kFsealgex2BOHcN8IRyNaYaNn0tHiSq+a+GFT3R6piPJo1lz+g== Received: from fifthhorseman.net (unknown [IPv6:2001:470:1f07:60d:4c78:24ff:fed5:5a77]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by che.mayfirst.org (Postfix) with ESMTPSA id 1CB31F9A5 for ; Mon, 3 Feb 2020 10:50:27 -0500 (EST) Received: by fifthhorseman.net (Postfix, from userid 1000) id 979C4204B9; Mon, 3 Feb 2020 10:50:23 -0500 (EST) From: Daniel Kahn Gillmor To: tools-discuss@ietf.org Autocrypt: addr=dkg@fifthhorseman.net; prefer-encrypt=mutual; keydata= mDMEXEK/AhYJKwYBBAHaRw8BAQdAr/gSROcn+6m8ijTN0DV9AahoHGafy52RRkhCZVwxhEe0K0Rh bmllbCBLYWhuIEdpbGxtb3IgPGRrZ0BmaWZ0aGhvcnNlbWFuLm5ldD6ImQQTFggAQQIbAQULCQgH AgYVCgkICwIEFgIDAQIeAQIXgAIZARYhBMS8Lds4zOlkhevpwvIGkReQOOXGBQJd5Hw3BQkFpJWB AAoJEPIGkReQOOXGDYEA/j0ERjPxDleKMZ2LDcWc/3o5cLFwAVzBKQHppu0Be5IWAP0aeTnyEqlp RTE7M8zugwkhYeUYfYu0BjecDUMnYz6iDLgzBF3kewUWCSsGAQQB2kcPAQEHQK1IuW0GZmcrs2mx CYMl8IHse0tMF8cP7eBNXevrlx2ZiPUEGBYIACYCGwIWIQTEvC3bOMzpZIXr6cLyBpEXkDjlxgUC XeR7TwUJAiGl/gCBdiAEGRYIAB0WIQQsv6x2UaqQJzY+dXHEDyVUMvKBDwUCXeR7BQAKCRDEDyVU MvKBD7KmAQCHs+7588C4jto6fMje0Nu97zzoppjJM7lrGF2rVnbHvwD+MgmGUbHzPSUrTWnZBQDi /QM595bxNrBA4N1CiXhs2AMJEPIGkReQOOXGpp0BAM7YeBnt/UNvxJAGm4DidSfHU7RDMWe6Tgux HrH21cDkAQC9leNFXJsQ7F2ZniRPHa8CkictcQEKPL8VCWpfe8LbArg4BF3ke5wSCisGAQQBl1UB BQEBB0Cf+EiAXtntQMf51xpqb6uZ5O0eCLAZtkg0SXHjA1JlEwMBCAeIfgQYFggAJhYhBMS8Lds4 zOlkhevpwvIGkReQOOXGBQJd5HucAhsMBQkCIaVkAAoJEPIGkReQOOXGdYcBANYnW7VyL2CncKH1 iO4Zr0IwfdIv6rai1PUHL98pVi3cAP9tMh85CKGDa0Xi/fptQH41meollLW5tLb/bEWMuUNuBQ== Date: Mon, 03 Feb 2020 10:50:22 -0500 Message-ID: <87eevbd60x.fsf@fifthhorseman.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Archived-At: Subject: [Tools-discuss] bad date math on https://www.ietf.org/registration/ietf107/ietfpayment.py 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, 03 Feb 2020 15:50:34 -0000 --=-=-= Content-Type: text/plain On submitting a registration for IETF 107, in advance of the early bird deadline, but before paying, i encountered this page: https://www.ietf.org/registration/ietf107/ietfpayment.py?confirmno=XXXXXXXXXX&confemail=YYYYYYYYYYYYYYYY (query parameters redacted) On that page, i see the following text: ----------------- If left unpaid, your partial registration will be deleted at 2359 UTC Monday, February 03, 2020. Time remaining to pay registration fee before your registration is deleted: 365 days 09h:16m:22s ----------------- This appears to be wrong by 365 days -- either the current time or the deadline is off by a year. i believe the current time is probably wrong by a year -- because if the deadline itself was off by a year instead, this would be 366 days (since 2020 is a leap year). --dkg --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQQsv6x2UaqQJzY+dXHEDyVUMvKBDwUCXjhBPwAKCRDEDyVUMvKB D577APwIOfWwEuD+GUyzq/PMQFjFjiQ2m5jNatP7Y/sITFqdlgEA1HZsE8lQ2wSd iJpM6zT1j5q/eu+6Yn9q4Yc7NJpKLQQ= =BIi/ -----END PGP SIGNATURE----- --=-=-=-- From nobody Mon Feb 3 07:54:38 2020 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 BFA9A1209B9 for ; Mon, 3 Feb 2020 07:54:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6oR25deDKGWC for ; Mon, 3 Feb 2020 07:54:34 -0800 (PST) Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DD3E1209E8 for ; Mon, 3 Feb 2020 07:54:33 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 7FAB5203411; Mon, 3 Feb 2020 07:52:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ICznBfUxTJ1I; Mon, 3 Feb 2020 07:52:54 -0800 (PST) Received: from [IPv6:2601:647:4200:c8e0:7519:d56c:22ee:d5a9] (unknown [IPv6:2601:647:4200:c8e0:7519:d56c:22ee:d5a9]) by c8a.amsl.com (Postfix) with ESMTPSA id 4597E20340F; Mon, 3 Feb 2020 07:52:54 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Alexa Morris In-Reply-To: <87eevbd60x.fsf@fifthhorseman.net> Date: Mon, 3 Feb 2020 07:54:32 -0800 Cc: tools-discuss@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <3600E528-C97D-4D73-A710-F11CBCDE5DE4@amsl.com> References: <87eevbd60x.fsf@fifthhorseman.net> To: Daniel Kahn Gillmor X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [Tools-discuss] bad date math on https://www.ietf.org/registration/ietf107/ietfpayment.py 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, 03 Feb 2020 15:54:37 -0000 Hi Daniel, Thank you for reporting this. The registration system is a = Secretariat-managed tool, so I have forwarded your email to the right = person within our team for handling. Best, Alexa > On Feb 3, 2020, at 7:50 AM, Daniel Kahn Gillmor = wrote: >=20 > On submitting a registration for IETF 107, in advance of the early = bird > deadline, but before paying, i encountered this page: >=20 > = https://www.ietf.org/registration/ietf107/ietfpayment.py?confirmno=3DXXXXX= XXXXX&confemail=3DYYYYYYYYYYYYYYYY >=20 > (query parameters redacted) >=20 > On that page, i see the following text: >=20 > ----------------- > If left unpaid, your partial registration will be deleted at 2359 UTC = Monday, February 03, 2020. >=20 > Time remaining to pay registration fee before your registration is = deleted: > 365 days 09h:16m:22s > ----------------- >=20 > This appears to be wrong by 365 days -- either the current time or the > deadline is off by a year. >=20 > i believe the current time is probably wrong by a year -- because if = the > deadline itself was off by a year instead, this would be 366 days = (since > 2020 is a leap year). >=20 > --dkg > ___________________________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/tools-discuss >=20 > Please report datatracker.ietf.org and mailarchive.ietf.org > bugs at http://tools.ietf.org/tools/ietfdb > or send email to datatracker-project@ietf.org >=20 > Please report tools.ietf.org bugs at > http://tools.ietf.org/tools/issues > or send email to webmaster@tools.ietf.org From nobody Mon Feb 3 07:56:40 2020 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 53499120A01 for ; Mon, 3 Feb 2020 07:56:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.102 X-Spam-Level: X-Spam-Status: No, score=0.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, PDS_TONAME_EQ_TOLOCAL_SHORT=1.999, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 Ft5t0qYWuV6e for ; Mon, 3 Feb 2020 07:56:37 -0800 (PST) Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (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 2A3AE1209FD for ; Mon, 3 Feb 2020 07:56:35 -0800 (PST) Received: by mail-lf1-x133.google.com with SMTP id t23so10066788lfk.6 for ; Mon, 03 Feb 2020 07:56:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=Q8bQ1t3+p0/syEfcDymfH4OzEr8QTuUDYZRb01Xz1Ko=; b=HXuUcx8KAK7vy2zPBzHWoWl88FBMpGUlkqgmm/xfeemH/dsw4o7OlXSrj+zjRPxRxw W30qqEgDrkBOf2J6xMTzXVyLZks9ItnQcmRB27nlWUl/Te2uJit2oBJDaAFGCx+Wu94U JB2+zzqGeLX56EuovnduTlzWA8PEtaK2gubSnLzmh/5NnlNsnZXi3UcNSauYZvNSc/Gc 6E4rqEVs3mGuHKHPPdcvHnckB/V5Pm/C51fVvIa/HbfNvIQqvwXS+zOFeGOxFlGVmMxF 0MP+jrXMHm4WqlRzDJXIwPxaXtvwxrua6N96meG9rSD1EgPdV3Yo7NYeS8E+Nwf5L+8N xX4g== 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=Q8bQ1t3+p0/syEfcDymfH4OzEr8QTuUDYZRb01Xz1Ko=; b=cSBz9fCMA7QLo3F1wxIGdWthOlhzadn920dQJffUy7Y+0ct4mwPBk3Arx2K7AHkvv6 X57mR82LZ55CE4uf/HWARwL2qZn0FRc/rcy9BYKymT+YDlsmBqUMg2Z37HT/rulbdlw/ sCfvCoh4bq15YxTr619g0Er0YpOyTI9phG4efofbNVGuQ17kbkNNhfarzz9caI9BNwI8 XxS5n0BtaxyIveHvhSQD1BGNzhJjjzwcoBFBc9b2xnTBaH3VfZusE3SV8GShC/qAK+3H bTrhG8/fE3jroXFmKWjs5iXFxsWo48pUe9LzF+JnJ+zf8OSEvsDyST9arkzVO/Oqs8zV ZNiw== X-Gm-Message-State: APjAAAVhQ3HGYTkUJPzDrBTFKnbHii76tiOoG5oxry1xlF231g8P7747 UN3HurxrkWjh28muF4ipK16UfmOBwYtj5GK+EnEIwhbyLOw= X-Google-Smtp-Source: APXvYqxWFCQe/RoxiCiOC6vNBPDQ8LTvOIZ24CFEZ0mEB0JNzqXpjzEnRK2VIAKsydtWy+oxLHv3cxqr3X6poL0ZsTc= X-Received: by 2002:a19:cc11:: with SMTP id c17mr12253116lfg.161.1580745393152; Mon, 03 Feb 2020 07:56:33 -0800 (PST) MIME-Version: 1.0 From: Eric Rescorla Date: Mon, 3 Feb 2020 07:55:57 -0800 Message-ID: To: tools-discuss Content-Type: multipart/alternative; boundary="000000000000a3b622059dadf781" Archived-At: Subject: [Tools-discuss] Empty page for: https://tools.ietf.org/html/draft-arkko-abcd-distributed-resolver-selection-00 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, 03 Feb 2020 15:56:39 -0000 --000000000000a3b622059dadf781 Content-Type: text/plain; charset="UTF-8" This link came from datatracker, but it looks right, so I suspect the problem is on tools --000000000000a3b622059dadf781 Content-Type: text/html; charset="UTF-8"
This link came from datatracker, but it looks right, so I suspect the problem is on tools
--000000000000a3b622059dadf781-- From nobody Mon Feb 10 07:58:05 2020 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 728331200E6 for ; Sun, 9 Feb 2020 03:45:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.7 X-Spam-Level: X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id weUuaQvqdENO for ; Sun, 9 Feb 2020 03:45:25 -0800 (PST) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BB411200E3 for ; Sun, 9 Feb 2020 03:45:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1581248717; bh=wjuykofP/ovuzRXPQ+LAL/Ez8yInbpYeISx/GJG+5ao=; h=X-UI-Sender-Class:To:From:Subject:Date; b=ewrVKNjyoqryzOUD/iv7ZMuugwHkX8lLlC/SCtUWbrKUMxdGP1LnKlyCHIFReUqZE 6v7wG3/Hx7K2sFZWUlkE4CgDrURY5dcV3Av7Rihr2yoxq7sUfHWrzTxv1/su4XJRZM YdCkyQ3x/GnRe87kHj7zkzKooWuxI0JEXWpqcVKU= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.124] ([217.251.142.96]) by mail.gmx.com (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MY68T-1j1TZQ1gr7-00YUbU for ; Sun, 09 Feb 2020 12:45:17 +0100 To: Tools Team Discussion From: Julian Reschke Message-ID: <58f74603-d7c8-f0c8-04f4-4b913afa0250@gmx.de> Date: Sun, 9 Feb 2020 12:45:13 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:/k7AMAxpgLRutCnwiwmb51oQQABE29pDbVQAoArN26mitBv0HRJ 8apRYh6o1T0EOQ1fPc71qH3OkuCsx8k5GjrVrYA9mbD864HzWxGvmu84x6k1EtYAvIKqAqV My8U0mKcOqfFe0zjXecJKuceIsNMx4itj6FGogCkn5j00MEjGWvnsJluR5iRp8rRb7ehFYP w5eju0ZRHXo6V8FVD18XQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:BuadUoQ1HvI=:gSROJ1A2XrxAss9m6OJrLf xl7dWwrvrkAPtNudFk3t3+l6cWT7D3IAzjR4vqqYpS+ImAVSmZT1K4FVML8H28yWLPAVvctZS 7j15zQnET+m5rphj14aGyNng65HD8WLQd1We3U+J8OCL1fPzNwKXRij9dktBSAPBVyiIVQ1pd uRu+h+/G3WmPoJjZD30qJa1F4nhXP7VlUthoA+4MBblUSFu6Eykkvel/Hb9vqS8m2qGTsydvA 0RP/w+XRqLnQXRx+EycZIouxtbehzSdYWKkjEw7UJIJGP1xfhLf6HRKrmDT6vAUMFqV1CbTcB sWKyaF+7fLhLBhloCr5YSANpKLOux9HXjeuIsZlxHzuKrRFER01eZM6FyfurudubojwoXTIu3 +R/n7X1DXD3ucXhV2F67YFvoExbyYGtUIfab9pBSr2yxJ/lVXZUql9YKGhJ4k+5RzjILieeEI kX2I5S04GYxDeUfT+OIzm6nOzjfQJ4q/xcknNLDhWLhVso1vOtbNkMk0pWfztbDH7rdYpRzUe oS1A4FXj1HnGeP1wMS7b9QO+d0BLRK7K/Tz79cBQLWlA2q87APvao1gqMG9vlGXNxk4Ih6rdg +Wxd4tT3OhNryyxyh0loo5/cz43sejjYFOr8zrsO8Gmkbrp8ohhib0w04kuO+SdGnN5x2n0F1 NZh50tRVkmTqHXpr0ndN2eBitl0p3Vjib2FZtYyUV/dQN603rpk5G2AbWD8hD0YUQMH4rRa4f Tfc+NEOsNajiK4ZUwIfbiKqnygAofl6duAVKw0d878/CancHnyKmcxGGYI5T96Uh6MTyFUxKo +jeq/EpR+Y3PiOKCiMrkpA0oo3lNlYEl8MOUI/1h3xcRC3padqbqng633943cyk9gU5iFF7MN Ai/OAz+wdVzZLIAVcdK7xsGIgSSpnvDMIVSoyD5NhDzmx6qqd79VwbXNIHQpoWyxyJq2ldPrz 4s3OlaIn+WjC6veFrHeIXFjYkr2O13SZBRABLeRk4peGomrGWjrb+pVTlpj2nUOdxK+7cFFtA XORlaTMxqFfQVjysWo5SFYZDc47sfMrTxAhAlbmOwecoYrl/XotGSDT0kNgMWkraIBq3nLZ/c Oj+7SzIOUBrFA5ubVZITsYW5pKMhOOstea5rjtxsjZUJq3sJjBVTVCu2Vc9QkaRfKB8f6NBZV K1ZgJRSQeiIEXvPiv/pdzAKDELBbOGQb5z7PpsxLuU9r5rgOZX5LBLoDj+rYA95OI1BP+kFwc Xfl24ecyBPsbqsckc Archived-At: Subject: [Tools-discuss] https://xml2rfc.ietf.org/ X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Feb 2020 11:45:27 -0000 ...seems to be down. Best regards, Julian From nobody Sat Feb 15 06:47:06 2020 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 6BE7E1200B1 for ; Sat, 15 Feb 2020 06:47:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.846 X-Spam-Level: X-Spam-Status: No, score=-0.846 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, MALFORMED_FREEMAIL=1.151, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 xumbXA55Phj9 for ; Sat, 15 Feb 2020 06:47:03 -0800 (PST) Received: from mail-wr1-x431.google.com (mail-wr1-x431.google.com [IPv6:2a00:1450:4864:20::431]) (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 B29291200A4 for ; Sat, 15 Feb 2020 06:47:02 -0800 (PST) Received: by mail-wr1-x431.google.com with SMTP id y11so14408717wrt.6 for ; Sat, 15 Feb 2020 06:47:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=user-agent:date:subject:from:to:message-id:thread-topic :mime-version; bh=sajP6eMCc2gNyoDEAOJ6vedfAe/y7BSUQm4Praeq9P4=; b=aH1Q7agbLZL9SaLq1i8xw3dZauhDOQMzLrjgrbccKu7F2ggot522F6g1zgFUgIahFm I0QIQ0gn+2jyMIBGmtm+fL0FK/LCOUIaf7VD3S/bUKHFbJr3PeIccwD7XresqePcVPjK oh8AjyEi5C+OVhwo8cXGJIZyBfx5IGI+xd0WNjJmT+RYhFLoOn/UqeqDzfeeLuZ/LW7R yYXOP197qzMk0gD/aBmHjNnaQG1+ZEF2Lw9fnFTyurYJsPHl8s4Rpt11NPOys/lGlwM2 645Mq1cs2q4slhQAexyDScIVbCxUX7q5iag2SpCt8Un4KSEN2PUbnHAIOtcZc2mzI5m0 cJUQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:mime-version; bh=sajP6eMCc2gNyoDEAOJ6vedfAe/y7BSUQm4Praeq9P4=; b=KW7jLTAPyFN3CKYHblZYptm9KEmFi4K4C9qFUrn/Pag+sny9dJ5CaEBE08cvHKD8pO 0f6A0wysuF7yh5YXckDRHK6HH+rRniWhFx50rfY0RE4pvDnGdxoSkg/MMKxJl1uQl84M y8tmymVhzEWnJoLtVgX0NOkeklQYbiCu193Oc4/NqUulIJmCqwExLhf+cJKylXSkRXrT yiFoUuIfX/UQGPzIV5jcbU6Kvcsif7JP1aYW1gAemxKRqccZkUE7Cx/O0T7EmVsnqQZ1 siDBuBRA5yhDeJZcbBZBCZwF+jhujS8JNw3FmywPi1F5FCF4TUmTYohHk5ofx+aUH6SJ wnAA== X-Gm-Message-State: APjAAAVlRelujFZ8riFkB4+qJG/+QL7eUaAI+DXeS6Lmp8zO1sfEuR6N aAAi/VhDzPU6vB8Pdtlvix0jm54t X-Google-Smtp-Source: APXvYqxE11nqxCV+/mf2Hmo8sGxF5ke3xQ7Pm/BKLY3gGyISVqBlW0eZYM5Mf/WACtzSOb/1s7JT6A== X-Received: by 2002:adf:e543:: with SMTP id z3mr10153948wrm.369.1581778021057; Sat, 15 Feb 2020 06:47:01 -0800 (PST) Received: from [10.0.0.141] (bzq-109-65-61-207.red.bezeqint.net. [109.65.61.207]) by smtp.gmail.com with ESMTPSA id v5sm12082450wrv.86.2020.02.15.06.47.00 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 15 Feb 2020 06:47:00 -0800 (PST) User-Agent: Microsoft-MacOutlook/10.22.0.200209 Date: Sat, 15 Feb 2020 16:46:59 +0200 From: Yaron Sheffer To: Message-ID: <84E3BB2F-9C76-40A6-9D3D-2A4B3909F48C@contoso.com> Thread-Topic: BibXML to Markdown converter Mime-version: 1.0 Content-type: multipart/alternative; boundary="B_3664630020_394051659" Archived-At: Subject: [Tools-discuss] BibXML to Markdown converter X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Feb 2020 14:47:05 -0000 > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --B_3664630020_394051659 Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: quoted-printable I recently had to convert a large number of references from a published RFC= (XML format) back to nicely editable Markdown, and I created this little sc= ript: https://github.com/yaronf/bibxml2md =20 I hope it can be useful to other people, too. =20 Thanks, =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Yaron --B_3664630020_394051659 Content-type: text/html; charset="UTF-8" Content-transfer-encoding: quoted-printable

I recently = had to convert a large number of references from a published RFC (XML format= ) back to nicely editable Markdown, and I created this little script: https://github.com/yaronf/bibxml2md<= /a>

<= o:p> 

I hope it can be useful to other people, too.

 

Thanks,

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 Yaron

--B_3664630020_394051659-- From nobody Thu Feb 20 20:47:11 2020 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 4707E12006D for ; Thu, 20 Feb 2020 20:47:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.997 X-Spam-Level: X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 lC_UpqaStH7P for ; Thu, 20 Feb 2020 20:47:06 -0800 (PST) Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) (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 6632B120639 for ; Thu, 20 Feb 2020 20:47:06 -0800 (PST) Received: by mail-pf1-x429.google.com with SMTP id 84so551206pfy.6 for ; Thu, 20 Feb 2020 20:47:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:message-id:date:to; bh=ssm056ASi8nPk5um+AOH36fOew5FYv3qoX4UNmxPpaQ=; b=U0HtMJMr5jcsGHlMAS52X1twJSY2aORpsuMYoBLa9sGgsdo+gt1ZsoACRCwcRuQZCy ZzXX2QhJYraMy4nfFGKpriXZvaWyY2ntlmGGUZwXp5ibtlDnvI/BTa1KpkovF3nAaZgS dKLBYDFirL4AJ7EZfq/7zqs8+Bu3oVGKDkPp31CARHoS5GmPlPwhw+6hJizigBRwq5/Z 8hwtmwnOfnV2T72aHal2Iu1rrfPK4MBfPlEMyEr8zdC/8dojzNTTBtVeA1Do7U7PtD+q A/sxRQmQa8G0yTSV8g69ziqP0jkBhtjfUVkPp+jSOnqzQzPc4ZLj7vTYPdR35z8cspGj NPHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:to; bh=ssm056ASi8nPk5um+AOH36fOew5FYv3qoX4UNmxPpaQ=; b=HCJVkG4YsZtjjnnBbWsGuODgYtEi4DtQZo5GYR0IN7yTnDIHriMvydaZqR4YGxuErL fBQ0DG8yDjIJAjOjpVzP7CRvaReZA84nt0+xfGUILV+rBU/ford6Md8x0re+4tS5y2Zr jV+w2vKXGuZNBP3XFRkngh/sGeXg1qGWfsObovMWyIOJRbi4ynXbYObaOypnNNbiv77c Y6bM4SNyQlDBuCUDKaOU8k/z0g7LK6vVBjfvdk+69Vja2UNo8UFhu4IeVfFT3F3e0wDK dgkPmZPPVpew4J1pqGus37C7COVToLwC4dH//ASx5lBhzsFqA/s+InFLgz1BB8nnF7m0 tkTA== X-Gm-Message-State: APjAAAXIpsjDRl/K1XB7ME0JlpB2KaI0/s+vXLJIvb42+pQWodQ41JMR BePzSGqmT5ZxOcS1g3OIWU4zv7aB X-Google-Smtp-Source: APXvYqzcI8IJLvDOGYuo4me9/SkPuWXLbEcq87VBr9rP+62nFafefwStYdu4yECaI5e26lDMYECGtw== X-Received: by 2002:a63:7207:: with SMTP id n7mr17874735pgc.253.1582260425197; Thu, 20 Feb 2020 20:47:05 -0800 (PST) Received: from ?IPv6:2601:647:5600:5020:ad08:93b7:5291:2276? ([2601:647:5600:5020:ad08:93b7:5291:2276]) by smtp.gmail.com with ESMTPSA id b3sm1188940pft.73.2020.02.20.20.47.03 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Feb 2020 20:47:04 -0800 (PST) From: Mahesh Jethanandani Content-Type: multipart/alternative; boundary="Apple-Mail=_9BBBAF00-522E-41C8-82EA-E63117C15AD1" Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Message-Id: <417469A6-ABC4-4BB5-BB97-B28BBB9B3F66@gmail.com> Date: Thu, 20 Feb 2020 20:47:02 -0800 To: tools-discuss@ietf.org X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: [Tools-discuss] Idnits-2.16.02 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: Fri, 21 Feb 2020 04:47:09 -0000 --Apple-Mail=_9BBBAF00-522E-41C8-82EA-E63117C15AD1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Henrik, Is there an issue with downloading the status files for some of the = newer RFCs. Using the above version of idnits, I keep getting the = following error. Needless to say, running the same idnits online does = not give the same errors. idnits draft-ietf-idr-bgp-model-08.txt idnits 2.16.02=20 draft-ietf-idr-bgp-model-08.txt: Attempted to download rfc0000 state... Failure fetching the file, proceeding without it. Attempted to download rfc428 state... Failure fetching the file, proceeding without it. Attempted to download rfc8528 state... The downloaded file seems to be corrupt, proceeding with outdated = information. Attempted to download rfc8529 state... Failure fetching the file, proceeding without it. Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): = --------------------------------------------------------------------------= - No issues found here. Checking nits according to = https://www.ietf.org/id-info/1id-guidelines.txt: = --------------------------------------------------------------------------= - No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : = --------------------------------------------------------------------------= - -- The document has examples using IPv4 documentation addresses = according to RFC6890, but does not use any IPv6 documentation addresses. = Maybe there should be IPv6 examples, too? Miscellaneous warnings: = --------------------------------------------------------------------------= - =3D=3D Line 413 has weird spacing: '...fi-name ide...' =3D=3D Line 423 has weird spacing: '...address ine...' =3D=3D Line 441 has weird spacing: '...address ine...' =3D=3D Line 2187 has weird spacing: '...unicast speci...' -- The document date (January 21, 2020) is 30 days in the past. Is = this intentional? Checking references for intended status: Proposed Standard = --------------------------------------------------------------------------= - (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Downref: Normative reference to an RFC: RFC 8528 ** Downref: Normative reference to an RFC: RFC 8529 Summary: 2 errors (**), 0 flaws (~~), 4 warnings (=3D=3D), 2 = comments (--). Run idnits with the --verbose option for more detailed information about the items above. A more detailed output for just one rfc is as follows: + for ref in '$rfcrefs' echo $ref | tr -d "\r" ++ echo 8528 ++ tr -d '\r' + ref=3D8528 + name=3Drfc8528 + num=3D8528 + '[' '!' rfc8528 =3D rfc ']' + download 'rfc8528 state' https://tools.ietf.org/draft/rfc8528/state = /Users/mahesh/.idnits/rfc8528.state 'Doc-rfcnum: 8528' + name=3D'rfc8528 state' + url=3Dhttps://tools.ietf.org/draft/rfc8528/state + file=3D/Users/mahesh/.idnits/rfc8528.state + test=3D'Doc-rfcnum: 8528' + cd /Users/mahesh/.idnits + '[' /Users/mahesh/.idnits/rfc8528.state ']' $FDATE $file.date 2>/dev/null ++ stat -f %Sm -t %Y-%m-%d /Users/mahesh/.idnits/rfc8528.state.date + filedate=3D2020-02-20 tmpfile ++ tmpfile basename $0 +++ basename /usr/local/bin/idnits ++ prefix=3Didnits ++ for tmpdir in '$TMPDIR' '$TMP' '$TEMP' /tmp . ++ '[' -d /var/folders/mk/217qg4m52h9drx2k5ybf76wc000ghf/T/ -a -w = /var/folders/mk/217qg4m52h9drx2k5ybf76wc000ghf/T/ ']' ++ = tmpfn=3D/var/folders/mk/217qg4m52h9drx2k5ybf76wc000ghf/T//idnits-81427.tmp= ++ '[' -f = /var/folders/mk/217qg4m52h9drx2k5ybf76wc000ghf/T//idnits-81427.tmp ']' ++ echo = /var/folders/mk/217qg4m52h9drx2k5ybf76wc000ghf/T//idnits-81427.tmp ++ exit + = tempfile=3D/var/folders/mk/217qg4m52h9drx2k5ybf76wc000ghf/T//idnits-81427.= tmp + debug 'Status file /Users/mahesh/.idnits/rfc8528.state is dated = 2020-02-20.' + '[' '' ']' + '[' 2020-02-20 =3D 2020-02-20 ']' + true --Apple-Mail=_9BBBAF00-522E-41C8-82EA-E63117C15AD1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi = Henrik,

Is there an = issue with downloading the status files for some of the newer RFCs. = Using the above version of idnits, I keep getting the following error. = Needless to say, running the same idnits online does not give the same = errors.

idnits draft-ietf-idr-bgp-model-08.txt
idnits 2.16.02 

draft-ietf-idr-bgp-model-08.txt:
  =  Attempted to download rfc0000 state...
  =  Failure fetching the file, proceeding without it.
   Attempted to download rfc428 state...
   Failure fetching the file, proceeding without = it.
  =  Attempted to download rfc8528 state...
   The = downloaded file seems to be corrupt, proceeding with outdated = information.
   Attempted to download rfc8529 = state...
   Failure fetching the file, proceeding without = it.

  Checking boilerplate required by RFC 5378 and the IETF = Trust (see
  https://trustee.ietf.org/license-info):
  = --------------------------------------------------------------------------= -

  =    No issues found here.

  Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
  = --------------------------------------------------------------------------= -

  =    No issues found here.

  Checking nits according to https://www.ietf.org/id-info/checklist :
  = --------------------------------------------------------------------------= -

  -- = The document has examples using IPv4 documentation addresses = according
     to RFC6890, but does = not use any IPv6 documentation addresses.  Maybe
     there should be IPv6 examples, = too?


  Miscellaneous = warnings:
  = --------------------------------------------------------------------------= -

  =3D=3D = Line 413 has weird spacing: '...fi-name    ide...'

  =3D=3D Line 423 = has weird spacing: '...address    ine...'

  =3D=3D Line 441 = has weird spacing: '...address    ine...'

  =3D=3D Line 2187 = has weird spacing: '...unicast  speci...'

  -- The document date (January = 21, 2020) is 30 days in the past.  Is this
     intentional?


  Checking references for intended status: Proposed = Standard
  = --------------------------------------------------------------------------= -

  =    (See RFCs 3967 and 4897 for information about using = normative
     references to = lower-maturity documents in RFCs)

 = ** Downref: Normative reference to an  RFC: RFC = 8528

  ** Downref: Normative reference to an  RFC: RFC = 8529


     Summary: 2 errors = (**), 0 flaws (~~), 4 warnings (=3D=3D), 2 comments (--).

     Run = idnits with the --verbose option for more detailed information
     about the items above.

A more detailed output = for just one rfc is as follows:

+ for ref in = '$rfcrefs'
echo $ref | tr -d "\r"
++ echo 8528
++ tr -d '\r'
+ ref=3D8528
+ name=3Drfc8528
+ num=3D8528
+ '[' '!' rfc8528 =3D rfc = ']'
+ download 'rfc8528 state' https://tools.ietf.org/draft/rfc8528/state = /Users/mahesh/.idnits/rfc8528.state 'Doc-rfcnum: 8528'
+ name=3D'rfc8528 state'
+ url=3Dhttps://tools.ietf.org/draft/rfc8528/state
+ file=3D/Users/mahesh/.idnits/rfc8528.state
+ test=3D'Doc-rfcnum: 8528'
+ cd = /Users/mahesh/.idnits
+ '[' = /Users/mahesh/.idnits/rfc8528.state ']'
$FDATE = $file.date 2>/dev/null
++ stat -f %Sm -t = %Y-%m-%d /Users/mahesh/.idnits/rfc8528.state.date
+ = filedate=3D2020-02-20
tmpfile
++= tmpfile
basename $0
+++ = basename /usr/local/bin/idnits
++ = prefix=3Didnits
++ for tmpdir in '$TMPDIR' '$TMP' = '$TEMP' /tmp .
++ '[' -d = /var/folders/mk/217qg4m52h9drx2k5ybf76wc000ghf/T/ -a -w = /var/folders/mk/217qg4m52h9drx2k5ybf76wc000ghf/T/ ']'
++ = tmpfn=3D/var/folders/mk/217qg4m52h9drx2k5ybf76wc000ghf/T//idnits-81427.tmp=
++ '[' -f = /var/folders/mk/217qg4m52h9drx2k5ybf76wc000ghf/T//idnits-81427.tmp = ']'
++ echo = /var/folders/mk/217qg4m52h9drx2k5ybf76wc000ghf/T//idnits-81427.tmp
++ exit
+ = tempfile=3D/var/folders/mk/217qg4m52h9drx2k5ybf76wc000ghf/T//idnits-81427.= tmp
+ debug 'Status file = /Users/mahesh/.idnits/rfc8528.state is dated 2020-02-20.'
+ '[' '' ']'
+ '[' 2020-02-20 =3D = 2020-02-20 ']'
+ true


= --Apple-Mail=_9BBBAF00-522E-41C8-82EA-E63117C15AD1-- From nobody Mon Feb 24 10:10:14 2020 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 57EE03A1062 for ; Mon, 24 Feb 2020 10:10:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jWs9Kdo-dHyz for ; Mon, 24 Feb 2020 10:10:10 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB5893A105F for ; Mon, 24 Feb 2020 10:10:09 -0800 (PST) Received: from client-0156.vpn.uni-bremen.de (client-0156.vpn.uni-bremen.de [134.102.107.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 48R98J00GLzyxZ; Mon, 24 Feb 2020 19:10:07 +0100 (CET) From: Carsten Bormann Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mao-Original-Outgoing-Id: 604260607.357648-499aa572e9a97492eb0e7bb8e22dd6f5 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\)) Date: Mon, 24 Feb 2020 19:10:07 +0100 Message-Id: <2E9B6B32-DD2F-4C0F-92F3-9555F58D0DC6@tzi.org> To: tools-discuss@ietf.org X-Mailer: Apple Mail (2.3608.60.0.2.5) Archived-At: Subject: [Tools-discuss] Old IDs in 1id-abstract.txt 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, 24 Feb 2020 18:10:13 -0000 https://tools.ietf.org/id/1id-abstracts.txt has a few each (single-digit) of I-Ds from 2010, 2011, etc. Makes me curious. Are these cobwebs in the ISE process? E.g., https://tools.ietf.org/html/draft-accilent-at-sign-00 is also marked as=20 Draft is active, In: IS-auth-wait Gr=C3=BC=C3=9Fe, Carsten From nobody Wed Feb 26 09:18:26 2020 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 AC4BA3A0D23 for ; Wed, 26 Feb 2020 09:18:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HYqrqZCaw0tb for ; Wed, 26 Feb 2020 09:18:22 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76D3F3A0D21 for ; Wed, 26 Feb 2020 09:18:22 -0800 (PST) Received: from [192.168.217.147] (p548DC4D8.dip0.t-ipconnect.de [84.141.196.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 48SMvd0FC8zyrH; Wed, 26 Feb 2020 18:18:20 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\)) From: Carsten Bormann In-Reply-To: Date: Wed, 26 Feb 2020 18:18:20 +0100 Cc: Michael Richardson , Robert Sparks X-Mao-Original-Outgoing-Id: 604430300.53532-c05259bc59f535b739679bd4c84d4f72 Content-Transfer-Encoding: quoted-printable Message-Id: <0C8935E8-7693-4FAE-85DF-33408D297F15@tzi.org> References: <20191121040335.A47AD120944@ietfa.amsl.com> <253406B7-7911-4971-9ED5-D836606D3B6A@tzi.org> <9898.1574329972@dooku.sandelman.ca> <96dbab15-2b11-4114-8ad0-690047430d68@nostrum.com> To: tools-discuss@ietf.org X-Mailer: Apple Mail (2.3608.60.0.2.5) Archived-At: Subject: Re: [Tools-discuss] SPF rejection of mail to chairs 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, 26 Feb 2020 17:18:25 -0000 Generic, undirected PING=E2=80=A6 Gr=C3=BC=C3=9Fe, Carsten > On 2019-12-20, at 18:33, Carsten Bormann wrote: >=20 > Hi Robert, >=20 >> On Dec 20, 2019, at 17:16, Robert Sparks = wrote: >>=20 >> Hi Carsten - >>=20 >> We're aware of this problem. Unfortunately there is not any quick fix = for it. >>=20 >> The path through the mail processing chain for the aliases is very = different than the path for the mailing lists, and the way we are = applying the current workaround isn't applicable there. >=20 > I suspected so. >=20 > A lot of our processes are set up to make use of the aliases, so in = the end this creates (hidden-terminal like) problems for these as well. >=20 > I=E2=80=99m not sure the majority of mail servers are set up to report = SPF failures as delivery status, so I=E2=80=99m not even sure I know the = extent of this problem. (So far, I have often resorted to the = explanation that some people are too lazy to read my mail, but maybe SPF = vs. forwarding is the real problem.) >=20 >> We are discussing what we can do instead. >=20 > I wonder if there is a way to stay informed about the progress of = issues like this (that are not naturally rooted in the issue tracker of = some piece of software). I mostly brought this up again on the list = because I have no visibility. >=20 > (I also need a better workaround. I wonder if I need to move to = sending IETF mail from a mail account with a ~all SPF setting, like = it=E2=80=99s 2014 again=E2=80=A6 Maybe I can just manually set my =46rom = address to cabo=3D40tzi.org@dmarc.ietf.org?) >=20 > Gr=C3=BC=C3=9Fe, Carsten >=20 > [1]: https://en.wikipedia.org/wiki/Hidden_node_problem >=20 >>=20 >> RjS >>=20 >> On 12/20/19 1:14 AM, Carsten Bormann wrote: >>> On Nov 21, 2019, at 10:52, Michael Richardson = wrote: >>>>> Is there a need for the DMARC hack for the chair aliases, too? >>>> Oh crap, yes we do. >>>> and on all of the Internet-draft author lists. >>> Just fell into the trap again (on a draft=E2=80=A6@ietf.org alias). >>>=20 >>> Where do I need to report this bug to so it gets addressed? >>>=20 >>> Gr=C3=BC=C3=9Fe, Carsten >>>=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 >=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 From nobody Wed Feb 26 14:05:27 2020 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 112473A08C5 for ; Wed, 26 Feb 2020 14:05:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PEjvfKbNAGzd for ; Wed, 26 Feb 2020 14:05:18 -0800 (PST) Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E52993A088C for ; Wed, 26 Feb 2020 14:05:17 -0800 (PST) Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 8092C38982 for ; Wed, 26 Feb 2020 17:04:15 -0500 (EST) Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id E10A8A0 for ; Wed, 26 Feb 2020 17:05:16 -0500 (EST) From: Michael Richardson To: tools-discuss@ietf.org X-Attribution: mcr X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.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: [Tools-discuss] extracting CODE BEGINS blocks 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, 26 Feb 2020 22:05:26 -0000 --=-=-= Content-Type: text/plain I thought that there was some trivial script pointed to on tools.ietf.org that would do the right trick of extracing blocks, along with the filenames. I looked through all the links, but I couldn't see anything. Yes, I can write my own... but.. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl5W65wACgkQgItw+93Q 3WWRkQf+O3TAnUpP7XO7aAn7tbfmqWHlULX/PSPVA/rV+qxiRPaD1/MLLwa+n9Y6 +35Km6ns2S4gBOGMG9xUqrrD9Wcb50LBze0yuMjXJuQpISa3kL1vWpK0uCalA+iP nihOoFhOC/jFuaOEfurk48HUF96ukJVm/9DlRljlLquBGenuvVaRl1ugZ6qrxcMm UNgqGqWhA6YfBm1z/LMfNxjTLmkBz/Y6BulcGSO2cJ9X2e5hIJGzAdpxq+WY7DNT YsNRRcAV8A5nHd8XJ3pTcUgt7utPoq164IVfL4xabBgsLae9TTEoB6bqhoKyXmbD Hs3+AGGfZdihvhuA5q5+boVN0vZ1pw== =2UFF -----END PGP SIGNATURE----- --=-=-=-- From nobody Wed Feb 26 14:08:58 2020 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 BCE863A08B8 for ; Wed, 26 Feb 2020 14:08:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.89 X-Spam-Level: X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=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 XkG307fH-cCi for ; Wed, 26 Feb 2020 14:08:41 -0800 (PST) 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 3D4BA3A08C3 for ; Wed, 26 Feb 2020 14:08:41 -0800 (PST) Received: by mail-qk1-x72d.google.com with SMTP id m2so1176942qka.7 for ; Wed, 26 Feb 2020 14:08:41 -0800 (PST) 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=X3A5OiR4iZLIjv8wmmzVrbXdQ4oQFzMXMJUdGXPTpr0=; b=VPx30fqDGxLg1mXDC+taNDdPlEpegBy+wDMkG1B1eg6BNT/k+/F0KfrRX1STDsVbRA WfbHeRc+GO1DsOIFeN5w35z7WnshII6mb6a2xp0CQaZKlQGc/qV4a2pMhKjn174IQu2u SNeQL80IyDCEX5/q157Vry4eih5q1mog8+hHerXfweTzt7bwcjXbep2AVdWdUZIPDJdx haJVsYpshnLagC/Wan6eICmi92ednv7oOeT7Xp2b4YmC40vyrVIXz3a2bdu8rrBuCYQs 2AZyBiTylq5Hx//N39IDw3dCuymr2theS55Bw8/JYFBJu1GtTiMsd9ibO367ByaQqm4c n40A== 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=X3A5OiR4iZLIjv8wmmzVrbXdQ4oQFzMXMJUdGXPTpr0=; b=Hn4IsAo9GDo5gCngoFUh5Ln8hT6LtIoKP7K+jiuLJySIPJ0bRXPSsOrGGMxdc8+J4A 8frT5Oi41O+vebHtUybfRN+y4rX+LTB6Z+/j1IlpTZqnpNKS7G2a6bzZoYunMdk4/mMV deOMWbrlSb//hZxerN5TRSEmyyzbazO9eg7PyTvhHxaPpIw0z8j/CT+rSWe6BQD+1PcG q59E3hTgR1Y1D5TYS3bFAdhWGJ7zbY1y0kvsN6/Pt/oqi5aqXGpkNrBcsx7VES4lmgs9 TvpzfMfptWcYh074aboQoIFhztRouDs463oo2DiwpbpKm7Z+eTqQ6XozOg+VuJHmTC92 isyA== X-Gm-Message-State: APjAAAVNv2s/MzL4+HUaUOCVgWAmSxrh6MQ6XOSsdeu/c9BbNu0D/8Rp S2GRZqcoZyNnIWAfLwbTigl4fIaGWXLoHCXNbt+0D2HQpd4= X-Google-Smtp-Source: APXvYqz+2M2f7Hcqy14dMj5GfSq1r3pt93A04Qj8fbUGqKMpLZ/WlK4XbkNYHvW7+N0NWamfvK6lqBc3Gjn+yMPkz54= X-Received: by 2002:a37:a8c3:: with SMTP id r186mr1584999qke.37.1582754919485; Wed, 26 Feb 2020 14:08:39 -0800 (PST) MIME-Version: 1.0 References: <32614.1582754716@localhost> In-Reply-To: <32614.1582754716@localhost> From: Warren Kumari Date: Wed, 26 Feb 2020 17:08:03 -0500 Message-ID: To: Michael Richardson Cc: Tools Discussion Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Tools-discuss] extracting CODE BEGINS blocks 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, 26 Feb 2020 22:08:51 -0000 I believe you are looking for rfcstrip, or the updated version at: https://github.com/mbj4668/rfcstrip "Extracts code components, YANG modules and SMIv2 modules from RFCs and Internet Drafts" W On Wed, Feb 26, 2020 at 5:05 PM Michael Richardson wrote: > > > I thought that there was some trivial script pointed to on tools.ietf.org > that would do the right trick of extracing blocks, along with > the filenames. > > I looked through all the links, but I couldn't see anything. > Yes, I can write my own... but.. > > -- > Michael Richardson , Sandelman Software Works > -= IPv6 IoT consulting =- > > > > ___________________________________________________________ > 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 From nobody Wed Feb 26 14:42:13 2020 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 1AF7B3A09D4 for ; Wed, 26 Feb 2020 14:42:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B7Vm29tNatM9 for ; Wed, 26 Feb 2020 14:42:05 -0800 (PST) Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 286BA3A0989 for ; Wed, 26 Feb 2020 14:42:05 -0800 (PST) Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id AAF3338982; Wed, 26 Feb 2020 17:41:02 -0500 (EST) Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 1027AA0; Wed, 26 Feb 2020 17:42:04 -0500 (EST) From: Michael Richardson To: Warren Kumari cc: Tools Discussion In-Reply-To: References: <32614.1582754716@localhost> X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.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] extracting CODE BEGINS blocks 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, 26 Feb 2020 22:42:12 -0000 --=-=-= Content-Type: text/plain Warren Kumari wrote: > I believe you are looking for rfcstrip, or the updated version at: > https://github.com/mbj4668/rfcstrip "Extracts code components, YANG > modules and SMIv2 modules from RFCs and Internet Drafts" Thank you. bookmarked now. In the meantime, I wrote another version, now at: https://github.com/anima-wg/anima-bootstrap/blob/master/extract-figures Pure-perl, with a different set of bugs. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl5W9DsACgkQgItw+93Q 3WVohAgAuFcCIc3sngkqO/rXKfdZthS1DqpSttam64bIVL/lqKqs5BQ5pswo1eRq sDUhsP0K+j0cAuYUGYWESwS1G0AVazEVaNr+3a+dklyzJl1DRjAOskwWz6dBxsv3 g7y9xOALpb5JntLt7nso5SeIIHfQ+5B61BAkSGvSPUHeIiyYxXikqDSg34K6qRfv TXpYaQMzRdfH8rwtqDr7bW648XKJusoBqbhF99CFQ32frZuHhXhfHDKiG25b5hwC AvYcwqGHmuCHONLaEdrB9CujZK/hTqORZ0I6wnFGgfc5nHgJW8RcbtgIzrq4tsYK MiydGOoJu7HSfn5ojsMjk64C1lIyRw== =gOZn -----END PGP SIGNATURE----- --=-=-=-- From nobody Thu Feb 27 06:01:51 2020 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 BC1023A0934 for ; Thu, 27 Feb 2020 06:01:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.888 X-Spam-Level: X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, 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 gWCWAO-Yug4y for ; Thu, 27 Feb 2020 06:01:47 -0800 (PST) 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 D39113A093C for ; Thu, 27 Feb 2020 06:01:46 -0800 (PST) Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id E596238980 for ; Thu, 27 Feb 2020 09:00:42 -0500 (EST) Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id CC5DC60A for ; Thu, 27 Feb 2020 09:01:44 -0500 (EST) From: Michael Richardson To: tools-discuss@ietf.org X-Attribution: mcr X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.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: [Tools-discuss] interim meeting calendar 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: Thu, 27 Feb 2020 14:01:49 -0000 --=-=-= Content-Type: text/plain Do interim meetings get removed from the interim calendar after the date has passed? -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl5Xy8gACgkQgItw+93Q 3WVo9wgAmpiKnlThuZ9vTeUhQIpeeZbVlNYodRO8UTLOi6tOuMr7bpZojGXpzX2Y HFzjOSPlGiubQ8pl/xbda0vaQUpcXVEm1HRCo07B6uI0KHJ/8ncK2Er7sCuRO1Ij hvfDXf7OOpOd3fHaUhOyHs/M4iWbtjiEMpivkjSkyAG+h28RsT8HzynfCgdwSvZ/ pqFR9/aISIQhlr7gbeLS6d/5YTG9nfQ2PZLfEVeEloawNHnfG9wQ2tUGkaLZwTnv 9NbwQLu0mmtuLRpxLzwT6k8S4+Ki0k4wMFdsDG/BLc/0SabYRBJNoqKYFYUa22QE nYhzHdK+Zh/ufa5HPhpEPe64Gv2cMA== =o0or -----END PGP SIGNATURE----- --=-=-=-- From nobody Thu Feb 27 07:12:31 2020 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 85E9C3A0B5F for ; Thu, 27 Feb 2020 07:12:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.078 X-Spam-Level: X-Spam-Status: No, score=-2.078 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) 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 n7xq0ksnUUJB for ; Thu, 27 Feb 2020 07:12:18 -0800 (PST) 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 26F283A0B52 for ; Thu, 27 Feb 2020 07:12:18 -0800 (PST) Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 01RFCG8T039653 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 27 Feb 2020 09:12:17 -0600 (CST) (envelope-from rjsparks@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1582816337; bh=iuroQBMkftxgZLM9m4aL4ueLgewxocH7lJYsjmXgkng=; h=Subject:To:References:From:Date:In-Reply-To; b=Cijf31La4MylzgFbVL7Z3FfEPPaoRV/l4ME9Rjx3ocmS+osLYBlipcLejkHa9L0kP gTw2lDbv9FVrNBmQOzFj5ejJC8cyodkarGlDkGTmH2eUbR44G/NrgHuQBmfVXQ5D6+ RH/7uwMpFRdzmTrsmfzDp564k746a4tOpJ6fOBZU= X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local To: Michael Richardson , tools-discuss@ietf.org References: <26035.1582812104@localhost> From: Robert Sparks Message-ID: <797f1b2e-4556-e0ee-90dc-a3a004b8a233@nostrum.com> Date: Thu, 27 Feb 2020 09:12:16 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: <26035.1582812104@localhost> Content-Type: multipart/alternative; boundary="------------82D825382602684A628C15A2" Content-Language: en-US Archived-At: Subject: Re: [Tools-discuss] interim meeting calendar 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: Thu, 27 Feb 2020 15:12:26 -0000 This is a multi-part message in MIME format. --------------82D825382602684A628C15A2 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit For what's available at and in particular , the answer is yes. The view and that ics are generated when accessed and list meetings that are in the future from that point in time. RjS On 2/27/20 8:01 AM, Michael Richardson wrote: > Do interim meetings get removed from the interim calendar after the date has > passed? > > -- > Michael Richardson , Sandelman Software Works > -= IPv6 IoT consulting =- > > > > > ___________________________________________________________ > 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 --------------82D825382602684A628C15A2 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

For what's available at <https://datatracker.ietf.org/meeting/upcoming> and in particular <https://datatracker.ietf.org/meeting/upcoming.ics>, the answer is yes.

The view and that ics are generated when accessed and list meetings that are in the future from that point in time.

RjS

On 2/27/20 8:01 AM, Michael Richardson wrote:
Do interim meetings get removed from the interim calendar after the date has
passed?

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-





___________________________________________________________
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
--------------82D825382602684A628C15A2-- From nobody Thu Feb 27 07:17:56 2020 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 000E93A0B83 for ; Thu, 27 Feb 2020 07:17:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.078 X-Spam-Level: X-Spam-Status: No, score=-2.078 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) 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 z1oRj3ZZ6jxM for ; Thu, 27 Feb 2020 07:17:50 -0800 (PST) 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 5D3E13A0B57 for ; Thu, 27 Feb 2020 07:17:50 -0800 (PST) Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 01RFHm9T040615 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 27 Feb 2020 09:17:49 -0600 (CST) (envelope-from rjsparks@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1582816670; bh=QWWN1FOa8SZzegECHtgS4b52ZTGEPBXn4/9VI4F4xT0=; h=Subject:From:To:References:Date:In-Reply-To; b=Y8QLVzfqDsHDTF+GuChhvjfpnNYgaKUrtaLt/yepfzkh2jYdwd1lWgzHiFK+t9edw If8YghOrh/mfYBN6pcGtkdRkpiCdyXBCsSRxCEqYBpelpTRg8dUrdp12g+SJZadoFL OheP2RPI8XSkqEmsCYaZLw5ScGY4yUexvuxMizi4= X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local From: Robert Sparks To: Michael Richardson , tools-discuss@ietf.org References: <26035.1582812104@localhost> <797f1b2e-4556-e0ee-90dc-a3a004b8a233@nostrum.com> Message-ID: <417c5ea2-fab0-da81-df3c-353d1a2038b3@nostrum.com> Date: Thu, 27 Feb 2020 09:17:48 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: <797f1b2e-4556-e0ee-90dc-a3a004b8a233@nostrum.com> Content-Type: multipart/alternative; boundary="------------1FC4ABD851B111C46E6E5154" Content-Language: en-US Archived-At: Subject: Re: [Tools-discuss] interim meeting calendar 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: Thu, 27 Feb 2020 15:17:55 -0000 This is a multi-part message in MIME format. --------------1FC4ABD851B111C46E6E5154 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit And fwiw, lists past interims, but doesn't provice an .ics version. RjS On 2/27/20 9:12 AM, Robert Sparks wrote: > > For what's available at > and in particular > , the answer is yes. > > The view and that ics are generated when accessed and list meetings > that are in the future from that point in time. > > RjS > > On 2/27/20 8:01 AM, Michael Richardson wrote: >> Do interim meetings get removed from the interim calendar after the date has >> passed? >> >> -- >> Michael Richardson, Sandelman Software Works >> -= IPv6 IoT consulting =- >> >> >> >> >> ___________________________________________________________ >> 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 athttp://tools.ietf.org/tools/ietfdb >> or send email todatatracker-project@ietf.org >> >> Please report tools.ietf.org bugs at >> http://tools.ietf.org/tools/issues >> or send email towebmaster@tools.ietf.org --------------1FC4ABD851B111C46E6E5154 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

And fwiw, <https://datatracker.ietf.org/meeting/past> lists past interims, but doesn't provice an .ics version.

RjS

On 2/27/20 9:12 AM, Robert Sparks wrote:

For what's available at <https://datatracker.ietf.org/meeting/upcoming> and in particular <https://datatracker.ietf.org/meeting/upcoming.ics>, the answer is yes.

The view and that ics are generated when accessed and list meetings that are in the future from that point in time.

RjS

On 2/27/20 8:01 AM, Michael Richardson wrote:
Do interim meetings get removed from the interim calendar after the date has
passed?

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-





___________________________________________________________
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
--------------1FC4ABD851B111C46E6E5154-- From nobody Thu Feb 27 08:11:23 2020 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 4B5CC3A0BD5 for ; Thu, 27 Feb 2020 08:11:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dmHqXox9Kvjz for ; Thu, 27 Feb 2020 08:11:12 -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 A9A223A0BD4 for ; Thu, 27 Feb 2020 08:11:12 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 533D2300A2E for ; Thu, 27 Feb 2020 11:11:10 -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 5cLxNrdfZuxN for ; Thu, 27 Feb 2020 11:11:08 -0500 (EST) Received: from a860b60074bd.fios-router.home (pool-108-51-198-163.washdc.fios.verizon.net [108.51.198.163]) by mail.smeinc.net (Postfix) with ESMTPSA id 4088F300A20; Thu, 27 Feb 2020 11:11:08 -0500 (EST) From: Russ Housley Content-Type: multipart/mixed; boundary="Apple-Mail=_57C25238-FA8A-4048-8952-9A9E9D182B99" Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Message-Id: <3729CE09-D13F-436D-A917-0DEF91348E31@vigilsec.com> Date: Thu, 27 Feb 2020 11:11:09 -0500 Cc: IETF Tools Development To: Tools Team Discussion X-Mailer: Apple Mail (2.3445.104.11) Archived-At: Subject: [Tools-discuss] Server Transition Briefing 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: Thu, 27 Feb 2020 16:11:14 -0000 --Apple-Mail=_57C25238-FA8A-4048-8952-9A9E9D182B99 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii The IETF Tools Team will hold a one-hour WebEx session (see invite below) on the recent server transition. The goal is to share information about the changes in the server architecture over the last decade and the most recent upgrade that took place on 22 Feb 2020. With this context in mind, there will be time for discussion. Some things we hope to hear about include: - how can the approach to monitoring/alerting be more transparent - how to ensure monitoring/alerting covers the end user experience - how to improve the infrastructure for testing - next steps toward separation of services to reduce fragility and increase flexibility I hope you are able to attend. For the IETF Tools Team, Russ = = = = = = = = Meeting number (access code): 643 457 472 Meeting password: 2tgKWY8VUU8 Wednesday, March 11, 2020 8:00 pm UTC for 1 hour Join by phone Tap to call in from a mobile device (attendees only) 1-650-479-3208 Call-in toll number (US/Canada) Join from a video system or application Dial 643457472@ietf.webex.com You can also dial 173.243.2.68 and enter your meeting number. Join using Microsoft Lync or Microsoft Skype for Business Dial 643457472.ietf@lync.webex.com Need help? Go to http://help.webex.com --Apple-Mail=_57C25238-FA8A-4048-8952-9A9E9D182B99 Content-Disposition: attachment; filename=Webex_Meeting.ics Content-Type: text/calendar; x-unix-mode=0644; name="Webex_Meeting.ics" Content-Transfer-Encoding: quoted-printable BEGIN:VCALENDAR=0APRODID:-//Microsoft=20Corporation//Outlook=2010.0=20= MIMEDIR//EN=0AVERSION:2.0=0AMETHOD:REQUEST=0ABEGIN:VEVENT=0A= ATTENDEE;CN=3D"IETF=20Tools=20Team":MAILTO:tools-discuss@ietf.org=0A= ORGANIZER;CN=3D"Cisco=20Webex":MAILTO:messenger@webex.com=0A= DTSTART:20200311T200000Z=0ADTEND:20200311T210000Z=0A= LOCATION:https://ietf.webex.com/ietf/j.php?MTID=3Dm00937c87933d32f8f66e20a= 62dd8e0a1=0ATRANSP:OPAQUE=0ASEQUENCE:1582818075=0A= UID:74196a3d-1b5a-4065-a2a1-942d4f8157bf=0ADTSTAMP:20200311T200000Z=0A= DESCRIPTION:\n\nJOIN=20WEBEX=20= MEETING\nhttps://ietf.webex.com/ietf/j.php?MTID=3Dm00937c87933d32f8f66e20a= 62dd8e0a1\nMeeting=20number=20(access=20code):=20643=20457=20472\n\nHost=20= key:=20889085\n\nMeeting=20password:=202tgKWY8VUU8\n\n\n\nJOIN=20BY=20= PHONE\n1-650-479-3208=20Call-in=20toll=20number=20(US/Canada)=20\nTap=20= here=20to=20call=20(mobile=20phones=20only,=20hosts=20not=20supported):=20= tel:%2B1-650-479-3208,,*01*643457472%23%23*01*\n\n\nJOIN=20FROM=20A=20= VIDEO=20SYSTEM=20OR=20APPLICATION\nDial=20= sip:643457472@ietf.webex.com\nYou=20can=20also=20dial=20173.243.2.68=20= and=20enter=20your=20meeting=20number.\n\n\nJoin=20using=20Microsoft=20= Lync=20or=20Microsoft=20Skype=20for=20Business\nDial=20= sip:643457472.ietf@lync.webex.com\n\n\n\nCan't=20join=20the=20meeting?=20= Contact=20support=20here:\nhttps://ietf.webex.com/ietf/mc\n\n\nIMPORTANT=20= NOTICE:=20Please=20note=20that=20this=20Webex=20service=20allows=20audio=20= and=20other=20information=20sent=20during=20the=20session=20to=20be=20= recorded,=20which=20may=20be=20discoverable=20in=20a=20legal=20matter.=20= You=20should=20inform=20all=20meeting=20attendees=20prior=20to=20= recording=20if=20you=20intend=20to=20record=20the=20meeting.\n=0A= X-ALT-DESC;FMTTYPE=3Dtext/html:*=20{=20=20=20=20= padding:=200;=20=20=20=20margin:=200;}table=20{=09border-collapse:=20= separate;=20width=20=3D100%;=09border:=200;=09border-spacing:=200;}tr=20= {=09line-height:=2018px;}a,=20td=20{=09font-size:=2014px;=09font-family:=20= Arial;=09color:=20#333;=09word-wrap:=20break-word;=09word-break:=20= normal;=09padding:=200;}.title=20{=09font-size:=2028px;}.image=20{=09= width:=20auto;=09max-width:=20auto;}.footer=20{=09width:=20604px;}.main=20= {}@media=20screen=20and=20(max-device-width:=20800px)=20{=09.title=20{=09= =09font-size:=2022px=20!important;=09}=09.image=20{=09=09width:=20auto=20= !important;=09=09max-width:=20100%=20!important;=09}=09.footer=20{=09=09= width:=20100%=20!important;=09=09max-width:=20604px=20!important=09}=09= .main=20{=09=09width:=20100%=20!important;=09=09max-width:=20604px=20= !important=09}}=09=  =09=09=09=09=09=09= =09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09 =09=09=09=09=09=09= =09=09=09=09=09=09=09=09=09=09
=09=09=09=09= =09=09When=20= it's=20time,=20join=20the=20Webex=20meeting=20here.=09=09=09=09=09=
=09=09=09=09=09=09Meeting=20number=20(access=20code):=20643=20457=20= 472=09=09=09=09=09
=09=09=09= =09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09
=09=09=09=09=09=09Host=20key:=20= 889085=09=09=09=09=09
=09=09= =09
Meeting=20password:2tgKWY8VUU8
=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=09 =09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09= Join=20meeting=09=09=09=09=09=09=09=09= =09=09=09
=09=09=09=09=09=09=09=09=09=20 
 
Join=20by=20phone =20=
Tap=20to=20= call=20in=20from=20a=20mobile=20device=20(attendees=20only) =20=
1-650-479-3208 Call-in=20toll=20number=20= (US/Canada) =20

 
Join=20from=20a=20video=20system=20or=20= application
Dial=20643457472@ietf.webex.com =20
You=20can=20= also=20dial=20173.243.2.68=20and=20enter=20your=20meeting=20= number.=20 =20
 =20
 =20=
Join=20using=20Microsoft=20Lync=20or=20Microsoft=20Skype=20for=20= BusinessDial=20643457472.ietf@lync.webex.com=
=09=09=09=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20 =09=09=09=09= =09=09=09=09=09Need=20= help?=20Go=20to=20http://help.webex.com=09=09=09=09=09=09=09= =09=09=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =09=09=09=09=09= =09=0ASUMMARY:Server=20Transition=20Briefing=0A= PRIORITY:5=0ACLASS:PUBLIC=0AEND:VEVENT=0AEND:VCALENDAR=0A= --Apple-Mail=_57C25238-FA8A-4048-8952-9A9E9D182B99-- From nobody Thu Feb 27 11:44:46 2020 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 C5BBE3A0A4F for ; Thu, 27 Feb 2020 11:44:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.079 X-Spam-Level: X-Spam-Status: No, score=-2.079 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) 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 IByOA6Ig8fQr for ; Thu, 27 Feb 2020 11:44:41 -0800 (PST) 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 021183A0A4E for ; Thu, 27 Feb 2020 11:44:40 -0800 (PST) Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 01RJiccp085393 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 27 Feb 2020 13:44:40 -0600 (CST) (envelope-from rjsparks@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1582832680; bh=z0l4VIHfQ3nkuq6MUp4DhfFjNH3q1R9BMcurfMt6io0=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=e2BH5fcj4b9J/wYOxfaO+fsWS1TY7b8Pns+GmZy5Od6W3aQGksKCqK+k7GGw9Dqtp FLI2F7K9UB0Lwoah889QamrQDy1i05IfqPRkWh3Zy5V6pYEicFSGvgR9sPAu0v2s/z x9SLkm0NoR530xMwbZXCuRfKGBjvj/ZKO3PUiWwk= X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local To: Carsten Bormann , tools-discuss@ietf.org Cc: Michael Richardson References: <20191121040335.A47AD120944@ietfa.amsl.com> <253406B7-7911-4971-9ED5-D836606D3B6A@tzi.org> <9898.1574329972@dooku.sandelman.ca> <96dbab15-2b11-4114-8ad0-690047430d68@nostrum.com> <0C8935E8-7693-4FAE-85DF-33408D297F15@tzi.org> From: Robert Sparks Message-ID: <7f34680e-4fe8-cf17-a0e9-d3696d509a6f@nostrum.com> Date: Thu, 27 Feb 2020 13:44:38 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: <0C8935E8-7693-4FAE-85DF-33408D297F15@tzi.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [Tools-discuss] SPF rejection of mail to chairs 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: Thu, 27 Feb 2020 19:44:45 -0000 Hi Carsten - The situation hasn't changed so far. Our efforts the last few weeks have been focused on the server replacement and finalizing the python2/3 transitions. I expect we will get to spend some time talking about changing the behavior of the draft and chair aliases while we're in Vancouver. I understand your point about not having a place to go to follow the status things like this, and am looking for ways to better provide that. RjS On 2/26/20 11:18 AM, Carsten Bormann wrote: > Generic, undirected PING… > > Grüße, Carsten > > >> On 2019-12-20, at 18:33, Carsten Bormann wrote: >> >> Hi Robert, >> >>> On Dec 20, 2019, at 17:16, Robert Sparks wrote: >>> >>> Hi Carsten - >>> >>> We're aware of this problem. Unfortunately there is not any quick fix for it. >>> >>> The path through the mail processing chain for the aliases is very different than the path for the mailing lists, and the way we are applying the current workaround isn't applicable there. >> I suspected so. >> >> A lot of our processes are set up to make use of the aliases, so in the end this creates (hidden-terminal like) problems for these as well. >> >> I’m not sure the majority of mail servers are set up to report SPF failures as delivery status, so I’m not even sure I know the extent of this problem. (So far, I have often resorted to the explanation that some people are too lazy to read my mail, but maybe SPF vs. forwarding is the real problem.) >> >>> We are discussing what we can do instead. >> I wonder if there is a way to stay informed about the progress of issues like this (that are not naturally rooted in the issue tracker of some piece of software). I mostly brought this up again on the list because I have no visibility. >> >> (I also need a better workaround. I wonder if I need to move to sending IETF mail from a mail account with a ~all SPF setting, like it’s 2014 again… Maybe I can just manually set my From address to cabo=40tzi.org@dmarc.ietf.org?) >> >> Grüße, Carsten >> >> [1]: https://en.wikipedia.org/wiki/Hidden_node_problem >> >>> RjS >>> >>> On 12/20/19 1:14 AM, Carsten Bormann wrote: >>>> On Nov 21, 2019, at 10:52, Michael Richardson wrote: >>>>>> Is there a need for the DMARC hack for the chair aliases, too? >>>>> Oh crap, yes we do. >>>>> and on all of the Internet-draft author lists. >>>> Just fell into the trap again (on a draft…@ietf.org alias). >>>> >>>> Where do I need to report this bug to so it gets addressed? >>>> >>>> Grüße, Carsten >>>> >>>> ___________________________________________________________ >>>> 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 >> ___________________________________________________________ >> 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 Thu Feb 27 11:55:11 2020 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 185743A0AA4 for ; Thu, 27 Feb 2020 11:55:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bus1nysB2yS5 for ; Thu, 27 Feb 2020 11:55:06 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 067663A0A9F for ; Thu, 27 Feb 2020 11:55:06 -0800 (PST) Received: from [192.168.217.147] (p548DC4D8.dip0.t-ipconnect.de [84.141.196.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 48T3L01RdbzytD; Thu, 27 Feb 2020 20:55:04 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\)) From: Carsten Bormann In-Reply-To: <7f34680e-4fe8-cf17-a0e9-d3696d509a6f@nostrum.com> Date: Thu, 27 Feb 2020 20:55:03 +0100 Cc: tools-discuss@ietf.org, Michael Richardson X-Mao-Original-Outgoing-Id: 604526103.673135-182eebacc7fb7e423ec422c103145674 Content-Transfer-Encoding: quoted-printable Message-Id: <73AA0A63-585C-4612-9995-D9CAF79F79FD@tzi.org> References: <20191121040335.A47AD120944@ietfa.amsl.com> <253406B7-7911-4971-9ED5-D836606D3B6A@tzi.org> <9898.1574329972@dooku.sandelman.ca> <96dbab15-2b11-4114-8ad0-690047430d68@nostrum.com> <0C8935E8-7693-4FAE-85DF-33408D297F15@tzi.org> <7f34680e-4fe8-cf17-a0e9-d3696d509a6f@nostrum.com> To: Robert Sparks X-Mailer: Apple Mail (2.3608.60.0.2.5) Archived-At: Subject: Re: [Tools-discuss] SPF rejection of mail to chairs 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: Thu, 27 Feb 2020 19:55:10 -0000 Hi Robert, thanks for replying. Certainly keeping the system running is more = urgent than solving this particular problem. I=E2=80=99m looking forward to the March 11 briefing; I hope I can make = it (it=E2=80=99s going to be 21:00 here). I particularly like that you = plan to discuss monitoring and knowing whether user-visible features = actually work; my favorite way of improving service quality further. = Let me hint that I=E2=80=99ll be bringing up performance (response time) = monitoring in that vein. And I hope we can talk in Vancouver despite the current troubles=E2=80=A6 Gr=C3=BC=C3=9Fe, Carsten > On 2020-02-27, at 20:44, Robert Sparks wrote: >=20 > Hi Carsten - >=20 > The situation hasn't changed so far. Our efforts the last few weeks = have been focused on the server replacement and finalizing the python2/3 = transitions. I expect we will get to spend some time talking about = changing the behavior of the draft and chair aliases while we're in = Vancouver. >=20 > I understand your point about not having a place to go to follow the = status things like this, and am looking for ways to better provide that. >=20 > RjS >=20 > On 2/26/20 11:18 AM, Carsten Bormann wrote: >> Generic, undirected PING=E2=80=A6 >>=20 >> Gr=C3=BC=C3=9Fe, Carsten >>=20 >>=20 >>> On 2019-12-20, at 18:33, Carsten Bormann wrote: >>>=20 >>> Hi Robert, >>>=20 >>>> On Dec 20, 2019, at 17:16, Robert Sparks = wrote: >>>>=20 >>>> Hi Carsten - >>>>=20 >>>> We're aware of this problem. Unfortunately there is not any quick = fix for it. >>>>=20 >>>> The path through the mail processing chain for the aliases is very = different than the path for the mailing lists, and the way we are = applying the current workaround isn't applicable there. >>> I suspected so. >>>=20 >>> A lot of our processes are set up to make use of the aliases, so in = the end this creates (hidden-terminal like) problems for these as well. >>>=20 >>> I=E2=80=99m not sure the majority of mail servers are set up to = report SPF failures as delivery status, so I=E2=80=99m not even sure I = know the extent of this problem. (So far, I have often resorted to the = explanation that some people are too lazy to read my mail, but maybe SPF = vs. forwarding is the real problem.) >>>=20 >>>> We are discussing what we can do instead. >>> I wonder if there is a way to stay informed about the progress of = issues like this (that are not naturally rooted in the issue tracker of = some piece of software). I mostly brought this up again on the list = because I have no visibility. >>>=20 >>> (I also need a better workaround. I wonder if I need to move to = sending IETF mail from a mail account with a ~all SPF setting, like = it=E2=80=99s 2014 again=E2=80=A6 Maybe I can just manually set my =46rom = address to cabo=3D40tzi.org@dmarc.ietf.org?) >>>=20 >>> Gr=C3=BC=C3=9Fe, Carsten >>>=20 >>> [1]: https://en.wikipedia.org/wiki/Hidden_node_problem >>>=20 >>>> RjS >>>>=20 >>>> On 12/20/19 1:14 AM, Carsten Bormann wrote: >>>>> On Nov 21, 2019, at 10:52, Michael Richardson = wrote: >>>>>>> Is there a need for the DMARC hack for the chair aliases, too? >>>>>> Oh crap, yes we do. >>>>>> and on all of the Internet-draft author lists. >>>>> Just fell into the trap again (on a draft=E2=80=A6@ietf.org = alias). >>>>>=20 >>>>> Where do I need to report this bug to so it gets addressed? >>>>>=20 >>>>> Gr=C3=BC=C3=9Fe, Carsten >>>>>=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 >>> ___________________________________________________________ >>> 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 From nobody Thu Feb 27 12:02:38 2020 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 1497C3A0B1A for ; Thu, 27 Feb 2020 12:02:30 -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, 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 Zaj1gNk8o56I; Thu, 27 Feb 2020 12:02:27 -0800 (PST) Received: from jays-mbp.localdomain (unknown [158.140.230.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id E48583A0ADC; Thu, 27 Feb 2020 12:02:26 -0800 (PST) From: Jay Daley Message-Id: <582A17E3-4599-49CC-8C01-282C46B0D083@ietf.org> Content-Type: multipart/alternative; boundary="Apple-Mail=_8435EC87-B4AB-45AF-8795-15BB37273A33" Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\)) Date: Fri, 28 Feb 2020 09:02:24 +1300 In-Reply-To: <73AA0A63-585C-4612-9995-D9CAF79F79FD@tzi.org> Cc: tools-discuss@ietf.org To: Carsten Bormann References: <20191121040335.A47AD120944@ietfa.amsl.com> <253406B7-7911-4971-9ED5-D836606D3B6A@tzi.org> <9898.1574329972@dooku.sandelman.ca> <96dbab15-2b11-4114-8ad0-690047430d68@nostrum.com> <0C8935E8-7693-4FAE-85DF-33408D297F15@tzi.org> <7f34680e-4fe8-cf17-a0e9-d3696d509a6f@nostrum.com> <73AA0A63-585C-4612-9995-D9CAF79F79FD@tzi.org> X-Mailer: Apple Mail (2.3608.60.0.2.5) Archived-At: Subject: Re: [Tools-discuss] SPF rejection of mail to chairs 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: Thu, 27 Feb 2020 20:02:37 -0000 --Apple-Mail=_8435EC87-B4AB-45AF-8795-15BB37273A33 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Carsten > On 28/02/2020, at 8:55 AM, Carsten Bormann wrote: >=20 > Hi Robert, >=20 > thanks for replying. Certainly keeping the system running is more = urgent than solving this particular problem. >=20 > I=E2=80=99m looking forward to the March 11 briefing; I hope I can = make it (it=E2=80=99s going to be 21:00 here). I particularly like that = you plan to discuss monitoring and knowing whether user-visible features = actually work; my favorite way of improving service quality further. = Let me hint that I=E2=80=99ll be bringing up performance (response time) = monitoring in that vein. Those points were raised by me and for the monitoring I certainly want = to see performance monitoring considered. If you=E2=80=99re not already = aware, there are two cloud services gaining a strong foothold in this = area - Pingdom for state monitoring and New Relic for performance = monitoring. Both of those can be linked into something like = statuspage.io to give end users immediate = visibility into current status and any issues. Jay >=20 > And I hope we can talk in Vancouver despite the current troubles=E2=80=A6= >=20 > Gr=C3=BC=C3=9Fe, Carsten >=20 >=20 >> On 2020-02-27, at 20:44, Robert Sparks wrote: >>=20 >> Hi Carsten - >>=20 >> The situation hasn't changed so far. Our efforts the last few weeks = have been focused on the server replacement and finalizing the python2/3 = transitions. I expect we will get to spend some time talking about = changing the behavior of the draft and chair aliases while we're in = Vancouver. >>=20 >> I understand your point about not having a place to go to follow the = status things like this, and am looking for ways to better provide that. >>=20 >> RjS >>=20 >> On 2/26/20 11:18 AM, Carsten Bormann wrote: >>> Generic, undirected PING=E2=80=A6 >>>=20 >>> Gr=C3=BC=C3=9Fe, Carsten >>>=20 >>>=20 >>>> On 2019-12-20, at 18:33, Carsten Bormann wrote: >>>>=20 >>>> Hi Robert, >>>>=20 >>>>> On Dec 20, 2019, at 17:16, Robert Sparks = wrote: >>>>>=20 >>>>> Hi Carsten - >>>>>=20 >>>>> We're aware of this problem. Unfortunately there is not any quick = fix for it. >>>>>=20 >>>>> The path through the mail processing chain for the aliases is very = different than the path for the mailing lists, and the way we are = applying the current workaround isn't applicable there. >>>> I suspected so. >>>>=20 >>>> A lot of our processes are set up to make use of the aliases, so in = the end this creates (hidden-terminal like) problems for these as well. >>>>=20 >>>> I=E2=80=99m not sure the majority of mail servers are set up to = report SPF failures as delivery status, so I=E2=80=99m not even sure I = know the extent of this problem. (So far, I have often resorted to the = explanation that some people are too lazy to read my mail, but maybe SPF = vs. forwarding is the real problem.) >>>>=20 >>>>> We are discussing what we can do instead. >>>> I wonder if there is a way to stay informed about the progress of = issues like this (that are not naturally rooted in the issue tracker of = some piece of software). I mostly brought this up again on the list = because I have no visibility. >>>>=20 >>>> (I also need a better workaround. I wonder if I need to move to = sending IETF mail from a mail account with a ~all SPF setting, like = it=E2=80=99s 2014 again=E2=80=A6 Maybe I can just manually set my =46rom = address to cabo=3D40tzi.org@dmarc.ietf.org?) >>>>=20 >>>> Gr=C3=BC=C3=9Fe, Carsten >>>>=20 >>>> [1]: https://en.wikipedia.org/wiki/Hidden_node_problem >>>>=20 >>>>> RjS >>>>>=20 >>>>> On 12/20/19 1:14 AM, Carsten Bormann wrote: >>>>>> On Nov 21, 2019, at 10:52, Michael Richardson = wrote: >>>>>>>> Is there a need for the DMARC hack for the chair aliases, too? >>>>>>> Oh crap, yes we do. >>>>>>> and on all of the Internet-draft author lists. >>>>>> Just fell into the trap again (on a draft=E2=80=A6@ietf.org = alias). >>>>>>=20 >>>>>> Where do I need to report this bug to so it gets addressed? >>>>>>=20 >>>>>> Gr=C3=BC=C3=9Fe, Carsten >>>>>>=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 >>>> ___________________________________________________________ >>>> Tools-discuss mailing list >>>> Tools-discuss@ietf.org >>>> https://www.ietf.org/mailman/listinfo/tools-discuss >>>>=20 >>>> Please report datatracker.ietf.org and mailarchive.ietf.org >>>> bugs at http://tools.ietf.org/tools/ietfdb >>>> or send email to datatracker-project@ietf.org >>>>=20 >>>> Please report tools.ietf.org bugs at >>>> http://tools.ietf.org/tools/issues >>>> or send email to webmaster@tools.ietf.org >>=20 >> ___________________________________________________________ >> Tools-discuss mailing list >> Tools-discuss@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-discuss >>=20 >> Please report datatracker.ietf.org and mailarchive.ietf.org >> bugs at http://tools.ietf.org/tools/ietfdb >> or send email to datatracker-project@ietf.org >>=20 >> Please report tools.ietf.org bugs at >> http://tools.ietf.org/tools/issues >> or send email to webmaster@tools.ietf.org >=20 > ___________________________________________________________ > 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 Jay Daley IETF Executive Director jay@ietf.org +64 21 678840 --Apple-Mail=_8435EC87-B4AB-45AF-8795-15BB37273A33 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Carsten

On 28/02/2020, at 8:55 AM, = Carsten Bormann <cabo@tzi.org> wrote:

Hi = Robert,

thanks for replying. =  Certainly keeping the system running is more urgent than solving = this particular problem.

I=E2=80=99m = looking forward to the March 11 briefing; I hope I can make it (it=E2=80=99= s going to be 21:00 here).  I particularly like that you plan to = discuss monitoring and knowing whether user-visible features actually = work; my favorite way of improving service quality further.  Let me = hint that I=E2=80=99ll be bringing up performance (response time) = monitoring in that vein.

Those points were raised by me and for the = monitoring I certainly want to see performance monitoring considered. =  If you=E2=80=99re not already aware, there are two cloud services = gaining a strong foothold in this area - Pingdom for state monitoring = and New Relic for performance monitoring.  Both of those can be = linked into something like statuspage.io to give end users immediate visibility = into current status and any issues.

Jay


And I hope we = can talk in Vancouver despite the current troubles=E2=80=A6

Gr=C3=BC=C3=9Fe, Carsten


On = 2020-02-27, at 20:44, Robert Sparks <rjsparks@nostrum.com> wrote:

Hi Carsten -

The situation = hasn't changed so far. Our efforts the last few weeks have been focused = on the server replacement and finalizing the python2/3 transitions. I = expect we will get to spend some time talking about changing the = behavior of the draft and chair aliases while we're in Vancouver.

I understand your point about not having a = place to go to follow the status things like this, and am looking for = ways to better provide that.

RjS

On 2/26/20 11:18 AM, Carsten Bormann wrote:
Generic, undirected = PING=E2=80=A6

Gr=C3=BC=C3=9Fe, Carsten


On 2019-12-20, at 18:33, Carsten Bormann <cabo@tzi.org> wrote:

Hi Robert,

On Dec 20, 2019, at = 17:16, Robert Sparks <rjsparks@nostrum.com> wrote:

Hi Carsten -

We're aware of this = problem. Unfortunately there is not any quick fix for it.

The path through the mail processing chain for = the aliases is very different than the path for the mailing lists, and = the way we are applying the current workaround isn't applicable = there.
I suspected so.

A lot of our processes are set up to make use of the aliases, = so in the end this creates  (hidden-terminal like) problems for = these as well.

I=E2=80=99m not sure the = majority of mail servers are set up to report SPF failures as delivery = status, so I=E2=80=99m not even sure I know the extent of this problem. =  (So far, I have often resorted to the explanation that some people = are too lazy to read my mail, but maybe SPF vs. forwarding is the real = problem.)

We are discussing what we can do instead.
I wonder if there is a way to stay informed = about the progress of issues like this (that are not naturally rooted in = the issue tracker of some piece of software).  I mostly brought = this up again on the list because I have no visibility.

(I also need a better workaround.  I wonder if I need to = move to sending IETF mail from a mail account with a ~all SPF setting, = like it=E2=80=99s 2014 again=E2=80=A6  Maybe I can just manually = set my =46rom address to cabo=3D40tzi.org@dmarc.ietf.org?)

Gr=C3=BC=C3=9Fe, Carsten

[1]: https://en.wikipedia.org/wiki/Hidden_node_problem

RjS

On 12/20/19 1:14 AM, Carsten Bormann wrote:
On Nov 21, 2019, at = 10:52, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
Is there a = need for the DMARC hack for the chair aliases, too?
Oh crap, yes we do.
and on all of = the Internet-draft author lists.
Just fell = into the trap again (on a draft=E2=80=A6@ietf.org alias).

Where do I need to report this bug to so it = gets addressed?

Gr=C3=BC=C3=9Fe, Carsten

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

___________________________________________________________
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

___________________________________________________________
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

-- 
Jay Daley
IETF = Executive Director
jay@ietf.org
+64 21 678840

= --Apple-Mail=_8435EC87-B4AB-45AF-8795-15BB37273A33-- From nobody Thu Feb 27 13:20:17 2020 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 C82133A0C30 for ; Thu, 27 Feb 2020 13:20:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zLkPX6LJ7B8X for ; Thu, 27 Feb 2020 13:20:13 -0800 (PST) Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (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 296A23A0C2F for ; Thu, 27 Feb 2020 13:20:12 -0800 (PST) Received: from steel.local (sfosf0017s350801.wiline.com [64.71.6.2] (may be forged)) (authenticated bits=0) by v2.bluepopcorn.net (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id 01RLK943014574 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 27 Feb 2020 13:20:10 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bluepopcorn.net; s=supersize; t=1582838412; bh=aQaMvYxchwskqZDyBoRoeRnH1X+9L641iYKS/9qBPOw=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=RVzB8Iedgv8zic1hN+cV9jJQyXqCApXdNLH3ZIJdpV6xdUvYSGE6AoP+MyMxbcVVt pJZjsmZb1gUBC95Lw4IvBREf5+xz3zruS0Tls9Q4hOndIocugz7I9cKnAiVFKfREto vhb1Xd2v/l+O9zBZvwi7b8nW5cJTZsMP55xtBC8E= To: Carsten Bormann , Robert Sparks Cc: Michael Richardson , tools-discuss@ietf.org References: <20191121040335.A47AD120944@ietfa.amsl.com> <253406B7-7911-4971-9ED5-D836606D3B6A@tzi.org> <9898.1574329972@dooku.sandelman.ca> <96dbab15-2b11-4114-8ad0-690047430d68@nostrum.com> <0C8935E8-7693-4FAE-85DF-33408D297F15@tzi.org> <7f34680e-4fe8-cf17-a0e9-d3696d509a6f@nostrum.com> <73AA0A63-585C-4612-9995-D9CAF79F79FD@tzi.org> From: Jim Fenton Autocrypt: addr=fenton@bluepopcorn.net; prefer-encrypt=mutual; keydata= mQINBFJNz0MBEADME6UoNSsTvSDJOdzL4yWfH4HTTOOZZPUcM/at38j4joeBb2PdatlwCBtk 9ZjupxFK+Qh5NZC19Oa6CHo0vlqw7V1hx1MUhmSPbzKRcNFhJu0KcQdniI8qmsqoG50IELXN BPI5OEZ3chYHpoXXi2+VCkjXJyeoqRNwNdv6QPGg6O1FMbB+AcIZj3x5U18LnJnXv1i+1vBq CxbMP43VmryPf8BLufcEciXpMEHydHbrEBZb/r7SBkUhdQXjxRNcWOLeYvOVUOOrr1c+jvqm DEbTWUJVRnUro/WpZQBffFnymR0jjkdAa8eOVl/nF2oMLbaBsOMvxCRSSEcGhuqwbEappNVT 1nuBTbkJT/GGcXxc+lEx9uNj86oYC4384VZJMTd1BRI4qPXImNZCIdmpKegK743B6xxN6Qh1 Tg167pn9429JENQE/AFIVX5B/gpsg7Aq+3rmz9H6GbfovPvFV3TBTgsHCHAMC8XU+S4fhcqN PN0lbUeyb7g6wxaE+dYqC7TExx7G3prw4v66y0qS7ow/Cfw8XXOEkaFQ4XwP7nvfILT+9CcU yS8I40vlDFU9Wnt56CbGz0ZVQgHnwyPXL+S9kCcIwRLFx1M79s6T6qwX1TXadfpbi1uIw7XG TiPDT8Pk6i2y22oSSROyYD4D+wOhVkkvO0S8iZ3+LhAYUx86nwARAQABtCNKaW0gRmVudG9u IDxmZW50b25AYmx1ZXBvcGNvcm4ubmV0PokCVQQTAQIAPwIbAwYLCQgHAwIGFQgCCQoLBBYC AwECHgECF4AWIQS1nUkJe2fEXbvBaacbJaiwFdCfvgUCXVD9ggUJDORhvgAKCRAbJaiwFdCf vgiSEACd3Nem63zL2C6daCFfRzOANkf30Q8AvaRVwhfdFxs+5vETCzbqctrtIAHeqncXjm9G uEJWxecAiHZXKoWUEFECMp3+Saznw0np+c722M4k9xI+mxqbcE0qgpYQgA8zbS/Lbds3f/bk /00jrQg4VMkumONlh+RZVwxAsnWp8efrJsNTn0QOPZavAkPEN59wfyWQ3O4pNY8i3zum8Wge 8NS4BBMyG0fmjWgUq0K2QrTD4AKBslM2IWCLECypP1AOfHKmmTACKFOnzJJ4KspUw3hdBnS1 fvudUC8u26Q3T6rHosRqxGmgW7sQWwAusgMSa/A6zxR6soEBSsMT5Tf+VHebuz1FWE4ogrvJ InvewfYSCYzOQamYYGArcBtAzU00pUzW2Or7SlwZPHHy2EfMd0zvT7mwSYLwwwcCsWc1O/CI xHGea7PBgO3TdR0Ex254yc+NTyxF3isBC/fodF9aNWF6x6SV3VKYJ3U2uqS9ga85dZz8Qeps MwlSEGRVhVVWGbSxy0GxV5Up0yX4vl0kI0c7Tt57JCOoRBpn/lTK/7IEtZK6/uiw98KCy+BM uF7HPsgXjd/AQjSsZIJgDyVY/y7niduqhW2izNEdhV77htVbKHRf2SfJQNudWOIcOhUTlddH kOSjet+MDso61JxrFV4j/8wFno7NwpPIhD//HvKAiLkCDQRSTc9DARAAwZaXYs3OzGlpqvSH 3HR9GjSzIeP0EmsBCjpfIdZbQBwQ3ZREiMGInNxV+xkdjLDg0ctrWzUCUe3plWe5NJkpjqm+ KMc7GKhyeWJ5MZRtVrh0VpFTqi8UwYPWumAYqE1y/U1me/zHpfG9EDwdSYqMkPF76Fy5W+vh ZP2ILKaY8qWSLyH8TPl5mFGBypfT8Q6UuzlRs2aTbsTtBX/qwH7gztMRJSjQtYo20AqCgBBH IA/0xV5qDH7CVYyKyPQ4tJLQ8/xyTysUS5fewrj8lZo/G9SaNtC3CEvrJYwyA0nvYB6+hJPM qMP/tyRXM/9XY3qO4Vxuc+m5fYbTZa5GYAZNNuB5dvqI1U0sFTWBEbpAeabqCQ40ZnFSj+t1 tBuwfj4ey/oJ78WRyg5+VTvPKRRubOmZcnzj5yfTS3VGxAZb4Nsj1S2f3KLP0Z+Cv4dt893I 2JWTChw7jA1omF0QTQaBq140n084PFndBHudrZ3cz+APC89iie2HQ4jGQldXZXnGySHnHlA+ WUyZ9wgOplW9F4Q/Lps1bnuh5VttPVpNfjX8hiV48al+b+ut4nfzXAripIRWF3TL72/6JqgE KNhRKyRn0S6BidieSyHWzqJR3Roi/YNTvyXyLh6i6jtByb3FbnhYf/9olobDpj0E+kTemLrw owre85gwupSphqlzVSUAEQEAAYkCPAQYAQIAJgIbDBYhBLWdSQl7Z8Rdu8FppxslqLAV0J++ BQJdUP9SBQkM5GOPAAoJEBslqLAV0J++vZoP/1shJ+5iImGzvGUTTDJcAX6Wha+22QP0G51Z QGZbeB0gE+gDmRwd2yw0cO3y1sPoTJliUSuZ3DFIjv8CLBgDlrkUnijBWbi5YznsAZkH0vKG ESGzinJC6y/Nzf2TZokKiOaYrTYcZx8x2wxjNO+zsihm/rvhV/YnHEYd9dlV/MjAL3xtHU/9 fNcTDtF3RchADyVCxlqrRUkFj61dHxU+U5JRftyIliLltsy2Nlr4uAsxNX+tpAH2D2HLmjwx bV2fpTnFCVImtuo6ZqNZ8SMk1Xq0fBBdo3acBw42kL/qGIKS9x3NWEy8vsmQXn0QqNBd1Q62 9ghm82mHMTRKnOXqkMgICpZ0HffPf3p7zMkEqWptgEHxE6ZHm9hJMGEf8RED9DCYh+N1uFaM 7ndQPPFKlj80sGmNF9+01mO53hrxeL/WAdGox/STpTb2BDpiyrLdT/2R0vJNEfMxBBYlw1gc g8mPEwHwZ940/qql7e41TkDGUZa2a1WegKLj8hK1pgDDBptcdIvlvuk284jOZ2/jDyaBDsMf 310OoJchJ3977odtSCArybQIwMjTx0rv6dqjsuqP89jqlrGV6izqf1n4p4FNrBSWOSRGaoWD JJVHL4YUhP44G5xDBCtp3TqatLa5F2Rgxj50EFIzOuu9Pg1tBCPP1G+0EiikVTdDkC63X4RG Message-ID: <36ad6759-0bce-ad05-d42c-abdd2083781c@bluepopcorn.net> Date: Thu, 27 Feb 2020 13:20:04 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: <73AA0A63-585C-4612-9995-D9CAF79F79FD@tzi.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US Archived-At: Subject: Re: [Tools-discuss] SPF rejection of mail to chairs 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: Thu, 27 Feb 2020 21:20:16 -0000 To clarify, we're really talking about DMARC rejection rather than SPF rejection, correct? SPF does have a "hardfail" policy, but just about nobody actually rejects mail because the problems with doing that are fairly obvious. DMARC's "reject" policy ((DKIM or SPF) and binding to =46rom address) and the problems with it are harder to understand. But there are a lot of industry people pushing DMARC, so some large domains are enforcing it even though it's an Informational RFC. -Jim On 2/27/20 11:55 AM, Carsten Bormann wrote: > Hi Robert, > > thanks for replying. Certainly keeping the system running is more urge= nt than solving this particular problem. > > I=E2=80=99m looking forward to the March 11 briefing; I hope I can make= it (it=E2=80=99s going to be 21:00 here). I particularly like that you = plan to discuss monitoring and knowing whether user-visible features actu= ally work; my favorite way of improving service quality further. Let me = hint that I=E2=80=99ll be bringing up performance (response time) monitor= ing in that vein. > > And I hope we can talk in Vancouver despite the current troubles=E2=80=A6= > > Gr=C3=BC=C3=9Fe, Carsten > > >> On 2020-02-27, at 20:44, Robert Sparks wrote: >> >> Hi Carsten - >> >> The situation hasn't changed so far. Our efforts the last few weeks ha= ve been focused on the server replacement and finalizing the python2/3 tr= ansitions. I expect we will get to spend some time talking about changing= the behavior of the draft and chair aliases while we're in Vancouver. >> >> I understand your point about not having a place to go to follow the s= tatus things like this, and am looking for ways to better provide that. >> >> RjS >> >> On 2/26/20 11:18 AM, Carsten Bormann wrote: >>> Generic, undirected PING=E2=80=A6 >>> >>> Gr=C3=BC=C3=9Fe, Carsten >>> >>> >>>> On 2019-12-20, at 18:33, Carsten Bormann wrote: >>>> >>>> Hi Robert, >>>> >>>>> On Dec 20, 2019, at 17:16, Robert Sparks wro= te: >>>>> >>>>> Hi Carsten - >>>>> >>>>> We're aware of this problem. Unfortunately there is not any quick f= ix for it. >>>>> >>>>> The path through the mail processing chain for the aliases is very = different than the path for the mailing lists, and the way we are applyin= g the current workaround isn't applicable there. >>>> I suspected so. >>>> >>>> A lot of our processes are set up to make use of the aliases, so in = the end this creates (hidden-terminal like) problems for these as well. >>>> >>>> I=E2=80=99m not sure the majority of mail servers are set up to repo= rt SPF failures as delivery status, so I=E2=80=99m not even sure I know t= he extent of this problem. (So far, I have often resorted to the explana= tion that some people are too lazy to read my mail, but maybe SPF vs. for= warding is the real problem.) >>>> >>>>> We are discussing what we can do instead. >>>> I wonder if there is a way to stay informed about the progress of is= sues like this (that are not naturally rooted in the issue tracker of som= e piece of software). I mostly brought this up again on the list because= I have no visibility. >>>> >>>> (I also need a better workaround. I wonder if I need to move to sen= ding IETF mail from a mail account with a ~all SPF setting, like it=E2=80= =99s 2014 again=E2=80=A6 Maybe I can just manually set my From address t= o cabo=3D40tzi.org@dmarc.ietf.org?) >>>> >>>> Gr=C3=BC=C3=9Fe, Carsten >>>> >>>> [1]: https://en.wikipedia.org/wiki/Hidden_node_problem >>>> >>>>> RjS >>>>> >>>>> On 12/20/19 1:14 AM, Carsten Bormann wrote: >>>>>> On Nov 21, 2019, at 10:52, Michael Richardson wrote: >>>>>>>> Is there a need for the DMARC hack for the chair aliases, too? >>>>>>> Oh crap, yes we do. >>>>>>> and on all of the Internet-draft author lists. >>>>>> Just fell into the trap again (on a draft=E2=80=A6@ietf.org alias)= =2E >>>>>> >>>>>> Where do I need to report this bug to so it gets addressed? >>>>>> >>>>>> Gr=C3=BC=C3=9Fe, Carsten >>>>>> >>>>>> ___________________________________________________________ >>>>>> 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 >>>> ___________________________________________________________ >>>> 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 > ___________________________________________________________ > 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 Thu Feb 27 14:27:27 2020 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 2ABB63A0E31 for ; Thu, 27 Feb 2020 14:27:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nyktj649csH8 for ; Thu, 27 Feb 2020 14:27:13 -0800 (PST) Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A5CF3A0DC9 for ; Thu, 27 Feb 2020 14:27:13 -0800 (PST) Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 0589A38982; Thu, 27 Feb 2020 17:26:10 -0500 (EST) Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 41E4EDB0; Thu, 27 Feb 2020 17:27:12 -0500 (EST) From: Michael Richardson To: Robert Sparks cc: tools-discuss@ietf.org In-Reply-To: <797f1b2e-4556-e0ee-90dc-a3a004b8a233@nostrum.com> References: <26035.1582812104@localhost> <797f1b2e-4556-e0ee-90dc-a3a004b8a233@nostrum.com> X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.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 Content-Transfer-Encoding: quoted-printable Date: Thu, 27 Feb 2020 17:27:12 -0500 Message-ID: <524.1582842432@localhost> Archived-At: Subject: Re: [Tools-discuss] interim meeting calendar 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: Thu, 27 Feb 2020 22:27:25 -0000 Robert Sparks wrote: > For what's available at and > in particular , t= he answer > is yes. okay, it was surprising to see things I attended this week disappear. I usually copy them to my calendar to have a record of what I did "last week", but I didn't do that yet. > The view and that ics are generated when accessed and list meetings = that are > in the future from that point in time. Maybe "future" could be set to -1 day or so? -- ] Never tell me the odds! | ipv6 mesh networ= ks [ ] Michael Richardson, Sandelman Software Works | IoT architect= [ ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails = [ From nobody Thu Feb 27 14:34:05 2020 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 24D953A0DE2 for ; Thu, 27 Feb 2020 14:34:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.079 X-Spam-Level: X-Spam-Status: No, score=-2.079 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) 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 0bU1mx8gupRc for ; Thu, 27 Feb 2020 14:34:00 -0800 (PST) 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 BAD373A0DDA for ; Thu, 27 Feb 2020 14:34:00 -0800 (PST) Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 01RMXxPG014255 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 27 Feb 2020 16:34:00 -0600 (CST) (envelope-from rjsparks@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1582842840; bh=NXnzxcoZlYc30LxCFwVQjRXct5RhcY2JgTJa9O+0F/k=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=ObhoAxCntrOs/LR2eAH7XLzdjYd3tKzFIoNgrR46JCVE8Yg8rMNrsXhT+ash6zmlD qEaYtGAXSRNAz9KvrDmFXFVzvI1FA3TKOh1xytgulsuXoHqlH/Vm82kiw78bxOHrO+ 1fQrSqgPcaFM7S1B7eVEKMHeokDloXMgpgFzGD3E= X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local To: Michael Richardson Cc: tools-discuss@ietf.org References: <26035.1582812104@localhost> <797f1b2e-4556-e0ee-90dc-a3a004b8a233@nostrum.com> <524.1582842432@localhost> From: Robert Sparks Message-ID: <4c7709dd-3b1e-2922-cfb2-25961eb47eb5@nostrum.com> Date: Thu, 27 Feb 2020 16:33:59 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: <524.1582842432@localhost> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: Re: [Tools-discuss] interim meeting calendar 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: Thu, 27 Feb 2020 22:34:03 -0000 Lets see what we can do. I've captured the suggestion at https://trac.tools.ietf.org/tools/ietfdb/ticket/2894 RjS On 2/27/20 4:27 PM, Michael Richardson wrote: > it was surprising to see things I attended this week disappear. > I usually copy them to my calendar to have a record of what I did "last > week", but I didn't do that yet. > > > The view and that ics are generated when accessed and list meetings that are > > in the future from that point in time. > > Maybe "future" could be set to -1 day or so? From nobody Thu Feb 27 14:41:40 2020 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 DC1303A0E12 for ; Thu, 27 Feb 2020 14:41:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5xdd0ftLyCcT for ; Thu, 27 Feb 2020 14:41:35 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47FA33A0DF8 for ; Thu, 27 Feb 2020 14:41:35 -0800 (PST) Received: from [192.168.217.147] (p548DC4D8.dip0.t-ipconnect.de [84.141.196.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 48T7252L3cz105P; Thu, 27 Feb 2020 23:41:33 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\)) From: Carsten Bormann In-Reply-To: <36ad6759-0bce-ad05-d42c-abdd2083781c@bluepopcorn.net> Date: Thu, 27 Feb 2020 23:41:32 +0100 Cc: Robert Sparks , Michael Richardson , tools-discuss@ietf.org X-Mao-Original-Outgoing-Id: 604536092.7544039-6ee089335d5e40af2fb4981e99a25b69 Content-Transfer-Encoding: quoted-printable Message-Id: <8A4D0737-333F-4801-85DA-3FA07D8C9767@tzi.org> References: <20191121040335.A47AD120944@ietfa.amsl.com> <253406B7-7911-4971-9ED5-D836606D3B6A@tzi.org> <9898.1574329972@dooku.sandelman.ca> <96dbab15-2b11-4114-8ad0-690047430d68@nostrum.com> <0C8935E8-7693-4FAE-85DF-33408D297F15@tzi.org> <7f34680e-4fe8-cf17-a0e9-d3696d509a6f@nostrum.com> <73AA0A63-585C-4612-9995-D9CAF79F79FD@tzi.org> <36ad6759-0bce-ad05-d42c-abdd2083781c@bluepopcorn.net> To: Jim Fenton X-Mailer: Apple Mail (2.3608.60.0.2.5) Archived-At: Subject: Re: [Tools-discuss] SPF rejection of mail to chairs 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: Thu, 27 Feb 2020 22:41:38 -0000 On 2020-02-27, at 22:20, Jim Fenton wrote: >=20 > SPF does have a "hardfail" policy, but just about > nobody actually rejects mail I would have thought that, but I now know better=E2=80=A6 Gr=C3=BC=C3=9Fe, Carsten From nobody Thu Feb 27 14:49:50 2020 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 47CC73A03F5 for ; Thu, 27 Feb 2020 14:49:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KaI2vQv_Pq0P for ; Thu, 27 Feb 2020 14:49:36 -0800 (PST) Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5B1D3A0128 for ; Thu, 27 Feb 2020 14:49:36 -0800 (PST) Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 6EDED3897D; Thu, 27 Feb 2020 17:48:30 -0500 (EST) Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id AECE8DB0; Thu, 27 Feb 2020 17:49:32 -0500 (EST) From: Michael Richardson To: Jim Fenton cc: Carsten Bormann , Robert Sparks , tools-discuss@ietf.org In-Reply-To: <36ad6759-0bce-ad05-d42c-abdd2083781c@bluepopcorn.net> References: <20191121040335.A47AD120944@ietfa.amsl.com> <253406B7-7911-4971-9ED5-D836606D3B6A@tzi.org> <9898.1574329972@dooku.sandelman.ca> <96dbab15-2b11-4114-8ad0-690047430d68@nostrum.com> <0C8935E8-7693-4FAE-85DF-33408D297F15@tzi.org> <7f34680e-4fe8-cf17-a0e9-d3696d509a6f@nostrum.com> <73AA0A63-585C-4612-9995-D9CAF79F79FD@tzi.org> <36ad6759-0bce-ad05-d42c-abdd2083781c@bluepopcorn.net> X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.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] SPF rejection of mail to chairs 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: Thu, 27 Feb 2020 22:49:47 -0000 --=-=-= Content-Type: text/plain Jim Fenton wrote: > To clarify, we're really talking about DMARC rejection rather than SPF > rejection, correct? SPF does have a "hardfail" policy, but just about > nobody actually rejects mail because the problems with doing that are > fairly obvious. DMARC's "reject" policy ((DKIM or SPF) and binding to > From address) and the problems with it are harder to understand. But > there are a lot of industry people pushing DMARC, so some large domains > are enforcing it even though it's an Informational RFC. And, I wish we would help them by respecting their p=reject email that arrives by dropping it for our mailing lists, since clearly they don't want email forwarded :-) Yes, it would hurt for a month. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl5YR3wACgkQgItw+93Q 3WXgswf/csEHMAaAmcHonRLtg/l40H6IrFLhg9rhvv3Gcyob/li4xF09sKdWJwVb vr5E1fm4KFUHHcMnQawEdMu67xoCOyMRgBAHJMfREm0CcFeA7ELy6YyCnQzEJpvU /1tLXv6LSdwT91vJTFw6zoxR2UmjBE7zr9PnzcewWlS68zFgK2niPpTCq2kJQnW2 BHWVQ0yGwmN1ZOKdbVHgBSqH7A/uKBb9YncSRhca/XipeI0ay+/NAjxQvDwiG46e 56TmARXB5Rp1WGlIx+w3+tbNNGSiOB/qEs6wCWw+AIgUq1eUnT70jxIICtOTTWIo oaPa7prXSqtq5f1rRuv24PzB2CkIfA== =g+uJ -----END PGP SIGNATURE----- --=-=-=-- From nobody Thu Feb 27 15:09:07 2020 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 76EE53A07E2 for ; Thu, 27 Feb 2020 15:08:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fR9KqXvwOzPH for ; Thu, 27 Feb 2020 15:08:56 -0800 (PST) Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (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 E322A3A0864 for ; Thu, 27 Feb 2020 15:08:56 -0800 (PST) Received: from steel.local (sfosf0017s350801.wiline.com [64.71.6.2] (may be forged)) (authenticated bits=0) by v2.bluepopcorn.net (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id 01RN8smK015829 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 27 Feb 2020 15:08:55 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bluepopcorn.net; s=supersize; t=1582844936; bh=irIn51hVRrWnQwpHkousLFySTmka9ozDwZ7tRU0ArwA=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=FIAxODvzEoAS1JFHEDNlYEYuQd2rhXRoeH9jIypKuwupUucp2cOmrf92ZBXXp6dtg 3aNBxHVCxv5nH5GBWFax9rg1zx2T+zsDMOecHr/Vv5ZckBL2KMiyT1rVmQTon0ws1y IOoqkDsvdM8S97WbPTGcLXvQTO/jYJy2JDJEo05g= To: Carsten Bormann Cc: Robert Sparks , Michael Richardson , tools-discuss@ietf.org References: <20191121040335.A47AD120944@ietfa.amsl.com> <253406B7-7911-4971-9ED5-D836606D3B6A@tzi.org> <9898.1574329972@dooku.sandelman.ca> <96dbab15-2b11-4114-8ad0-690047430d68@nostrum.com> <0C8935E8-7693-4FAE-85DF-33408D297F15@tzi.org> <7f34680e-4fe8-cf17-a0e9-d3696d509a6f@nostrum.com> <73AA0A63-585C-4612-9995-D9CAF79F79FD@tzi.org> <36ad6759-0bce-ad05-d42c-abdd2083781c@bluepopcorn.net> <8A4D0737-333F-4801-85DA-3FA07D8C9767@tzi.org> From: Jim Fenton Autocrypt: addr=fenton@bluepopcorn.net; prefer-encrypt=mutual; keydata= mQINBFJNz0MBEADME6UoNSsTvSDJOdzL4yWfH4HTTOOZZPUcM/at38j4joeBb2PdatlwCBtk 9ZjupxFK+Qh5NZC19Oa6CHo0vlqw7V1hx1MUhmSPbzKRcNFhJu0KcQdniI8qmsqoG50IELXN BPI5OEZ3chYHpoXXi2+VCkjXJyeoqRNwNdv6QPGg6O1FMbB+AcIZj3x5U18LnJnXv1i+1vBq CxbMP43VmryPf8BLufcEciXpMEHydHbrEBZb/r7SBkUhdQXjxRNcWOLeYvOVUOOrr1c+jvqm DEbTWUJVRnUro/WpZQBffFnymR0jjkdAa8eOVl/nF2oMLbaBsOMvxCRSSEcGhuqwbEappNVT 1nuBTbkJT/GGcXxc+lEx9uNj86oYC4384VZJMTd1BRI4qPXImNZCIdmpKegK743B6xxN6Qh1 Tg167pn9429JENQE/AFIVX5B/gpsg7Aq+3rmz9H6GbfovPvFV3TBTgsHCHAMC8XU+S4fhcqN PN0lbUeyb7g6wxaE+dYqC7TExx7G3prw4v66y0qS7ow/Cfw8XXOEkaFQ4XwP7nvfILT+9CcU yS8I40vlDFU9Wnt56CbGz0ZVQgHnwyPXL+S9kCcIwRLFx1M79s6T6qwX1TXadfpbi1uIw7XG TiPDT8Pk6i2y22oSSROyYD4D+wOhVkkvO0S8iZ3+LhAYUx86nwARAQABtCNKaW0gRmVudG9u IDxmZW50b25AYmx1ZXBvcGNvcm4ubmV0PokCVQQTAQIAPwIbAwYLCQgHAwIGFQgCCQoLBBYC AwECHgECF4AWIQS1nUkJe2fEXbvBaacbJaiwFdCfvgUCXVD9ggUJDORhvgAKCRAbJaiwFdCf vgiSEACd3Nem63zL2C6daCFfRzOANkf30Q8AvaRVwhfdFxs+5vETCzbqctrtIAHeqncXjm9G uEJWxecAiHZXKoWUEFECMp3+Saznw0np+c722M4k9xI+mxqbcE0qgpYQgA8zbS/Lbds3f/bk /00jrQg4VMkumONlh+RZVwxAsnWp8efrJsNTn0QOPZavAkPEN59wfyWQ3O4pNY8i3zum8Wge 8NS4BBMyG0fmjWgUq0K2QrTD4AKBslM2IWCLECypP1AOfHKmmTACKFOnzJJ4KspUw3hdBnS1 fvudUC8u26Q3T6rHosRqxGmgW7sQWwAusgMSa/A6zxR6soEBSsMT5Tf+VHebuz1FWE4ogrvJ InvewfYSCYzOQamYYGArcBtAzU00pUzW2Or7SlwZPHHy2EfMd0zvT7mwSYLwwwcCsWc1O/CI xHGea7PBgO3TdR0Ex254yc+NTyxF3isBC/fodF9aNWF6x6SV3VKYJ3U2uqS9ga85dZz8Qeps MwlSEGRVhVVWGbSxy0GxV5Up0yX4vl0kI0c7Tt57JCOoRBpn/lTK/7IEtZK6/uiw98KCy+BM uF7HPsgXjd/AQjSsZIJgDyVY/y7niduqhW2izNEdhV77htVbKHRf2SfJQNudWOIcOhUTlddH kOSjet+MDso61JxrFV4j/8wFno7NwpPIhD//HvKAiLkCDQRSTc9DARAAwZaXYs3OzGlpqvSH 3HR9GjSzIeP0EmsBCjpfIdZbQBwQ3ZREiMGInNxV+xkdjLDg0ctrWzUCUe3plWe5NJkpjqm+ KMc7GKhyeWJ5MZRtVrh0VpFTqi8UwYPWumAYqE1y/U1me/zHpfG9EDwdSYqMkPF76Fy5W+vh ZP2ILKaY8qWSLyH8TPl5mFGBypfT8Q6UuzlRs2aTbsTtBX/qwH7gztMRJSjQtYo20AqCgBBH IA/0xV5qDH7CVYyKyPQ4tJLQ8/xyTysUS5fewrj8lZo/G9SaNtC3CEvrJYwyA0nvYB6+hJPM qMP/tyRXM/9XY3qO4Vxuc+m5fYbTZa5GYAZNNuB5dvqI1U0sFTWBEbpAeabqCQ40ZnFSj+t1 tBuwfj4ey/oJ78WRyg5+VTvPKRRubOmZcnzj5yfTS3VGxAZb4Nsj1S2f3KLP0Z+Cv4dt893I 2JWTChw7jA1omF0QTQaBq140n084PFndBHudrZ3cz+APC89iie2HQ4jGQldXZXnGySHnHlA+ WUyZ9wgOplW9F4Q/Lps1bnuh5VttPVpNfjX8hiV48al+b+ut4nfzXAripIRWF3TL72/6JqgE KNhRKyRn0S6BidieSyHWzqJR3Roi/YNTvyXyLh6i6jtByb3FbnhYf/9olobDpj0E+kTemLrw owre85gwupSphqlzVSUAEQEAAYkCPAQYAQIAJgIbDBYhBLWdSQl7Z8Rdu8FppxslqLAV0J++ BQJdUP9SBQkM5GOPAAoJEBslqLAV0J++vZoP/1shJ+5iImGzvGUTTDJcAX6Wha+22QP0G51Z QGZbeB0gE+gDmRwd2yw0cO3y1sPoTJliUSuZ3DFIjv8CLBgDlrkUnijBWbi5YznsAZkH0vKG ESGzinJC6y/Nzf2TZokKiOaYrTYcZx8x2wxjNO+zsihm/rvhV/YnHEYd9dlV/MjAL3xtHU/9 fNcTDtF3RchADyVCxlqrRUkFj61dHxU+U5JRftyIliLltsy2Nlr4uAsxNX+tpAH2D2HLmjwx bV2fpTnFCVImtuo6ZqNZ8SMk1Xq0fBBdo3acBw42kL/qGIKS9x3NWEy8vsmQXn0QqNBd1Q62 9ghm82mHMTRKnOXqkMgICpZ0HffPf3p7zMkEqWptgEHxE6ZHm9hJMGEf8RED9DCYh+N1uFaM 7ndQPPFKlj80sGmNF9+01mO53hrxeL/WAdGox/STpTb2BDpiyrLdT/2R0vJNEfMxBBYlw1gc g8mPEwHwZ940/qql7e41TkDGUZa2a1WegKLj8hK1pgDDBptcdIvlvuk284jOZ2/jDyaBDsMf 310OoJchJ3977odtSCArybQIwMjTx0rv6dqjsuqP89jqlrGV6izqf1n4p4FNrBSWOSRGaoWD JJVHL4YUhP44G5xDBCtp3TqatLa5F2Rgxj50EFIzOuu9Pg1tBCPP1G+0EiikVTdDkC63X4RG Message-ID: Date: Thu, 27 Feb 2020 15:08:49 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: <8A4D0737-333F-4801-85DA-3FA07D8C9767@tzi.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [Tools-discuss] SPF rejection of mail to chairs 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: Thu, 27 Feb 2020 23:09:05 -0000 On 2/27/20 2:41 PM, Carsten Bormann wrote: > On 2020-02-27, at 22:20, Jim Fenton wrote: >> SPF does have a "hardfail" policy, but just about >> nobody actually rejects mail > I would have thought that, but I now know better… > You're saying that this rejection is actually due to SPF and not DMARC then? If that were the case, it would be a lot easier to remediate (just rewrite the envelope-from address to a different domain). DMARC binds to the From header field, which requires the much uglier rewriting we're all seeing. From nobody Thu Feb 27 21:55:12 2020 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 92E973A10CF for ; Thu, 27 Feb 2020 21:55:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r4qjiY9Pgo3A for ; Thu, 27 Feb 2020 21:55:03 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 870073A10CC for ; Thu, 27 Feb 2020 21:55:03 -0800 (PST) Received: from [192.168.217.147] (p548DC4D8.dip0.t-ipconnect.de [84.141.196.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 48TJfF0bDhz10p1; Fri, 28 Feb 2020 06:55:01 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\)) From: Carsten Bormann In-Reply-To: Date: Fri, 28 Feb 2020 06:55:00 +0100 Cc: Michael Richardson , tools-discuss@ietf.org, Robert Sparks X-Mao-Original-Outgoing-Id: 604562100.5679801-2bd172e5de8fe9ff5732ef5416bd8aaf Content-Transfer-Encoding: quoted-printable Message-Id: References: <20191121040335.A47AD120944@ietfa.amsl.com> <253406B7-7911-4971-9ED5-D836606D3B6A@tzi.org> <9898.1574329972@dooku.sandelman.ca> <96dbab15-2b11-4114-8ad0-690047430d68@nostrum.com> <0C8935E8-7693-4FAE-85DF-33408D297F15@tzi.org> <7f34680e-4fe8-cf17-a0e9-d3696d509a6f@nostrum.com> <73AA0A63-585C-4612-9995-D9CAF79F79FD@tzi.org> <36ad6759-0bce-ad05-d42c-abdd2083781c@bluepopcorn.net> <8A4D0737-333F-4801-85DA-3FA07D8C9767@tzi.org> To: Jim Fenton X-Mailer: Apple Mail (2.3608.60.0.2.5) Archived-At: Subject: Re: [Tools-discuss] SPF rejection of mail to chairs X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Feb 2020 05:55:10 -0000 On 2020-02-28, at 00:08, Jim Fenton wrote: >=20 > You're saying that this rejection is actually due to SPF and not DMARC > then? If that were the case, it would be a lot easier to remediate = (just > rewrite the envelope-from address to a different domain). DMARC binds = to > the =46rom header field, which requires the much uglier rewriting = we're > all seeing. I=E2=80=99m not an expert in nomenclature for ways of making email not = work, so I have instead included an example of the rejection that AMSL = sees when I send mail to IETF aliases. (I probably should collect them more rigorously, as there may be = different situations in other cases.) Gr=C3=BC=C3=9Fe, Carsten (expanded from = ): host cloud8.spamtitan.com[13.58.8.62] said: 550 5.7.1 SPF Policy = Rejection t=3Dietf@augustcellars.com, s=3Dmfrom, id=3Dcabo@tzi.org (in reply to = RCPT TO command) Reporting-MTA: dns; ietfa.amsl.com X-Postfix-Queue-ID: 42C173A0CFD X-Postfix-Sender: rfc822; cabo@tzi.org Arrival-Date: Wed, 26 Feb 2020 09:13:40 -0800 (PST) Final-Recipient: rfc822; ietf@augustcellars.com Original-Recipient: rfc822;expand-cbor-chairs@virtual.ietf.org Action: failed Status: 5.7.1 Remote-MTA: dns; cloud8.spamtitan.com Diagnostic-Code: smtp; 550 5.7.1 SPF Policy Rejection = t=3Dietf@augustcellars.com, s=3Dmfrom, id=3Dcabo@tzi.org From: Carsten Bormann Subject: Re: [Cbor] Interim today Date: 2020-02-26 at 18:13:33 CET To: CBOR Working Group Cc: "cbor@ietf.org" Resent-From: Resent-To: ietf@augustcellars.com, francesca.palombini@ericsson.com= From nobody Sat Feb 29 12:04:50 2020 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 572643A1253 for ; Sat, 29 Feb 2020 12:04:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oouN6TzxIjUM for ; Sat, 29 Feb 2020 12:04:46 -0800 (PST) Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (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 9D4113A1252 for ; Sat, 29 Feb 2020 12:04:46 -0800 (PST) Received: from steel.local ([IPv6:2601:647:4300:2290:dde4:bdf4:df3e:8c13]) (authenticated bits=0) by v2.bluepopcorn.net (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id 01TK4iao021034 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sat, 29 Feb 2020 12:04:45 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bluepopcorn.net; s=supersize; t=1583006686; bh=CgpIbiYx1GrOaEg42SOCOTiwaLm3OEgCzI5+Ma8drz4=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=s+y5VWDfUBiJwvVmbYGJqGcPbo0UOSoHyXVbk0Ccb/Kn8tU4Vo28ORCquZq4wXCgM ia2+oht/aNJNQsRaZfhXJZqLRd1kYoVd05EyhrKKEPVY+uBfsn+2Xb0Yow7nqiYRwF DIEHQwJZpxFN5YU95MRoTwHKoT2LYykmaNUT4ARU= To: Carsten Bormann Cc: tools-discuss@ietf.org References: <20191121040335.A47AD120944@ietfa.amsl.com> <253406B7-7911-4971-9ED5-D836606D3B6A@tzi.org> <9898.1574329972@dooku.sandelman.ca> <96dbab15-2b11-4114-8ad0-690047430d68@nostrum.com> <0C8935E8-7693-4FAE-85DF-33408D297F15@tzi.org> <7f34680e-4fe8-cf17-a0e9-d3696d509a6f@nostrum.com> <73AA0A63-585C-4612-9995-D9CAF79F79FD@tzi.org> <36ad6759-0bce-ad05-d42c-abdd2083781c@bluepopcorn.net> <8A4D0737-333F-4801-85DA-3FA07D8C9767@tzi.org> From: Jim Fenton Autocrypt: addr=fenton@bluepopcorn.net; prefer-encrypt=mutual; keydata= mQINBFJNz0MBEADME6UoNSsTvSDJOdzL4yWfH4HTTOOZZPUcM/at38j4joeBb2PdatlwCBtk 9ZjupxFK+Qh5NZC19Oa6CHo0vlqw7V1hx1MUhmSPbzKRcNFhJu0KcQdniI8qmsqoG50IELXN BPI5OEZ3chYHpoXXi2+VCkjXJyeoqRNwNdv6QPGg6O1FMbB+AcIZj3x5U18LnJnXv1i+1vBq CxbMP43VmryPf8BLufcEciXpMEHydHbrEBZb/r7SBkUhdQXjxRNcWOLeYvOVUOOrr1c+jvqm DEbTWUJVRnUro/WpZQBffFnymR0jjkdAa8eOVl/nF2oMLbaBsOMvxCRSSEcGhuqwbEappNVT 1nuBTbkJT/GGcXxc+lEx9uNj86oYC4384VZJMTd1BRI4qPXImNZCIdmpKegK743B6xxN6Qh1 Tg167pn9429JENQE/AFIVX5B/gpsg7Aq+3rmz9H6GbfovPvFV3TBTgsHCHAMC8XU+S4fhcqN PN0lbUeyb7g6wxaE+dYqC7TExx7G3prw4v66y0qS7ow/Cfw8XXOEkaFQ4XwP7nvfILT+9CcU yS8I40vlDFU9Wnt56CbGz0ZVQgHnwyPXL+S9kCcIwRLFx1M79s6T6qwX1TXadfpbi1uIw7XG TiPDT8Pk6i2y22oSSROyYD4D+wOhVkkvO0S8iZ3+LhAYUx86nwARAQABtCNKaW0gRmVudG9u IDxmZW50b25AYmx1ZXBvcGNvcm4ubmV0PokCVQQTAQIAPwIbAwYLCQgHAwIGFQgCCQoLBBYC AwECHgECF4AWIQS1nUkJe2fEXbvBaacbJaiwFdCfvgUCXVD9ggUJDORhvgAKCRAbJaiwFdCf vgiSEACd3Nem63zL2C6daCFfRzOANkf30Q8AvaRVwhfdFxs+5vETCzbqctrtIAHeqncXjm9G uEJWxecAiHZXKoWUEFECMp3+Saznw0np+c722M4k9xI+mxqbcE0qgpYQgA8zbS/Lbds3f/bk /00jrQg4VMkumONlh+RZVwxAsnWp8efrJsNTn0QOPZavAkPEN59wfyWQ3O4pNY8i3zum8Wge 8NS4BBMyG0fmjWgUq0K2QrTD4AKBslM2IWCLECypP1AOfHKmmTACKFOnzJJ4KspUw3hdBnS1 fvudUC8u26Q3T6rHosRqxGmgW7sQWwAusgMSa/A6zxR6soEBSsMT5Tf+VHebuz1FWE4ogrvJ InvewfYSCYzOQamYYGArcBtAzU00pUzW2Or7SlwZPHHy2EfMd0zvT7mwSYLwwwcCsWc1O/CI xHGea7PBgO3TdR0Ex254yc+NTyxF3isBC/fodF9aNWF6x6SV3VKYJ3U2uqS9ga85dZz8Qeps MwlSEGRVhVVWGbSxy0GxV5Up0yX4vl0kI0c7Tt57JCOoRBpn/lTK/7IEtZK6/uiw98KCy+BM uF7HPsgXjd/AQjSsZIJgDyVY/y7niduqhW2izNEdhV77htVbKHRf2SfJQNudWOIcOhUTlddH kOSjet+MDso61JxrFV4j/8wFno7NwpPIhD//HvKAiLkCDQRSTc9DARAAwZaXYs3OzGlpqvSH 3HR9GjSzIeP0EmsBCjpfIdZbQBwQ3ZREiMGInNxV+xkdjLDg0ctrWzUCUe3plWe5NJkpjqm+ KMc7GKhyeWJ5MZRtVrh0VpFTqi8UwYPWumAYqE1y/U1me/zHpfG9EDwdSYqMkPF76Fy5W+vh ZP2ILKaY8qWSLyH8TPl5mFGBypfT8Q6UuzlRs2aTbsTtBX/qwH7gztMRJSjQtYo20AqCgBBH IA/0xV5qDH7CVYyKyPQ4tJLQ8/xyTysUS5fewrj8lZo/G9SaNtC3CEvrJYwyA0nvYB6+hJPM qMP/tyRXM/9XY3qO4Vxuc+m5fYbTZa5GYAZNNuB5dvqI1U0sFTWBEbpAeabqCQ40ZnFSj+t1 tBuwfj4ey/oJ78WRyg5+VTvPKRRubOmZcnzj5yfTS3VGxAZb4Nsj1S2f3KLP0Z+Cv4dt893I 2JWTChw7jA1omF0QTQaBq140n084PFndBHudrZ3cz+APC89iie2HQ4jGQldXZXnGySHnHlA+ WUyZ9wgOplW9F4Q/Lps1bnuh5VttPVpNfjX8hiV48al+b+ut4nfzXAripIRWF3TL72/6JqgE KNhRKyRn0S6BidieSyHWzqJR3Roi/YNTvyXyLh6i6jtByb3FbnhYf/9olobDpj0E+kTemLrw owre85gwupSphqlzVSUAEQEAAYkCPAQYAQIAJgIbDBYhBLWdSQl7Z8Rdu8FppxslqLAV0J++ BQJdUP9SBQkM5GOPAAoJEBslqLAV0J++vZoP/1shJ+5iImGzvGUTTDJcAX6Wha+22QP0G51Z QGZbeB0gE+gDmRwd2yw0cO3y1sPoTJliUSuZ3DFIjv8CLBgDlrkUnijBWbi5YznsAZkH0vKG ESGzinJC6y/Nzf2TZokKiOaYrTYcZx8x2wxjNO+zsihm/rvhV/YnHEYd9dlV/MjAL3xtHU/9 fNcTDtF3RchADyVCxlqrRUkFj61dHxU+U5JRftyIliLltsy2Nlr4uAsxNX+tpAH2D2HLmjwx bV2fpTnFCVImtuo6ZqNZ8SMk1Xq0fBBdo3acBw42kL/qGIKS9x3NWEy8vsmQXn0QqNBd1Q62 9ghm82mHMTRKnOXqkMgICpZ0HffPf3p7zMkEqWptgEHxE6ZHm9hJMGEf8RED9DCYh+N1uFaM 7ndQPPFKlj80sGmNF9+01mO53hrxeL/WAdGox/STpTb2BDpiyrLdT/2R0vJNEfMxBBYlw1gc g8mPEwHwZ940/qql7e41TkDGUZa2a1WegKLj8hK1pgDDBptcdIvlvuk284jOZ2/jDyaBDsMf 310OoJchJ3977odtSCArybQIwMjTx0rv6dqjsuqP89jqlrGV6izqf1n4p4FNrBSWOSRGaoWD JJVHL4YUhP44G5xDBCtp3TqatLa5F2Rgxj50EFIzOuu9Pg1tBCPP1G+0EiikVTdDkC63X4RG Message-ID: <1aa743fd-cba7-d11e-7259-37dd6e7efdca@bluepopcorn.net> Date: Sat, 29 Feb 2020 12:04:39 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US Archived-At: Subject: Re: [Tools-discuss] SPF rejection of mail to chairs X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Feb 2020 20:04:48 -0000 On 2/27/20 9:55 PM, Carsten Bormann wrote: > On 2020-02-28, at 00:08, Jim Fenton wrote: >> You're saying that this rejection is actually due to SPF and not DMARC= >> then? If that were the case, it would be a lot easier to remediate (ju= st >> rewrite the envelope-from address to a different domain). DMARC binds = to >> the From header field, which requires the much uglier rewriting we're >> all seeing. > I=E2=80=99m not an expert in nomenclature for ways of making email not = work, so I have instead included an example of the rejection that AMSL se= es when I send mail to IETF aliases. > (I probably should collect them more rigorously, as there may be differ= ent situations in other cases.) I stand corrected; the header you sent indeed does represent an SPF rejection and not DMARC. This is happening to you because of your SPF record: tzi.org.=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 86400=C2=A0=C2=A0=C2=A0 IN=C2= =A0=C2=A0=C2=A0 TXT=C2=A0=C2=A0=C2=A0 "v=3Dspf1 mx a:submithost.informatik.uni-bremen.de a:imaphost.informatik.uni-bremen.de a:smtp.uni-bremen.de ip4:134.102.50.0/24 ip4:134.102.51.0/24 ip4:134.102.22.0/24 -all" The -all at the end is requesting that message recipients reject your mail if it doesn't come from one of the named hosts, and augustcellars.com (actually spamtitan.com on their behalf) is doing that.= I'm wondering why I haven't been running into that problem. I just checked and (to my surprise) my domain's SPF record has a -all as well. Perhaps it's because I DKIM-sign my outgoing email (you don't seem to). =46rom a tools standpoint, we could rewrite the envelope-from address, bu= t that would also have the effect of redirecting bounce messages to that address. Unless we rewrote it to an address that redirected back to the original sender. I wonder a bit if there are ways that those rewriting tricks can be abused, though. -Jim