Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin
Barry Leiba <barryleiba@computer.org> Sun, 30 June 2013 18:47 UTC
Return-Path: <barryleiba.mailing.lists@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 7857721F9BEF for <dmarc@ietfa.amsl.com>; Sun, 30 Jun 2013 11:47:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.918
X-Spam-Level:
X-Spam-Status: No, score=-101.918 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NW3OO9Oy+lB4 for <dmarc@ietfa.amsl.com>; Sun, 30 Jun 2013 11:47:27 -0700 (PDT)
Received: from mail-vc0-x22f.google.com (mail-vc0-x22f.google.com [IPv6:2607:f8b0:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id D13C421F9BDC for <dmarc@ietf.org>; Sun, 30 Jun 2013 11:47:26 -0700 (PDT)
Received: by mail-vc0-f175.google.com with SMTP id hr11so1530128vcb.20 for <dmarc@ietf.org>; Sun, 30 Jun 2013 11:47:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=w6m64GfzoRZEbkG6ESwIoh4TK9LUcEoz8COn/PCJlB0=; b=wlqRw/6YqqxhiCRlYXiZVI0Jk9Byll+lujD3MKRSMQiD5v2PnNK12yRPlkJ/cQSBUs obUKBIGaWgcEtSLrACFGetKICd6tXxKsv//SBCrBcnKLQ2rUfxOFaUlMxzZ3Ta8cJ6Ta 3gcVIzEnJPxbOFMP7GF+SzMI0TsXjydyTnp9fxFvhWPZ9hgqdHL6Xbcro0Xo4fWE6Q6K Zie1QaA+sQ9hPZtWbW2QrA7Me+LaipXsyF01XFBjiQTf98GHMjJ/imIaH63UJbTX/0HA lt0vzL7wvKTW22MPCcGyHgNm0f+ba5rXvk51FwzrKN4uMD8oTuEJhT4Gmv6BMB1Qi98P VRdA==
MIME-Version: 1.0
X-Received: by 10.52.91.202 with SMTP id cg10mr7086855vdb.85.1372618046199; Sun, 30 Jun 2013 11:47:26 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.137.227 with HTTP; Sun, 30 Jun 2013 11:47:26 -0700 (PDT)
In-Reply-To: <1453736.2es1zahXvQ@scott-latitude-e6320>
References: <20130628211600.84812.qmail@joyce.lan> <51CE0195.8090504@gmail.com> <EAB182AB-76D4-4F88-8BBD-CC327C39BC8D@vigilsec.com> <1453736.2es1zahXvQ@scott-latitude-e6320>
Date: Sun, 30 Jun 2013 14:47:26 -0400
X-Google-Sender-Auth: eCO0uum5RwJqqVSAPCYQcKTO5rQ
Message-ID: <CAC4RtVD1f0ahd_pQaFLcTNYVy3gV_zXH1j40w2FxHXwtqQe-9Q@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Scott Kitterman <sklist@kitterman.com>
Content-Type: multipart/alternative; boundary="bcaec5015cf70e622704e0638bb2"
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
Subject: Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 30 Jun 2013 18:47:27 -0000
> > Then why have a BoF at all? It seems rather premature to discuss work > beyond > the base specification before we know what will be in the base > specification. > > Scott K First, the DMARC spec is sufficiently well baked and mature that it should provide a solid enough basis for discussion. It's not likely that changes to it would be so drastic as to invalidate the BoF results. Second, the *plan* right now is to have the base spec AD sponsored, but the BoF could provide input to that plan. We expect to hear what the community thinks of the work and how it should proceed, as well as to get a sense of who will work on it, who will implement it, and that sort of thing. Barry > Barry tells me that the base DMARC specification will be AD sponsored. > > Therefore, the BOF will talk about work beyond the base DMARC > > specification. > > > > Russ
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Dave Crocker
- [dmarc-ietf] DMARC BoF at IETF 87, Berlin Barry Leiba
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Russ Housley
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin J. Trent Adams
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin John Levine
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Dave Crocker
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Russ Housley
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Scott Kitterman
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Barry Leiba
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Franck Martin
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Scott Kitterman
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin John Levine
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Scott Kitterman
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Franck Martin
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin John Levine
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Franck Martin
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin John R Levine
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Dave Crocker
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin John Levine
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Dave Crocker
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin John R Levine
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Scott Kitterman
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Dave Crocker
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Dave Crocker
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin John R Levine
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Scott Kitterman
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Scott Kitterman
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Dave Crocker
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Scott Kitterman
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Dave Crocker
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Dave Crocker
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Murray S. Kucherawy
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Scott Kitterman
- Re: [dmarc-ietf] Charter improvements John Levine
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Murray S. Kucherawy
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Scott Kitterman
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Dave Crocker
- Re: [dmarc-ietf] Charter improvements Dave Crocker
- Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin Barry Leiba
- Re: [dmarc-ietf] Charter improvements John Levine
- Re: [dmarc-ietf] Charter improvements Dave Crocker
- Re: [dmarc-ietf] Charter improvements John Levine
- Re: [dmarc-ietf] Charter improvements Dave Crocker
- Re: [dmarc-ietf] Charter improvements Rolf E. Sonneveld
- Re: [dmarc-ietf] Charter improvements Dave Crocker
- Re: [dmarc-ietf] Charter improvements Matt Simerson
- Re: [dmarc-ietf] Charter improvements SM
- Re: [dmarc-ietf] Charter improvements J. Trent Adams
- Re: [dmarc-ietf] Charter improvements Dave Crocker
- Re: [dmarc-ietf] Charter improvements MH Michael Hammer (5304)
- Re: [dmarc-ietf] Charter improvements Scott Kitterman
- Re: [dmarc-ietf] Charter improvements Kurt Andersen
- Re: [dmarc-ietf] Charter improvements Kelley, John
- Re: [dmarc-ietf] Charter improvements Dave Crocker
- Re: [dmarc-ietf] Charter improvements Mike Jones
- Re: [dmarc-ietf] Charter improvements Franck Martin
- Re: [dmarc-ietf] Charter improvements Barry Leiba
- Re: [dmarc-ietf] Charter improvements Dave Crocker
- Re: [dmarc-ietf] Charter improvements Roland Turner
- Re: [dmarc-ietf] Charter improvements Dave Crocker
- Re: [dmarc-ietf] Charter improvements Murray S. Kucherawy
- Re: [dmarc-ietf] Charter improvements Murray S. Kucherawy
- Re: [dmarc-ietf] Charter improvements Dave Crocker
- Re: [dmarc-ietf] Charter improvements Murray S. Kucherawy
- Re: [dmarc-ietf] Charter improvements Greg Colburn