IETF Logo Mail Archive

Re: [dmarc-ietf] Request to accept a new I-D into the WG work items

Scott Kitterman <sklist@kitterman.com> Wed, 07 November 2018 04:54 UTC

Return-Path: <sklist@kitterman.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 965AF130F35 for <dmarc@ietfa.amsl.com>; Tue, 6 Nov 2018 20:54:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=ba8wXueN; dkim=pass (2048-bit key) header.d=kitterman.com header.b=pNY/wQzQ
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 iYltlbSoSDMh for <dmarc@ietfa.amsl.com>; Tue, 6 Nov 2018 20:54:11 -0800 (PST)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82188130F1E for <dmarc@ietf.org>; Tue, 6 Nov 2018 20:54:11 -0800 (PST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201803e; t=1541566449; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from : subject : date; bh=2pGyfvsmL0hEBOcznqQwhrbNvFXb6FA2JCoHTH3fjfQ=; b=ba8wXueN9fxvwBRQZG/zK/QGTHeRUmBi0JKgsuOpk+WHkiVD09iQyn1w U7i+tL6RchbtL+v+NNvooWPsZi+/CA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201803r; t=1541566449; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from : subject : date; bh=2pGyfvsmL0hEBOcznqQwhrbNvFXb6FA2JCoHTH3fjfQ=; b=pNY/wQzQx85Ca306AUJ6J5KW9KgtT+1SJKa9VBfQEznuqzCph3WKVG7e aABleca/yMtJ7h116VDx73Z2EZ22vDjsbKN1w4B9e/qsdN2ku6pqtMVgy8 PQETPt7WCqL7UMZBsp6eZph2CLj3Xysp7hs5QeRnAp/roddTfFdluPcnLO 5n63bcqSe2yb4yIKa2IVdNjhHhnTEEyvTNQXAb/TkHT+Hrx46DZyTNrl+C 3wVH9enSFJa+manDmjTA+rI2OZXE4vA54qYFSg51/UAekt+cRflx5usL0w sK+iWzXhTTelr7ydC2j2BfT279nUSbDtFED7i1GOeFjetFox3RS4Yw==
Received: from kitterma-e6430.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id C66D7C401DD for <dmarc@ietf.org>; Tue, 6 Nov 2018 22:54:09 -0600 (CST)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Tue, 06 Nov 2018 23:54:08 -0500
Message-ID: <4226992.SIzckGkbUk@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-158-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <CAL0qLwa6jE_0DxHZYHu7n3v2nF2b90vWGeBgJB_XyyPj0Oz-ng@mail.gmail.com>
References: <CABuGu1o4E-Svt9N++RaFvO4SATt3Wh1w7gZb1OdBSVRCm7Odmg@mail.gmail.com> <CAL0qLwZXRD6jmbZDR+ETK+N3kW96i8mChaP1yHqsqnyzYw8T3Q@mail.gmail.com> <CAL0qLwa6jE_0DxHZYHu7n3v2nF2b90vWGeBgJB_XyyPj0Oz-ng@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/IH9BjhALi2iXaiOkt1V2J9vztPc>
Subject: Re: [dmarc-ietf] Request to accept a new I-D into the WG work items
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2018 04:54:16 -0000

On Wednesday, November 07, 2018 11:37:24 AM Murray S. Kucherawy wrote:
> On Wed, Nov 7, 2018 at 10:08 AM Murray S. Kucherawy <superuser@gmail.com>
> 
> wrote:
> > My concern with this approach (which doesn't rise to the level of
> > objecting to its application as a WG document, though perhaps it should)
> > is
> > that it is trending toward needing an IANA registry to be queryable in
> > real-time, and I don't believe they are equipped with the infrastructure
> > to
> > provide that kind of service, nor is that likely to happen anytime soon.
> 
> This issue or something like it came up when I was chairing WEIRDS, so
> that's where this is coming from.
> 
> There are IANA folks here at IETF this week.  I'll ask them.

Thanks,

My estimation is that this would change very rarely.  If I were developing 
software for this, I'd probably check at build time and use that unless there 
are some reason to update.  Not that people won't try, but I think not very 
real time is sufficient.

Scott K

v2.23.0 | Report a Bug | By Email