From nobody Fri Apr 1 11:13:23 2016 Return-Path: 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 1F72C12D19D for ; Fri, 1 Apr 2016 11:13:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=drkurt.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 LirrGhH2iJom for ; Fri, 1 Apr 2016 11:13:20 -0700 (PDT) Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (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 7785412D172 for ; Fri, 1 Apr 2016 11:13:20 -0700 (PDT) Received: by mail-io0-x232.google.com with SMTP id e3so160699586ioa.1 for ; Fri, 01 Apr 2016 11:13:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=drkurt.com; s=20130612; h=mime-version:sender:date:message-id:subject:from:to; bh=xzYDVVrN+T/sYBCJMCJd6rv8qwm29cI+QxCbdNsMq58=; b=UUHRIZd1jGLdJ2n5FMD+Kn8BTXV+kBdExQZ1noDBdhF3mvMbaCnHsFZlU4XyRxp+bD YR1XdIQBR9iu68uR6xhwQjxkgcEtHVBrlB/Ea7FOlNXB9rkrfs0B72iBlp1pbT6ylhQQ ajAiW6MsLRgOJg6nB+8azK6D3Pw9FJBUJrcu0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:date:message-id:subject:from :to; bh=xzYDVVrN+T/sYBCJMCJd6rv8qwm29cI+QxCbdNsMq58=; b=Na8CBBohVxQ2XXygHj/hZzrUUB7Jg51ZnTrxP9kdaY6/PerZOyPo9S2NCIipkrnAKM J/Qdb3Gb/UlNJY1WtjCIucf7qBwuBOxTf6tBMmtkksM0w9M863Vqkes/LQ+yF+/U7eSn EnOL1JQlBciGwZvMTFVk9QQ3KBHZyqTbktqDxXQLzWtGHVsKvaMEo9Hx2FD20TgqR88w uRQ9O0ZMpu3K3/2I4jEapv7am+N1YxQLQ1vqGSXY1uSMQ+YY/HzGTeIT/lCETnjYvSwK NXCVpsDck8DnJwnieozYw1c/MxcSdYnmehpWdzf39uhqdANNHCnGYtGTwoQuVa4uVC0V UmTA== X-Gm-Message-State: AD7BkJKXpPnzq8kAYo//4R/R9khcULaQRY83DHKcuIF7jwh58eNNdqn8AbrLnRmdJWkxFfBfOFEIUguFkXoxgA== MIME-Version: 1.0 X-Received: by 10.107.150.2 with SMTP id y2mr921433iod.113.1459534399644; Fri, 01 Apr 2016 11:13:19 -0700 (PDT) Sender: kurta@drkurt.com Received: by 10.107.201.16 with HTTP; Fri, 1 Apr 2016 11:13:19 -0700 (PDT) Date: Fri, 1 Apr 2016 11:13:19 -0700 X-Google-Sender-Auth: pOKdO9byHAc2Tu9EWN1DE19lNkY Message-ID: From: "Kurt Andersen (b)" To: "dmarc@ietf.org" Content-Type: multipart/alternative; boundary=001a1140ed3a6dbc36052f705508 Archived-At: Subject: [dmarc-ietf] Moving on to our next phase? X-BeenThere: dmarc@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2016 18:13:22 -0000 --001a1140ed3a6dbc36052f705508 Content-Type: text/plain; charset=UTF-8 Since we've completed the task of identifying the interoperability problems with some mitigations (phase I), is it time for us to move on to our next activity phase? Also, is there some admin-magic that has to happen to move a document from "draft" to "hey! all done!" status? ( https://datatracker.ietf.org/doc/draft-ietf-dmarc-interoperability/) >From the group charter: > Phase I: > * Draft description of interoperability issues for indirect mail flows > and plausible methods for reducing them. > Phase II: > * Specification of DMARC improvements to support indirect mail flows > * Draft Guide on DMARC Usage > Phase III: > * Review and refinement of the DMARC specification > * Completion of Guide on DMARC Usage I think that we need to update our target milestones a bit since they still call for everything to be completed by May 2015. --Kurt --001a1140ed3a6dbc36052f705508 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Since we've completed the task of identifying the inte= roperability problems with some mitigations (phase I), is it time for us to= move on to our next activity phase?

Also, is there some= admin-magic that has to happen to move a document from "draft" t= o "hey! all done!" status? (https://datatracker.ietf.org/doc= /draft-ietf-dmarc-interoperability/)

From the group charter:
=
Phase I:
=C2=A0 =C2=A0* Draft description of interopera= bility issues for indirect mail=C2=A0flows and plausible methods for reduci= ng them.
Phase II:
=C2=A0 =C2=A0* Specification of DMARC improvements= to support indirect mail flows
=C2=A0 =C2=A0* Draft Guide on DMARC Usag= e
Phase III:
=C2=A0 =C2=A0* Review and refinement of the DMARC specif= ication
=C2=A0 =C2=A0* Completion of Guide on DMARC Usage

I think that we need to update our target milestones a bi= t since they still call for everything to be completed by May 2015.

--Kurt=C2=A0
--001a1140ed3a6dbc36052f705508-- From nobody Fri Apr 1 11:59:00 2016 Return-Path: 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 F044512D11D for ; Fri, 1 Apr 2016 11:58:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.718 X-Spam-Level: X-Spam-Status: No, score=-2.718 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=FGD6CYI0; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=nrW1SsxS 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 qH07FyPXuPYL for ; Fri, 1 Apr 2016 11:58:56 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B22C12D0F0 for ; Fri, 1 Apr 2016 11:58:56 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 0F56720BCE for ; Fri, 1 Apr 2016 14:58:55 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Fri, 01 Apr 2016 14:58:55 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=oqrszxFPBEHBE3guTv9WhH/Li14=; b=FGD6CY I0ds/x12HMbqHram7DBQk9yJZFjDIIDBsZTJtk2yZ7Z3ueWRVH9Ji9Fkz+HO6oxa Apv6/LqN/I0bda4cqJ9TjPnkTENX5T7F/ZeOjttenE6zOX+VY5jjl6zSlgRpfui6 8mHvMtjyAPsGE5MkHAMZk165UfOPI3d6D+X/8= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=oqrszxFPBEHBE3g uTv9WhH/Li14=; b=nrW1SsxSq1tpP3JA6Eza0iKMnRTAzRFiACgUpwVbn0MBnf8 qKPP5x79mqX7y7fFby91G7u+OUu2cmS2lXcpNzDVUHp5Rnn/MYAJjE2AQDdRxubo gux9LjbNKcscPheutHgxLPhE7mepVnTH4oVEXPsYX2mGnlQZ1Z+ABB1tSWaA= X-Sasl-enc: 4vgyWnk73oyQ00j251p/jwVRw0zxH/ojHvZ+145rWyAF 1459537134 Received: from [10.14.33.169] (unknown [212.183.128.138]) by mail.messagingengine.com (Postfix) with ESMTPA id ABABA6801A8; Fri, 1 Apr 2016 14:58:54 -0400 (EDT) Content-Type: multipart/alternative; boundary=Apple-Mail-322EF93F-EB6C-4A73-B4CD-5ECBD8F543C9 Mime-Version: 1.0 (1.0) From: Alexey Melnikov X-Mailer: iPhone Mail (13D15) In-Reply-To: Date: Fri, 1 Apr 2016 20:01:44 +0100 Content-Transfer-Encoding: 7bit Message-Id: <763614A1-2F98-416D-A835-BA2CAD7798BF@fastmail.fm> References: To: "Kurt Andersen (b)" Archived-At: Cc: "dmarc@ietf.org" Subject: Re: [dmarc-ietf] Moving on to our next phase? X-BeenThere: dmarc@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2016 18:58:59 -0000 --Apple-Mail-322EF93F-EB6C-4A73-B4CD-5ECBD8F543C9 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Hi Kurt, > On 1 Apr 2016, at 19:13, Kurt Andersen (b) wrote: >=20 > Since we've completed the task of identifying the interoperability problem= s with some mitigations (phase I), is it time for us to move on to our next a= ctivity phase? >=20 > Also, is there some admin-magic that has to happen to move a document from= "draft" to "hey! all done!" status? (https://datatracker.ietf.org/doc/draft= -ietf-dmarc-interoperability/) One of the chairs should do shepherding write up and request publication usi= ng datatracker. Or find another person who can serve as the document shepher= d. >=20 > =46rom the group charter: >> Phase I: >> * Draft description of interoperability issues for indirect mail flows= and plausible methods for reducing them. >> Phase II: >> * Specification of DMARC improvements to support indirect mail flows >> * Draft Guide on DMARC Usage >> Phase III: >> * Review and refinement of the DMARC specification >> * Completion of Guide on DMARC Usage >=20 > I think that we need to update our target milestones a bit since they stil= l call for everything to be completed by May 2015. That would be great! Alexey, Who would become the responsible AD for this group on Wednesday evening. --Apple-Mail-322EF93F-EB6C-4A73-B4CD-5ECBD8F543C9 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi Kurt,

On 1 Apr 2016, at 19:13, Kurt Andersen (b) <kboth@drkurt.com> wrote:

Since we've completed the task= of identifying the interoperability problems with some mitigations (phase I= ), is it time for us to move on to our next activity phase?

Also, is there some admin-magic that has to happen to move a document fro= m "draft" to "hey! all done!" status? (https://datatracker.ietf.org/doc/= draft-ietf-dmarc-interoperability/)

One of the chairs should do shepherding write up and request pu= blication using datatracker. Or find another person who can serve as the doc= ument shepherd.

= =46rom the group charter:
Phase I:
   * Draft= description of interoperability issues for indirect mail flows and pla= usible methods for reducing them.
Phase II:
   * Specificati= on of DMARC improvements to support indirect mail flows
   * Dr= aft Guide on DMARC Usage
Phase III:
   * Review and refineme= nt of the DMARC specification
   * Completion of Guide on DMARC= Usage

I think that we need to update our ta= rget milestones a bit since they still call for everything to be completed b= y May 2015.

That would be= great!

Alexey,
Who would become the respon= sible AD for this group on Wednesday evening.

= --Apple-Mail-322EF93F-EB6C-4A73-B4CD-5ECBD8F543C9-- From nobody Fri Apr 1 12:12:53 2016 Return-Path: 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 E3D6212D643 for ; Fri, 1 Apr 2016 12:12:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.012 X-Spam-Level: X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mrochek.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 bln3skG1V9gf for ; Fri, 1 Apr 2016 12:12:50 -0700 (PDT) Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (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 3603212D11D for ; Fri, 1 Apr 2016 12:12:50 -0700 (PDT) Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PYHXV5CGK000BOL7@mauve.mrochek.com> for dmarc@ietf.org; Fri, 1 Apr 2016 12:07:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mrochek.com; s=mauve; t=1459537665; bh=hAM8AafY4yLkqvA3tfXKUIjsdp/QJJ//O1WA0lfbr78=; h=From:Cc:Date:Subject:In-reply-to:References:To; b=M8jcU5PRNu7VnLvTTN16ruGiB3XXU/JOmsjJoJGh6Jig07b70L97MOEVTpmfo2MEL sjDkTXBiw25Rzcsoi/9MBGovpvaJF/URYjfSZ5r8vRZZnYNSmjyWvIBA83dyI+YyRU IWaH1fGyR51xh8NySyIpoLJGPzQgjGbCxAyMy6vA= MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: TEXT/PLAIN; CHARSET=us-ascii Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PY1MT70XR400005M@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for dmarc@ietf.org; Fri, 01 Apr 2016 12:07:42 -0700 (PDT) From: ned+dmarc@mrochek.com Message-id: <01PYHXV3J4RW00005M@mauve.mrochek.com> Date: Fri, 01 Apr 2016 12:06:50 -0700 (PDT) In-reply-to: "Your message dated Fri, 01 Apr 2016 20:01:44 +0100" <763614A1-2F98-416D-A835-BA2CAD7798BF@fastmail.fm> References: <763614A1-2F98-416D-A835-BA2CAD7798BF@fastmail.fm> To: Alexey Melnikov Archived-At: Cc: "dmarc@ietf.org" , "Kurt Andersen \(b\)" Subject: Re: [dmarc-ietf] Moving on to our next phase? X-BeenThere: dmarc@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2016 19:12:52 -0000 > Hi Kurt, > > On 1 Apr 2016, at 19:13, Kurt Andersen (b) wrote: > > > > Since we've completed the task of identifying the interoperability problems with some mitigations (phase I), is it time for us to move on to our next activity phase? > > > > Also, is there some admin-magic that has to happen to move a document from "draft" to "hey! all done!" status? (https://datatracker.ietf.org/doc/draft-ietf-dmarc-interoperability/) > One of the chairs should do shepherding write up and request publication > using datatracker. Or find another person who can serve as the document > shepherd. I'll take care of it. > > > > From the group charter: > >> Phase I: > >> * Draft description of interoperability issues for indirect mail flows and plausible methods for reducing them. > >> Phase II: > >> * Specification of DMARC improvements to support indirect mail flows > >> * Draft Guide on DMARC Usage > >> Phase III: > >> * Review and refinement of the DMARC specification > >> * Completion of Guide on DMARC Usage > > > > I think that we need to update our target milestones a bit since they still > > call for everything to be completed by May 2015. > That would be great! > Alexey, > Who would become the responsible AD for this group on Wednesday evening. I won't be there but may be online. Ned From nobody Fri Apr 1 12:21:27 2016 Return-Path: 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 41D4812D168 for ; Fri, 1 Apr 2016 12:21:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=drkurt.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 egyEqMK6qWe3 for ; Fri, 1 Apr 2016 12:21:24 -0700 (PDT) Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com [IPv6:2607:f8b0:4001:c05::22d]) (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 55D6C12D11D for ; Fri, 1 Apr 2016 12:21:24 -0700 (PDT) Received: by mail-ig0-x22d.google.com with SMTP id ma7so3782394igc.0 for ; Fri, 01 Apr 2016 12:21:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=drkurt.com; s=20130612; h=mime-version:sender:date:message-id:subject:from:to:cc; bh=nIdzhMKJS93FxLFV/sRAcD72ZKQFcxCS4pX5jwSgpjE=; b=GINP01oYB/YsjL8oGnbqJ4Sb1qgY4FuGcDC6/6tXAFrZBUkESkMvVkJS4g22xYjtBi a4FM6UhqsX7R/zkloXs0mYUrnWPcdDy57Pqr6yHE8KCHr7bEv3RBXn7DYf5gHppf6Z8F 1B85tjW3YmfF+p3HXxEi8kFDsokwCqDXDDoaQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:date:message-id:subject:from :to:cc; bh=nIdzhMKJS93FxLFV/sRAcD72ZKQFcxCS4pX5jwSgpjE=; b=aNFaCJO9hxDrAYdfA46ROw+7pEhfst8sS0sMAffK6ORttwuY5tNDghersJsX+g75HI bTQ9E9ErWtaKQVyzhh1TW3iZUZJUnKMyeJPsXk/lECgj0OjmKSCPOj8EIyGCqZZrwdKF Ag54LqDu5odp8dGNyQIXtjFx9ma3Vn6H0dwPSBEv1rTOng6OrwO/oY1+aAQrH0YV1CMY VgwA4ACqrjHlBWm8TLijZADJnAkGa6HZONEsczHVSgfrxRHR7khSZe1eaUflmJC/6UlO gWbcsPW7eys8nowIV2ftarC2kHrcCcfJFcWUUs4z1UA5KSU1hKTajH8rKAnNwWgEP1so Awbg== X-Gm-Message-State: AD7BkJKBdvCOTMNkhvb6o9loKn33YJ6XqvLKX0P1caeIAP32t49VJ7k744g6wMVz+ySMxm8Lphy9YUmqehDc8Q== MIME-Version: 1.0 X-Received: by 10.50.72.82 with SMTP id b18mr423056igv.79.1459538483695; Fri, 01 Apr 2016 12:21:23 -0700 (PDT) Sender: kurta@drkurt.com Received: by 10.107.201.16 with HTTP; Fri, 1 Apr 2016 12:21:23 -0700 (PDT) Date: Fri, 1 Apr 2016 12:21:23 -0700 X-Google-Sender-Auth: oU_DnHBXPrCFGAYCY0UMybF1wTQ Message-ID: From: "Kurt Andersen (b)" To: Ned Freed Content-Type: multipart/alternative; boundary=047d7bdc9e76dbadde052f71487c Archived-At: Cc: "dmarc@ietf.org" , Alexey Melnikov Subject: Re: [dmarc-ietf] Moving on to our next phase? X-BeenThere: dmarc@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2016 19:21:26 -0000 --047d7bdc9e76dbadde052f71487c Content-Type: text/plain; charset=UTF-8 On Fri, Apr 1, 2016 at 12:06 PM, Ned Freed wrote: > > > On 1 Apr 2016, at 19:13, Kurt Andersen (b) wrote: > > > > > > Since we've completed the task of identifying the interoperability > problems with some mitigations (phase I), is it time for us to move on to > our next activity phase? > > > > > > Also, is there some admin-magic that has to happen to move a document > from "draft" to "hey! all done!" status? ( > https://datatracker.ietf.org/doc/draft-ietf-dmarc-interoperability/) > > > One of the chairs should do shepherding write up and request publication > > using datatracker. Or find another person who can serve as the document > > shepherd. > > I'll take care of it. > Thank you! I'll do my best to attend at least the APPSWG general session (remotely). If there are any others pertinent to this work, please let me know. --Kurt --047d7bdc9e76dbadde052f71487c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On F= ri, Apr 1, 2016 at 12:06 PM, Ned Freed <ned.freed@mrochek.com><= /span> wrote:
> > = On 1 Apr 2016, at 19:13, Kurt Andersen (b) <kboth@drkurt.com> wrote:
> >
> > Since we've completed the task of identifying the interoperab= ility problems with some mitigations (phase I), is it time for us to move o= n to our next activity phase?
> >
> > Also, is there some admin-magic that has to happen to move a docu= ment from "draft" to "hey! all done!" status? (https://datatracker.ietf.org/doc/draft-i= etf-dmarc-interoperability/)

> One of the chairs should do shepherding write up and request publicati= on
> using datatracker. Or find another person who can serve as the documen= t
> shepherd.

I'll take care of it.

Thank = you! I'll do my best to attend at least the APPSWG general session (rem= otely). If there are any others pertinent to this work, please let me know.=

--Kurt=C2=A0
--047d7bdc9e76dbadde052f71487c-- From nobody Fri Apr 1 15:24:31 2016 Return-Path: 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 AEE6F12D589 for ; Fri, 1 Apr 2016 15:24:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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_LOW=-0.7, 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 a1UxdKCVCXES for ; Fri, 1 Apr 2016 15:24:28 -0700 (PDT) Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::230]) (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 0B0F512D1D4 for ; Fri, 1 Apr 2016 15:24:28 -0700 (PDT) Received: by mail-vk0-x230.google.com with SMTP id k1so120437760vkb.0 for ; Fri, 01 Apr 2016 15:24:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=IFSpep9t50Qmt1b6R5Ye2CEpAnFwG9CSB4uMcBBJ2yQ=; b=aZSb1JgibuE/rNQWyoMTqm/BEnHoClhfH5yZQINco55VQL+/8RzO3hyc3nS8eAz/6Y SJMFC5pkmnxlYKD0JrAs5dHnY1X9GwiqxgljvHoGU1nSiBAoxeK9i0lDtOf8dKhqSF7E 1d/ozokU3ecjm3zr/qzoIdjOtkhaVFO4Hr6hmrwhdJkg/9Wu7EQFPfNgOK+y/Ius1orm T/sIuEzjzkmX98fEF1NorQ4YYRDJaBr8a8aFgRXs4teS6ZH1uNyJ6jH17Xa/Z3aqnHC+ BG1puXcaadxsd2rL9QNNZDctuGzQ6XpGVrvxkrqdweokFG8iFODVzeKPTMfDvMma/PFK TDGw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=IFSpep9t50Qmt1b6R5Ye2CEpAnFwG9CSB4uMcBBJ2yQ=; b=RmH3w1z0+39E+8SaSvFkF3vQzUv7q+7ESXEVm6/ZPFkc7YI1U43B6z1UGjAujUhySE kJDnr+dcem2ZBXkAN+U+UhkUeXT6YV4I6yeOwB2qJX4IMmcwka3LHOVdBl1F/FTCY1LZ +h/KkECjUV+RCZdPmfdWJOupbvS3oKh+HjfJYluD1u2oiCxJdknvUMgvuKxzXYJC+kWM w0KjGW8Tz8n6hCh3ES58ZGGCuU8pTjf8F9eBgIejFO516CO7rkVLU6/lfKr9fNE7tqGz eoqVUQgFU+yo6B5+Kmv3yfr7RAE1PiyzCBBmnWwruDn6wmNE+ZTxE9sVNEqE5WpNfV1Y l/nQ== X-Gm-Message-State: AD7BkJIUUbupnSdXdcfOCeYx+l3KcywkcVuev3Yi6CMvpCbYfucSVOUIE/6GVvNs1DcVMixrUjg5wbLGTpu7dw== MIME-Version: 1.0 X-Received: by 10.31.8.205 with SMTP id 196mr139514vki.144.1459549467112; Fri, 01 Apr 2016 15:24:27 -0700 (PDT) Received: by 10.103.43.5 with HTTP; Fri, 1 Apr 2016 15:24:27 -0700 (PDT) In-Reply-To: References: Date: Fri, 1 Apr 2016 15:24:27 -0700 Message-ID: From: "Murray S. Kucherawy" To: "Kurt Andersen (b)" Content-Type: multipart/alternative; boundary=001a1144f91284f97a052f73d709 Archived-At: Cc: "dmarc@ietf.org" Subject: Re: [dmarc-ietf] Moving on to our next phase? X-BeenThere: dmarc@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2016 22:24:29 -0000 --001a1144f91284f97a052f73d709 Content-Type: text/plain; charset=UTF-8 On Fri, Apr 1, 2016 at 12:21 PM, Kurt Andersen (b) wrote: > Thank you! I'll do my best to attend at least the APPSWG general session > (remotely). If there are any others pertinent to this work, please let me > know. > Please note that APPSAWG is in the process of folding into DISPATCH, so the session you're looking for is the latter one. APPSAWG will cease to exist soon. -MSK, co-chair of both of those --001a1144f91284f97a052f73d709 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Fri, Apr 1, 2016 at 12:21 PM, Kurt Andersen (b) <kboth@= drkurt.com> wrote:
Thank you! I'll do my best to attend at least the APPS= WG general session (remotely). If there are any others pertinent to this wo= rk, please let me know.

Please note that APPSAWG is in the process of fo= lding into DISPATCH, so the session you're looking for is the latter on= e.=C2=A0 APPSAWG will cease to exist soon.

-MSK, co-chair= of both of those
--001a1144f91284f97a052f73d709--