Re: [dmarc-ietf] Working group next steps
Dotzero <dotzero@gmail.com> Sun, 31 March 2019 18:39 UTC
Return-Path: <dotzero@gmail.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 6FE53120096 for <dmarc@ietfa.amsl.com>; Sun, 31 Mar 2019 11:39:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xmeFoUPdweGf for <dmarc@ietfa.amsl.com>; Sun, 31 Mar 2019 11:39:37 -0700 (PDT)
Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450: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 6295E120048 for <dmarc@ietf.org>; Sun, 31 Mar 2019 11:39:37 -0700 (PDT)
Received: by mail-wr1-x429.google.com with SMTP id y13so9017429wrd.3 for <dmarc@ietf.org>; Sun, 31 Mar 2019 11:39:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Q4XnZVOxceE6JZrmYiQbmL2jwSFD7IzHWl/v8Qs2osI=; b=S11wjsq7qNUtFdCNxk8bQ45A/nq1QXrKJJOdd2jQEHcGVCf2/2G3G8dIR5E49aCbDX cr3cmPU26bqWwFTbtuyHjkDq5jnR965zFZjPq7Og0LGnaaS9olHyJ16q5LymLpNuphpR vpSkoUyzTb3eduyOjtZs5Ndf1glBRSr0qM8aX/DjnM2f8FJ6ZDhRWu+21yxWfH0uJ7FO 4Zr4aEED249aRJ4kKDD+kCPfrVBzsbeRRl4taQWOZqZWT2nsJb9jWrCkmGMzjOBLS340 p5uleovWvN0un6gGvzWz3nJ7UFV3NCNDhwScJCmgEnjYbdFMyT3tcCy4EtgxvOmPNO68 pNEg==
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=Q4XnZVOxceE6JZrmYiQbmL2jwSFD7IzHWl/v8Qs2osI=; b=eWJbbfDvI58TuzG4+cZQ5K0fiGaaXSyS+0SzWD70z0+aWcv0CBwG8TDPAgimYdJePT YxMJfWK9Pi7BF9SAgKC1hAwS99iFCZS/1BKrkr4ufjJtXFIjzJhfxJMP6cgIxP4FRiBu 3PfqiW6wnFN6J8qpQcc/AJABcz21+FMO9hKfxDn00CBx8Ceb7PyvEfPGTeQK+mQS8B1V gLAnt9dkVY6bXp/aBOxZZKfp5+75Y6jMB6El3swHZj8fdXIl+Vvk9POU6thksa0IuAoq ERiKOuuO+4C9ZRtbfUJRu7qgt+C4JhGhpLZiuSmf/rNyNWDQ5lXjl0MUDkWpT6mfrtEX nA0g==
X-Gm-Message-State: APjAAAUYOX/LsYyCn+v6dRGZW1zfjxLCdDzc25XQaVWcw1V8G2YZ65rF oLQPyF1gbNXUn8udLupO8vDr837nY/BWVSYhvsGgFw==
X-Google-Smtp-Source: APXvYqw61KPCGfZW3ZWQhe0JnI8/rqx1GVjGL4jXNyWyqlOGJFrLEWeFw2SqzPhi3a0Be2fiXtWGHWe9JUOFneQ6wNg=
X-Received: by 2002:adf:ee91:: with SMTP id b17mr38669361wro.234.1554057575840; Sun, 31 Mar 2019 11:39:35 -0700 (PDT)
MIME-Version: 1.0
References: <CAL0qLwaPG+CcuMGsJjdJM=x4bigSXvRAHxAf3nk9krknJbtUqw@mail.gmail.com> <LO2P123MB22857A6A1EDD9D54A817C4F5C95A0@LO2P123MB2285.GBRP123.PROD.OUTLOOK.COM> <3802074.4RGYGbXOYh@kitterma-e6430> <LO2P123MB2285E7ED4CD46A11BD9F4676C9540@LO2P123MB2285.GBRP123.PROD.OUTLOOK.COM> <641c4907897e4a81b12847a29bfcd3b8@bayviewphysicians.com>
In-Reply-To: <641c4907897e4a81b12847a29bfcd3b8@bayviewphysicians.com>
From: Dotzero <dotzero@gmail.com>
Date: Sun, 31 Mar 2019 14:39:24 -0400
Message-ID: <CAJ4XoYcyuWv2BVu1JTc-WmGppeQvWOcP+n13Q9L9BzeAUfBF1Q@mail.gmail.com>
To: fosterd@bayviewphysicians.com
Cc: Scott Kitterman <sklist@kitterman.com>, IETF DMARC WG <dmarc@ietf.org>, Ian Levy <ian.levy=40ncsc.gov.uk@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c4bf040585683947"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ym5XddWOSFSa-ZEXg5euq9oYosY>
Subject: Re: [dmarc-ietf] Working group next steps
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: Sun, 31 Mar 2019 18:39:39 -0000
Douglas, Can you show us a single email authentication standard that is 100% deployed on the Internet? There isn't anything that comes close to that achievement. Even things like DNS are not 100%. I know hosts that are only reachable by IP address. Michael Hammer On Sun, Mar 31, 2019 at 2:31 PM Douglas E. Foster < fosterd@bayviewphysicians.com> wrote: > Certainly not. > > You cannot drop existing defenses until the new standard is 100% deployed > on the Internet, which means probably never. Your experimental > implementation will need to prioritize the new test over the SPF test, to > prove that it is working and to show that it is good at intercepting > any subdomains that have been newly imagined by the attackers > > To speed up the deployment process for existing or new standards, IETF > would meed to embrace the idea of defining required features of a spam > filter. > > Doug Fosterd > > ------------------------------ > *From*: "Ian Levy" <ian.levy=40ncsc.gov.uk@dmarc.ietf.org> > *Sent*: Sunday, March 31, 2019 6:18 AM > *To*: "Scott Kitterman" <sklist@kitterman.com>, "IETF DMARC WG" < > dmarc@ietf.org> > *Subject*: Re: [dmarc-ietf] Working group next steps > > >> I’ll also offer gov.uk as an experimental ground (within reason!). > > > Excellent. I've listed it in the experimental registry at psddmarc.org.. > > Since you already had a live DMARC record for that domain, people can > experiment with this now. > > I guess at some point we'll have to stop generating SPF and DMARC records > for the non-existent subdomains of gov.uk so we can test the new stuff > properly. When we're at that point, let me know. > > Ta. > > I. > > -- > Dr Ian Levy > Technical Director > National Cyber Security Centre > ian@ncsc.gov.uk > > Staff Officer : Kate Atkins, kate.a@ncsc.gov.uk > > (I work stupid hours and weird times – that doesn’t mean you have to. If > this arrives outside your normal working hours, don’t feel compelled to > respond immediately!) > > > This information is exempt under the Freedom of Information Act 2000 > (FOIA) and may be exempt under other UK information legislation. Refer any > FOIA queries to ncscinfoleg@ncsc.gov.uk > _______________________________________________ > dmarc mailing list > dmarc@ietf.org > https://www.ietf.org/mailman/listinfo/dmarc > > _______________________________________________ > dmarc mailing list > dmarc@ietf.org > https://www.ietf.org/mailman/listinfo/dmarc >
- [dmarc-ietf] Working group next steps Murray S. Kucherawy
- Re: [dmarc-ietf] Working group next steps Seth Blank
- Re: [dmarc-ietf] Working group next steps Scott Kitterman
- Re: [dmarc-ietf] Working group next steps Hector Santos
- Re: [dmarc-ietf] Working group next steps Kurt Andersen (b)
- Re: [dmarc-ietf] Working group next steps Ian Levy
- Re: [dmarc-ietf] Working group next steps Scott Kitterman
- Re: [dmarc-ietf] Working group next steps Ian Levy
- Re: [dmarc-ietf] Working group next steps Douglas E. Foster
- Re: [dmarc-ietf] Working group next steps Dotzero
- Re: [dmarc-ietf] Working group next steps Ian Levy